Collection never stops, and you are never charged for going over.
Two things do happen, and this page says exactly when: we stretch your plan by 10% so a normal overshoot costs nothing, and past that band your reports pause until you move up a step.
The events keep arriving the whole time. That is the part worth understanding before the month it applies to you: a gap in your data would be permanent and could never be bought back, while a paused report is opened by an upgrade — over a period with nothing missing from it.
What happens
We stretch your plan by 10%, and we tell you we have. Passing your included events puts you in a grace band worth another tenth of your allowance. Collection continues through it exactly as before — nothing sampled, nothing queued.
Past the grace band, your reports pause until you move up a step. The collection does not: every event still lands, and your billing page says how many we carried beyond the band.
Your site screens redirect to billing while that lasts, and so do your shared boards — a shared link answers as if it were not there rather than showing a stranger that you went over. Embedded widgets stay up and simply show nothing, so nothing breaks on your own site. Your account settings and billing stay open throughout.
The billing page says so, under the events meter: how far past the band you are, how many events we carried beyond it, and the traffic step that would cover the period.
The moment you crossed is recorded, so your billing page can tell you when it happened rather than only that it did.
What does not happen
We do not throw away your data. Some products offer the opposite trade — an opt-in that stops recording at the limit, with the events during the pause lost for good. We do not have that setting and will not: the month you exceed your plan is usually the month worth measuring, and that record cannot be recreated later.
We do not sample. Your numbers are counts, not estimates.
We do not automatically charge you more. Going over does not silently upgrade you or add a charge, and no overage line ever appears on an invoice. You choose what to do.
We do not stop at exactly 100%. The grace band exists so that a normal overshoot — 1.1M on a 1M plan — costs nothing and interrupts nothing.
What you should do
Three options, and doing nothing is one of them.
Do nothing
Fine for a one-off spike that stays inside the grace band: your data is complete, your dashboard works, the billing page notes the overshoot, and no penalty is accruing.
If the spike is large enough to pass the band, doing nothing costs you the reports for the rest of the period, not the data. Everything is still recorded and waiting; upgrading at any point — including after the spike is over — opens the whole period at once. So a launch you cannot repeat is measured either way, which is exactly why the policy is this way round.
Buy an add-on
Extra events for the current period only. The right answer for a spike you do not expect to repeat — a launch, a viral post, a conference.
Your limit for the period becomes your plan's allowance plus the add-on, and it reverts at the next period. Ask billing@truestat.io — this one is not yet a button on the billing page.
Move up a traffic step
The right answer for sustained growth. It takes effect immediately and is prorated against the rest of your period. See Changing plan.
Moving up a step is self-serve — the Change plan button on your billing page. Buying extra events for a single period is not yet: email billing@truestat.io and it will be arranged manually. Your collection is unaffected either way.
If you stay over month after month
Nothing changes automatically and nothing escalates: no automatic upgrade and no charge. Each new period starts your allowance — and the grace band with it — over again, and your reports open with it, because the new period's count begins at zero.
So a single spike costs you the reports for the rest of that period and nothing after it. What does not resolve itself is a pattern: if you are past the band every month, your reports are paused most of the time, and the fix is a step up rather than waiting for the next renewal.
At some point that is a conversation — if your traffic has outgrown the top of the ladder, write to billing@truestat.io.
What the quota does, period by period
The whole lifecycle in one place, because the answer differs by what changed.
| What happens | Your events | Your reports |
| You pass your included events | still collected | open — the grace band absorbs it |
| You pass the band (plan + 10%) | still collected | paused until you move up |
| The period renews, plan unchanged | collected, count back to zero | open again |
| You move up a step, same billing period | collected; the period's count carries over | open the same day — the ceiling rose above it |
| You move down a step | collected | the smaller plan applies at renewal, and the lock follows it |
Two things are worth pulling out of that table:
An upgrade does not reset your count, and does not need to. The events in the period really were sent, so they stay. What changes is the ceiling — on a 2.5M plan the band is 2.75M, and a period sitting at 1.3M is comfortably under it, so the reports come back immediately.
A downgrade is not a way to unlock. The lock is recalculated against whichever plan you are on, so moving to a smaller one with usage already above its band keeps the reports paused.
What actually stops collection
The complete list, so there is no ambiguity about which one you are in:
The site is switched off in its settings. Deliberate, and reversible.
Your subscription has lapsed past its grace period. See Cancelling.
Your trial ended without a plan being chosen.
Passing your quota is not on that list, in any form. It pauses reports, never collection.
Reducing usage instead
If you would rather bring the number down than pay more, exclusions are free and apply before anything is stored. See What counts as an event.