A count showing which pages get viewed and where people drop off. It stores nothing on the visitor's device — which is why your site needs no consent banner.
Either you know nothing at all, or you annoy every visitor with a banner.
You see what gets read, and nobody has to dismiss anything.
- Events are counted, not page views
Not just "someone was here" but "someone tapped call". That's the difference between traffic and demand.
- Where someone came from is included
Google, Instagram, typed directly — that's what decides where effort pays off.
- Numbers are aggregated, not hoarded
Answering which page works needs no personal data. I set it up to collect as little as possible.
- Nothing runs without consent
Until someone agrees, nothing is measured. That's not a preference, it's the law.
- Visit to the site
- Event is recorded
- Report
- Decision
The last step is the point of it. Numbers without a decision are just a prettier way of knowing nothing.
A count of page views running on the same platform that hosts the site. Instead of a persistent identifier on the device, an anonymous value is derived from technical request details and rotated daily. It also measures the real loading times of actual visitors, not lab values.
- Cookies
- none
- Identifier
- anonymous, daily
- Data
- real visits
- Consent
- not required
Seeing which service gets read most
Spotting where people abandon the enquiry flow
Checking whether a change actually helped
You see no individuals and no path across devices. That is exactly the price for the site working without a consent banner.
Running here — and you won't see a cookie banner anywhere, because none is needed.