Link previews, our own browser checks, a cache host and an EU setting skew Cloudflare stats. We gave 21 dashboards to two models, with and without a skill.
Cloudflare Web Analytics counts a visit whenever a browser runs the beacon, and a lot of browsers that run it are not readers. The usual culprits are the single fetch a social network makes to draw link previews, your own headless-browser checks, and a staging site that shares the same token. Next to that, the table can also be missing real readers: one automatic setup option never injects the beacon for visitors in the EU. To get a reader count you subtract the first group, check the setting for the second, and only then add up the rest. The rows below come from our own sites, and the model test at the end shows how easily the sum goes wrong.
Read the full report on AISkills402: https://aiskills402.com/blog/cloudflare-web-analytics-real-readers?utm_source=devto&utm_medium=social
Top comments (0)