Cookieless web analytics
Privacy, paired with insight.
Everything gets measured. Nobody gets tracked. No cookies, no stored IP addresses, nothing written to a visitor’s device, and no consent banner. Every session counted, past ad blockers, unsampled.
The insight
Every visit, counted.
Traffic, pages, referrers, countries, devices, languages, and any event you define, live and unsampled. The numbers are whole because nothing sits between your visitors and the count.
- Sessions
- 27,564
- Page views
- 66,154
- Pages / session
- 2.4
- Bounce rate
- 41%
- Avg. visit
- 2m 18s
Sessions
Per dayPages
Views- /14,882
- /pricing9,204
- /docs/install6,118
- /how-it-works5,470
- /vs-ga44,236
Channels
Sessions- Organic search9,431
- Paid search7,752
- Paid social5,261
- Direct5,120
The marketing layer
Spend, paired with results.
Analytics tells you how many people came. What it usually cannot tell you is what any of them cost.
So your ad accounts come in too, synced daily and matched to the sessions they paid for. One row per campaign, with its spend, sessions, conversions and CPA side by side.
Both platforms, one axis.
Daily spend in one currency, cut on one set of days. Getting those two right is most of the work, and it is done for you.
What we don’t do.
We don’t show you individual visitors. We don’t build audiences. We don’t follow anyone across the internet. We can’t tell you that user #48291 visited four times, because there is no user #48291. There’s no cookie, no fingerprint, no stored IP address.
What’s left is what you decide with anyway: how many people came, where from, and what they did.
It also means there are no data subject requests to service. When someone asks what you hold on them, or asks you to delete it, there is no record of that person to find.
In practice
Where you notice the difference.
Cookieless analytics sounds like a compliance decision. It is one, and that is the least interesting thing about it. These are the three places it turns up as a better number instead.
01
The figure stops moving.
Nothing is sampled, thresholded or modelled. Every session is a row you can query, so the number you screenshot in March is still the number in September, and two people pulling the same week get the same answer.
02
The refusals are in the count.
Nothing is written to a device, so there is no banner and nobody opts out of being counted. That missing slice is what a consent-gated tool has to estimate, and estimating it is how a dashboard ends up arguing with the finance report about the same month.
03
One line, then nothing to maintain.
A script from your own subdomain and a single DNS record. No tag manager, no cookie library, no consent tool to keep working. Data arrives in about ten minutes and the install does not need revisiting.
The terms
Nothing to get locked into.
The parts of a contract you only ever read when you want out. Ours are short on purpose, and every one of them is checkable against the thing you can sign up for today.
Your numbers are not the product.
Nothing is sold, shared with an ad platform, or pooled into anyone’s benchmark. You are the customer, which is the duller business model and the better deal.
Export whenever you like.
CSV from the dashboard, with the filters and date range you are looking at already applied. No request form, no waiting on us.
Cancel without a conversation.
No minimum term and no exit fee. Cancel from your billing settings, and take the export with you.
Count everyone. Track nobody.
