Usage and billing
Which events count against your plan, which are always free, and what happens when a subscription lapses.
What bills, what never does
Plans are sized by billable events per month. An event bills exactly one unit when it is a pageview, custom event or conversion, from real customer traffic, valid, not a bot, not test-mode, and not a duplicate. Everything else is always free:
| Event | Bills |
|---|---|
| Pageview, custom event, conversion | One unit each |
| Identify, engagement, Web Vitals, click positions | Never |
| Realtime heartbeats | Never |
| Imported history | Never, structurally: imports are aggregates, not events |
Traffic with data-test-mode | Never, and it stays out of every chart too |
One click never double-bills through our own features: when a no-code rule and a raw track call describe the same click under the same name, the pair costs one unit. The one way to pay twice is instrumenting the same element twice yourself under the same name with two mechanisms; the custom events page flags it.
Watching your usage
- The meter in the user menu and under Account, Usage shows the month's billable count against your plan, with a per-site split so one noisy site cannot hide.
- Each site's Settings has a Usage tab: what this site sent, what your other sites sent, what remains.
- Usage counts events as accepted; analytics counts them as they occurred. The two systems agree in total but are deliberately not the same query.
Plans, upgrades, lapses
- Every plan is paid; there is no free tier, because free analytics is usually paid for with visitors' data. Move between sizes whenever traffic changes; cancel any time.
- Hitting a plan's ceiling warns you in the dashboard well before anything is dropped.
- If a subscription lapses, collection pauses after 24 hours and the site's data is kept 90 days so you can come back; after that it is permanently deleted.
- Deleting a site or your account is self-serve and irreversible; the Privacy Policy names the two records that survive, and why.