Cloudflare Web Analytics vs Edge Traffic: How to Filter Bots and Measure Real Visitors
Cloudflare edge traffic displays raw HTTP requests from web crawlers and scrapers. This guide explains why edge counts run high, how client-side Web Analytics isolates real human visitors, and how to enable it on Cloudflare Pages.
Cloudflare Edge Traffic counts every raw HTTP request hitting proxy servers, which inflates numbers with automated bots, scrapers, and crawlers. The standard dashboard cannot filter arbitrary HTTP headers. To see real human visitors, enable Cloudflare Web Analytics. Web Analytics uses a client-side JavaScript beacon that only executes in real browsers, filtering out automated traffic without tracking cookies.
Looking at raw edge traffic numbers leads founders to overestimate website visitors because automated scrapers, security scanners, and search crawlers generate thousands of proxy requests.
Enabling client-side Web Analytics runs a lightweight browser beacon that ignores headless crawlers, providing accurate visitor counts and Core Web Vitals without privacy banners.
Edge Traffic Analytics vs Client-Side Web Analytics (RUM)
The default Cloudflare Traffic tab operates at the DNS and reverse proxy layer.
It records every TCP connection and HTTP packet reaching Cloudflare edge datacenters.
Automated vulnerability scanners probe common URLs every minute.
Search engines like Google and Bing crawl pages continuously to refresh their search indexes.
Uptime monitoring services ping servers on short intervals.
Every static asset on a page triggers a separate HTTP request.
A single human visitor loading an HTML page with twenty images creates twenty-one edge requests.
In contrast, Cloudflare Web Analytics operates as Real User Monitoring (RUM).
RUM relies on a lightweight JavaScript snippet running inside a real web browser.
Headless scrapers, curl commands, and automated spiders do not execute this script.
Therefore, client-side analytics reflects real human engagement rather than proxy load.
Can You Filter HTTP Headers on the Edge Traffic Dashboard?
Founders often ask if they can filter the edge traffic dashboard by User-Agent or custom HTTP headers.
The short answer is no on the standard free Cloudflare dashboard.
The free edge traffic view aggregates all incoming requests into gross bandwidth and request counters.
It does not provide arbitrary HTTP header filtering controls in the analytics UI.
Pro and Enterprise zones offer Bot Class filtering through Bot Fight Mode or Bot Management.
Those paid tiers categorize requests into Human, Likely Automated, or Confirmed Search Engine Bot.
Exporting raw HTTP logs to external data warehouses via Cloudflare Logpush allows custom SQL filtering on headers.
However, Logpush requires paid infrastructure and external query tools.
For small businesses, enabling Cloudflare Web Analytics is the fastest and completely free remedy.
How to Enable Cloudflare Web Analytics on Cloudflare Pages
Cloudflare Pages offers two methods to activate Web Analytics.
The first approach uses the native project toggle inside the Cloudflare dashboard.
The second approach injects a standalone beacon token into your HTML template.
- Dashboard Native Toggle: Open the Cloudflare dashboard and select Workers & Pages from the left navigation.
- Select your Pages project name and click on the Settings tab.
- Scroll down to the Analytics section on the settings page.
- Click the toggle switch to enable Web Analytics.
- Cloudflare edge proxies automatically inject the beacon script into your HTML before serving responses.
- Standalone Token Method: Open Analytics & Logs from the top-level account menu and select Web Analytics.
- Click Add a site, enter your custom domain name, and copy the provided JS token.
- Add this token to your deployment environment variables as VITE_CF_WEB_ANALYTICS_TOKEN or paste the script snippet before the closing body tag.
Key Metrics Provided by Cloudflare Web Analytics
Once enabled, the Web Analytics dashboard provides clean metrics focused on visitor behavior.
Page views show the total number of HTML documents rendered in real browsers.
Visits show unique user sessions based on daily page activity.
Top referrers reveal where visitors arrive from, including Google, Bing, LinkedIn, and direct links.
Core Web Vitals measure real-world user experience across three essential performance signals.
Largest Contentful Paint measures loading speed for main page elements.
Interaction to Next Paint measures user input responsiveness.
Cumulative Layout Shift measures visual page stability.
Edge Traffic Analytics vs Web Analytics Comparison
Understanding when to consult each dashboard keeps your reporting clear.
Use Edge Traffic to monitor bandwidth usage, caching efficiency, and DDoS attack spikes.
Use Web Analytics to measure marketing reach, user engagement, and browser performance.
| Metric Feature | Edge Traffic Analytics | Cloudflare Web Analytics (RUM) |
|---|---|---|
| Measurement Layer | Raw HTTP/TCP server requests at proxy edge | Actual user browser page loads |
| Bot Traffic Handling | Counts all automated spiders and scrapers | Filters out headless crawlers automatically |
| HTTP Header Filtering | Unavailable on free analytics dashboard | Not needed because beacon only runs in browser |
| Privacy and Cookies | No cookies used | Cookieless and requires no consent banner |
| Asset Multiplier Effect | Counts individual CSS, JS, and image files | Counts distinct HTML page views only |
| Performance Insights | Edge cache hit ratios and origin response codes | Real Core Web Vitals (LCP, INP, CLS) |
How to Enable Cloudflare Web Analytics on a Pages Project
- 1Open Cloudflare Pages Project
Sign in to your Cloudflare dashboard and select Workers & Pages from the main left sidebar.
- 2Navigate to Project Settings
Click on your active deployment project name and select the Settings tab at the top.
- 3Enable Analytics Toggle
Scroll down to the Analytics section and toggle on Web Analytics for automatic script injection.
- 4Review Clean Visitor Reports
Navigate to Analytics & Logs and select Web Analytics to review bot-filtered traffic and Core Web Vitals.
Frequently Asked Questions
Why is my edge request count so much higher than my page views?
Edge analytics counts every image, script, stylesheet, and automated scraper hit. A single visitor loading one page can generate twenty edge requests.
Can I filter out scrapers by User-Agent header on the free Cloudflare dashboard?
No. The standard free edge dashboard does not support custom header filters. Enabling Cloudflare Web Analytics solves this because scrapers do not run client-side scripts.
Does Cloudflare Web Analytics require a GDPR cookie banner?
No. Cloudflare Web Analytics is cookieless and does not track visitors across independent domains. You do not need a cookie consent banner for this tool.
Will search engine crawlers inflate my Cloudflare Web Analytics numbers?
No. Automated crawlers from Google, Bing, and other search engines do not execute client-side JavaScript. Only real browsers running JavaScript appear in reports.
Spot an error or have an example to share? Email [email protected].