Huny's Dev Blog
huny.dev

Cloudflare Web Analytics Not Showing Data: Check Installation and the Beacon

Distinguish proxy, manual, and Pages setup and verify beacon loading and data submission.

Hun Jang
Hun Jang Nov 18, 2026

If Cloudflare Web Analytics shows no visitor data, first check whether the beacon is present on the deployed page and sends data from the browser. The installation path depends on whether the site uses the Cloudflare proxy or Cloudflare Pages.

AI-generated conceptual illustration of browser performance measurement and cloud collection

This guide is based on Cloudflare documentation checked on November 18, 2026. The configuration was not tested by changing a live account or site.

Choose the installation path

For a site that does not use the proxy, select Add a site in Web Analytics and register the hostname. Copy the JavaScript snippet from Manage site and insert it before the closing body tag on the HTML pages to measure. You do not need to move DNS to Cloudflare or use its proxy.

For a proxied site, adding the hostname in Web Analytics enables the automatic installation path. Check Manage Site for automatic injection, EU visitor exclusion, manual snippet installation, or disabling the beacon. Before combining automatic and manual installation, inspect existing snippets and the actual response to avoid duplication.

For a Cloudflare Pages project, open the project under Workers & Pages and choose Metrics → Web Analytics → Enable. Cloudflare says the snippet is added on the next deployment. Automatic insertion requires valid HTML. Pages setup and HTML example

Check collection in the browser

Open the deployed page, reload it with the browser developer tools Network tab open, and check whether beacon.min.js loads and a request to /cdn-cgi/rum is sent. The documentation describes the site domain as the destination for proxied sites and cloudflareinsights.com for sites without the proxy. Manual installation may use a different destination, so inspect the actual request. Data collection, setup FAQ

Data can take a few minutes to appear. Check the reporting period and hostname filters, then leave the page or hide the tab and check again. Core Web Vitals are reported when the page first becomes hidden after loading. A single successful request does not prove every visit or metric is collected correctly.

What to check when data is missing

  • Injection: Inspect the deployed HTML for the snippet. With Cache-Control: public, no-transform, proxy-based automatic injection cannot modify the origin response.
  • Security policy and blocking: Check whether Content Security Policy permits the beacon script and its actual destination. Investigate browser extensions and network blocking too. Review only the necessary origins rather than weakening the policy indiscriminately.
  • Settings and deployment: Verify the hostname, measured pages, automatic injection setting, and whether a new Pages deployment has completed.
  • EU exclusion: When enabled, this option prevents snippet injection for EU visitors. Check the test location alongside the setting.

The browser beacon provides real user monitoring (RUM) of the page experience. Visits where JavaScript does not run or the request is blocked can be missing, so do not expect its counts to match Cloudflare edge request analytics. Before production use, check the official FAQ and your settings for collection scope, SPA behavior, and data retention.

한국어 버전: Cloudflare Web Analytics 데이터가 안 보일 때: 설치와 Beacon 점검Cloudflare Web Analytics 데이터가 안 보일 때: 설치와 Beacon 점검

추천 글