Event limits
Know which actions count as tracked events and what happens at your allowance.
What counts
| Counts as a tracked event | Does not count |
|---|---|
| Accepted pageview | Stripe payment import |
| Accepted custom event, including an opt-in scroll event | identify or reset |
| Server custom event | Graytower-generated calculations |
A repeated pageview of the same path within 60 seconds is suppressed and does not count.
Accepted events use the same allowance in first-party and cookieless tracking modes.
At the limit
Free warns at 80% of its 2,500-event lifetime allowance and stops accepting tracked events at 100%. Paid plans warn at 80%, mark the included allowance at 100%, and allow a buffer up to 105%. Tracking pauses after that buffer is exhausted. The paid usage window resets monthly, including on annual billing.
| Usage reached | Free | Paid |
|---|---|---|
| 80% | Warning | Warning |
| 100% | Tracking stops | Included allowance reached; buffer begins |
| 105% | Already stopped | Tracking stops |
When tracking pauses
Existing analytics stay readable while tracking is paused. Stripe revenue synchronization continues. Check Workspace → Billing for current usage, the selected tier, and the next reset date. A higher paid tier can increase capacity; a planned tier change does not itself erase events already used in the period.