Website analytics without the privacy tax
Every site owner needs answers to basic questions: Which pages get visited? Where do visitors come from? What sites refer traffic? Traditional analytics providers offer these insights “free,” but the real cost is user privacy. Cloudflare is introducing a privacy-first analytics service available to anyone, not just its own customers.
The company’s core business has never relied on tracking users or serving ads, so its analytics product takes a different approach. The key principle: no client-side state such as cookies or localStorage, and no fingerprinting via IP address, User Agent string, or similar data. Fingerprinting is considered more invasive than cookies, since users have no way to opt out of it.
How visits are counted without tracking
Traditional tools report “unique” visitors, which requires identifying individual users over time. Cloudflare instead measures visits: a visit is a successful page view whose HTTP referer doesn’t match the requesting hostname. That means a single visit represents someone navigating to the site from elsewhere, without needing to recognize that person on their next session.
This definition differs from “unique” counts, so numbers won’t match other analytics platforms. It also avoids collecting data on users who arrive directly or via same-site navigation in a way that ties separate sessions together.
Slicing data without the noise
The dashboard shows core metrics like page views and visits, plus breakdowns by hostname, URL, country, and status code. Any of these dimensions can be clicked to filter the entire view. The time-series charts support drag-to-zoom for narrowing into a specific window and a “group by” option to re-dimension the data — useful for diagnosing traffic spikes.
For Bot Management customers, a forthcoming feature will identify automated traffic and allow one-click blocking via Firewall Rules. The analytics infrastructure runs on Cloudflare’s ABR technology, which is designed to serve results quickly regardless of site size.
Edge measurement vs. browser measurement
Web analytics can be collected either at the edge (server-side) or in the client via a JavaScript beacon. Cloudflare has traditionally collected data at the edge, which offers:
- Higher accuracy, since users who block third-party scripts or JavaScript entirely are still counted.
- Visibility into all traffic back to the origin server, even when HTML pages don’t load.
- Built-in bot detection and Firewall rule application before data is recorded.
- The ability to measure origin server performance.
Client-side measurement, the approach most providers use, has its own advantages:
- Captures performance as users actually experience it, such as page render time.
- Detects errors in client-side JavaScript execution.
- Supports custom event types emitted by JavaScript frameworks.
Cloudflare’s Browser Insights already augment edge analytics with performance data and now incorporate Web Vitals metrics. But edge-based measurement requires DNS changes that not every site owner can make. That’s why the standalone analytics product works via a JavaScript snippet instead.
Availability and rollout
Existing customers on Pro, Biz, and Enterprise plans can opt into the new analytics experience from the Analytics tab today. The team plans to make it the default in a few weeks. The JavaScript-based standalone version is still in final development; anyone can sign up to be notified when it’s ready.
The launch marks a shift in how Cloudflare thinks about analytics. What began as a basic set of metrics around cache performance and Firewall activity has expanded into flexible analytics for Firewall, Cache, Load Balancing, and Network traffic. Making those analytics available as a standalone product is described as only the first step, with real-time analytics, deeper performance analysis, and custom events planned.
