← Analytics / analytics / faq

About Cloudflare Analytics

In an effort to make analytics an ubiquitous component of all Cloudflare's products, Cloudflare has implemented, and continues to evolve, several ways in which customers can access and gain insights from Internet properties on Cloudflare.

You can access root-level analytics that give you an overview of metadata related to your Cloudflare account, analytics related to specific properties and products, and the GraphQL API that gives you more control over how you visualize the analytics and log information available on the Cloudflare dashboard.

Refer to Types of analytics for more information regarding this subject.

The underlying datasets that Cloudflare Analytics captures and processes share the following characteristics:

• All metrics reflect traffic proxied through the Cloudflare network (also known as orange-clouded), as configured via DNS records in the Cloudflare DNS app. Note that for a CNAME setup, Cloudflare is unable to offer DNS metrics.
• Cloudflare does not count traffic for unproxied DNS records. However, if your site is not proxied through Cloudflare but Cloudflare is your authoritative DNS server, then we are able to collect DNS metrics.
• Cloudflare can only proxy information for traffic targeting specific ports.
• In determining the originating country, Cloudflare uses the IP address associated with each request. Learn about Configuring Cloudflare IP Geolocation.

It is possible that your Cloudflare metrics do not fully align with data for the same site as reported by other analytics sources, such as Google Analytics and web server logs.

Once Cloudflare identifies a unique IP address for a request, we identify such request as a visit. Therefore, the number of visitors Cloudflare Analytics shows is probably higher than what other analytics services may report.

For example, Google Analytics and other web-based analytics programs use JavaScript on the web browser to track visitors. As a result, Google Analytics does not record threats, bots, and automated crawlers because those requests typically do not trigger JavaScript. Also, these services do not track visitors who disable JavaScript on their browser or who leave a page before it fully loads.

Finally, it is likely that unique visitor data from the Cloudflare Analytics app is greater than your search analytics unique pageviews. This is because pageviews reflect when someone visits a page via a web browser and loads the entire page. However, when another site or service like a bot, plugin, or API is consuming partial content from your site (but not loading a full page), this counts as a unique visitor in Cloudflare and not as a pageview.

You may not be seeing metrics on Cloudflare Analytics for the following reasons:

• You only recently signed up for Cloudflare. Metrics are delayed 24 hours for domains on a free Cloudflare plan.
• If you signed up directly with Cloudflare, your nameservers might not be pointing to Cloudflare at your registrar just yet. Registrars can take 24-72 hours to update their nameservers. Metrics will not start gathering until we detect the nameservers pointing to Cloudflare.
• If you signed up through a Cloudflare hosting partner option ↗, something might not be configured correctly. Contact the hosting partner for support.
• Some browser extensions designed to block ads may prevent analytics from loading. To address this issue, disable the ad block extension or allow cloudflare.com on it.

The Overview page shows analytics based on all traffic, including subrequests. However, when you navigate to Analytics & Logs > HTTP Traffic, the metrics (for example, Requests, Data, Visits) are filtered to show only end user traffic (that is, requestSource = eyeball).

As a result, subrequests are excluded from the HTTP Traffic view, which can lead to discrepancies between the numbers shown in Overview and those displayed in other analytics sections of the dashboard.