Billing4 min read
How billing works
Billing is per workspace, not per site. A workspace is on exactly one plan, and every site inside it shares that plan's monthly pageview allowance.
You are billed for traffic, not for instrumenting your product. Pageviews are the only thing that counts.
The plan and the included pageviews
Each plan includes a flat monthly price and a monthly allowance of pageviews. Custom events, goals, revenue events, outbound clicks, downloads, scroll depth, engaged time, session replays, and AI-crawler hits are all ingested, stored, and shown on your dashboards without counting against that allowance. See What counts toward your quota for the exhaustive list and Plans for the numbers.
The billing period
Your usage period is the calendar month in UTC: the 1st through the last day of the month, reset at UTC midnight on the 1st. This is separate from your Stripe subscription's renewal date, which is when your card is actually charged; the two can fall on different days of the month.
Metered overage
Every plan carries a Stripe metered price alongside its flat base price. Once your workspace's pageviews in the current month exceed the plan's included allowance, every additional 1,000 pageviews is billed at $0.05. The rate is the same on Starter, Pro, and Business, so overage is never a reason to be pushed up a tier: you move up when the included allowance plus the site limit and retention window are worth more to you than the overage.
Going over is a billing event, not an ingest error. Your pageviews keep being recorded in full, and the excess appears on your next invoice.
Workspaces grandfathered onto the old free plan have no metered price, so there is nowhere to bill their excess: their 10,000-pageview allowance is a hard ceiling and recording stops until the month resets. That plan is no longer offered. See Plans.
When usage is reported
A daily job reports the previous UTC day's complete usage to Stripe's billing meter for every workspace on a metered plan with an active, trialing, or past-due subscription. Each report is idempotent (keyed by customer and day), so a retry after a failure never double-counts a day. Stripe sums the daily reports across your subscription's billing period and bills the total overage on your next invoice.
Because usage is reported once daily for the previous day, there's up to a one-day lag between a pageview being recorded and it appearing in Stripe's meter. The in-app usage meter reads live from your own data, so it's always current even when Stripe's view lags by a day.
Reading the usage meter
The usage meter under Settings → Billing shows the current month's pageview total against your plan's allowance, a progress bar, and how much you have left (or how far over you are). If you're over, the meter says the excess is being billed at $0.05 per 1,000. On a grandfathered free workspace, which has no overage price, it says plainly that new events are no longer being recorded.