Practical guide · Search topic: Cloudflare Pages analytics
Cloudflare Pages analytics: edge requests or visitor analytics?
A Cloudflare Pages site may be measured through Cloudflare’s platform analytics, browser-side analytics or exported logs. Confirm whether the report counts HTTP requests, page views, unique visitors or another event before using the number.
What the query can—and cannot—measure
Edge request data can include bots, assets and cached responses depending on the report. A browser tracker can offer page paths, referrers and campaign context but misses visitors who block the script. Choose the system that answers the operational or marketing question, and keep the definitions separate.
A practical way to do it
Check current Cloudflare documentation and available plan features. Test the browser tag on the deployed Pages domain, verify custom domains and compare only equivalent metrics over the same period.
A useful checklist
- Identify whether the report measures requests or browser views.
- Check bot, asset and cache treatment.
- Keep edge and browser figures labelled separately.
Limits to keep in mind
Platform features and product names may change; verify current Cloudflare documentation and your account’s enabled products.
Questions
Does Cloudflare request analytics equal visitors?
No; an HTTP request is not necessarily a human page visit.
Can I combine Cloudflare and a browser tracker?
Yes, if you preserve their separate definitions and avoid adding unlike counts.
Sources and further reading
Related pages
Install guide & docs · quietstats Sources and channels · quietstats cookie-free analytics Methodology: how quietstats counts visitors, visits, bounce rate and duration
Put your traffic in context
Explore the product, its measurement method and pricing before choosing a tool.