What it is.
Cloudflare reports the traffic it already routes, so measurement does not depend on a script running in the visitor's browser. That means numbers that survive ad blockers and privacy settings.
Use it as a second opinion. When your analytics shows a traffic drop, edge numbers tell you whether traffic fell or whether tracking broke.
Because there are no cookies involved, it sidesteps most of the consent problem that makes client-side analytics under-report.
What you get.
- Page view and referrer data measured at the edge.
- Numbers that do not depend on a script loading in the browser.
- A cross-check against your client-side analytics.
- No cookie, so no consent banner requirement for this data.
- All of it on Cloudflare's free plan.
How to set it up.
Confirm your site is proxied through Cloudflare, since the data comes from traffic passing through it.
Enable Web Analytics in the dashboard for the zone you want measured.
Compare a week of edge page views against the same week in your client-side analytics.
Treat a large gap as a tracking problem to investigate, not as a traffic change.
Use referrer data to sanity-check channel numbers your ad platforms report.
Keep your existing analytics, since this measures traffic and not behavior.
Use cases
Numbers that survive an ad blocker
Measure at the edge so a blocked script does not lose the visit.
Traffic without a banner
Report page views with nothing stored in the browser.
Second source for a disputed number
Compare against your tag when the two reports disagree.
Best for
Traffic drops you cannot explain
Edge numbers tell you whether the traffic left or the tag broke.
Privacy-sensitive sites
No cookie means no consent gate on your basic traffic numbers.
Sites already on Cloudflare
It is a switch, so there is nothing to install or maintain.