What counts as an event

Statsy is priced on a ladder of monthly events, from 10,000 to 10 million. Both plans include every feature; the tier only sets how much traffic is included.

What counts as an event

• A pageview, including each client-side route change in a single-page app.
• A goal completion: statsy.goal(), a data-statsy-goal click, a dashboard click or scroll goal, and the automatic outbound, download and checkout_start goals.
• A page-visit goal completed on the server, which is recorded alongside the pageview that completed it, once per session.
• An identify call.
• A verified payment, recorded as a revenue event when the webhook arrives.
• A rage click, the burst the script folds into one event so replays can be filtered by frustration.
• A web vitals measurement, when advanced tracking is on.

What does not count

• Ordinary clicks and scroll-depth reports. They aggregate straight into the heatmap tables and never become events.
• Session replay chunks, however long the session.
• Requests from bots and crawlers, which are recorded separately.
• Anything dropped at ingest: excluded paths and IPs, beacons from hosts you have not added, and browsers that opted out. See Exclude your own visits and bots.

How usage is counted

Events are counted per calendar month in UTC, across every site in the workspace, and refreshed nightly as well as whenever you open the billing page. A site with 20,000 pageviews and 1,000 goal completions in a month has used 21,000 events.

Going over

Nothing is ever dropped for being over the limit, and no page stops reporting. Owners hear at 80% and at 100% of the included amount, and after a week above it the dashboard suggests the tier that fits. Moving up a tier is a plan change, not a surprise invoice.

Tip. The cheapest way to cut event volume is to stop counting things you do not look at: exclude your own IP ranges and admin paths, and check that the tag is not on any page twice. Two tags mean two pageviews per visit.