Depth where it matters,
nothing you would never read.
Pageviews, visitors, visits, bounce rate and real engagement time out of the box, plus every breakdown below. Auto-capture is opt-in per feature — one attribute each — because an event nobody reads is still a row you pay for.
Twelve things it collects
- AudienceCountry, region, device, browser, OS and language, resolved at the edge with no lookup service.
- AcquisitionReferrers, channels and full UTM campaign attribution, credited to the visit rather than the click.
- PagesTop pages, entry pages, exit pages, and time on page from real engagement rather than request gaps.
- ConversionsSignups, purchases and any custom event, with properties — filterable and breakable down by every dimension above.
- Scroll depthHow far down the page people actually get, at 25, 50, 75 and 100 per cent.
- Video & audioPlay, quarter, half, three-quarter and completion for every player on the page.
- Core Web VitalsLCP, CLS, INP and TTFB from real visitors, as good, needs-improvement or poor.
- Rage clicksThree clicks in one spot inside a second — where people are stuck on something that is not responding.
- Outbound linksWhich links send people away, and where they go.
- File downloadsPDFs, archives, documents and media, tracked without tagging a single link.
- Form submissionsWhich forms get submitted. Never the values people typed into them.
- Real-timeWho is on the site right now, which page they are on, and how they got there.
The part most privacy analytics stop short of.
Traffic numbers tell you a month was busy. These tell you whether it was worth anything — and none of them are a paid tier, because there is no tier to be on.
Goals that count backwards
Define a conversion as a custom event or simply as a page being reached, and it answers for your entire history — not from the day you thought to add it. Nothing to tag, and no code change at all for a thank-you page.
Funnels that respect order
Chain goals into a sequence and see exactly which step loses people. A visit counts at a step only if it genuinely reached every step before it, in order, in the same visit — so the drop-off you are looking at is real.
Revenue on the conversion
Pass an amount with the event and every goal totals it, in your currency, with the average order value beside it. Stored as whole hundredths rather than a float, so the number still reconciles with your payment processor at the end of the year.
Segments worth saving
Any set of filters — mobile visitors from Germany who arrived on a campaign — named once and one click away afterwards, for everyone who can see the site.
A read-only API, included
Bearer-token access to every number the dashboard shows, so it can land in Metabase, a status page or a Slack bot. Tokens can be pinned to a single site and revoked instantly.
It tells you, you don't check
Weekly and monthly summaries by email or webhook, and a spike alert that compares each hour against your own recent baseline — so it keeps meaning something as the site grows, instead of needing re-tuning.
No cookie, no banner, no third party.
Faster than the page it measures
The script is deferred, has no dependencies, and is served from the same edge network as your site. There is no third-party connection to open.
Live, without a polling bill
Current visitors are held in memory at the edge by the same component that does the counting, so the live view costs no database reads at all.
Bots filtered before they land
Running at the edge means every request arrives with a network-level bot score no page-side script can see. Junk traffic is dropped on the way in, not cleaned up later.
Every one of those, on day one.
There are no feature tiers — the price only decides how many sites it is set up for.
One payment · runs in your own Cloudflare account · nothing reports back