Cloudflare Web Analytics: An Honest Review of the Limits
Cloudflare Web Analytics is free and privacy-friendly. It is also minimal by design. What it answers, what it cannot, and when to upgrade.
Cloudflare Web Analytics costs nothing, requires no cookies, and comes from a company whose privacy arguments are credible. As a free baseline it is genuinely respectable — which is exactly why an honest review matters: the limits are structural, not bugs, and you should know where they sit before depending on it.
What you get for free
- Pageviews, visits, top pages, referrers, countries, and device classes — cookieless, banner-free.
- Basic Core Web Vitals sampling.
- Either zero-install (traffic proxied through Cloudflare) or a JS beacon for any site.
The structural limits
- Short retention, coarse history. Data visibility is limited to recent windows; year-over-year questions and long-trend SEO analysis are out of reach.
- No custom events. No signups, no CTA clicks, no funnels — the tool counts visits and stops. The entire event layer is absent.
- No identity, no attribution. Without identify() or persistent first-touch capture, 'which channel produced this customer' cannot be asked, let alone answered.
- Sampling and bot ambiguity. High-traffic properties see sampled estimates, and proxy-level counting includes noise that beacon-based tools filter differently — expect numbers that disagree with everything else.
- Reporting is a panel, not a product. No per-page drill-downs of consequence, no journeys, no shareable public dashboards, no error capture.
Who it fits
A personal site, a docs mirror, a project where the only question is 'is anyone visiting?' — Cloudflare answers that for free with clean privacy. No criticism; that is a real use case.
Who outgrows it, and when
The day your site exists to produce outcomes — signups, sales, subscribers — you need events, attribution, and enough retention to see seasonality. The upgrade test is concrete: can your analytics answer 'how many people converted last month, and from which source?' Cloudflare cannot, structurally. A purpose-built cookieless tool can, while keeping the same privacy posture: Clycyo adds custom events, first-touch attribution, identify(), webhook revenue, per-visit load times, and JS error capture — still 1.1 KB, still no banner.
Honest comparison
| Capability | Cloudflare WA | Clycyo |
|---|---|---|
| Price at small volume | Free | Free (10k events/mo, forever) |
| Cookieless | Yes | Yes |
| Custom events / funnels | No | Yes |
| Attribution & revenue | No | Yes |
| Errors + load time per visit | No | Yes |
| Public live demo to judge first | No | Yes |
Run both if you like — they coexist without conflict — and let two weeks of side-by-side data make the call.