Cloudflareinsights.com blocked - workaround?

General Analytics
1

What is the name of the domain?

crestpoint.ro

What is the error number?

“blocked” by browser, no error number

What is the error message?

This URL matches a known tracker and it would be blocked with Content Blocking enabled.

What is the issue you’re encountering

This URL matches a known tracker and it would be blocked with Content Blocking enabled. Looking for a workaround.

What steps have you taken to resolve the issue?

Searched the web, few results for the same issue, found a script posted on this site:
https://kai.bi/post/cloudflare-web-analytics-kill-adblock
but couldn’t make it work with mine by creating a worker, as the script got rejected by Cloudflare (err 405 - Not allowed)
Tried to add the address to the exceptions list, still get the same message, besides, I can not ask all visitors to do the same, even if this would have worked.
Using Firefox 132 (x64 bit) on Linux

What are the steps to reproduce the issue?

Visit the site (with Firefox browser), see how https://static.cloudflareinsights.com/beacon.min.js is being blocked.

What feature, service or problem is this related to?

Web Analytics

Screenshot of the error

Screenshot from 2024-12-02 20-24-08.png
Screenshot from 2024-12-02 20-24-08.png326×171 12.1 KB

2

So after 2 weeks I have 17 views on this question but zero feedback or help, thread about to be permanently locked. Conclusion is that this “beacon” on cludflareinsights is useless and no one can make it actually work. Taking it down and opting for another solution in traffic analysis.

3

You will always have this issue when you are using well known analytics / tracking addresses, together with any adblockers, or privacy solutions, such as e.g. the “Enhanced Tracking Protection” of Firefox.

Looking at the source code of your website, and especially the parts you’ve commented out at the moment:

<script defer src='https://static.cloudflareinsights.com/beacon.min.js' data-cf-beacon='{"token": "0ef2d7c011f649d5b917d2186cbbec5a"}'></script>
<!--script defer src='https://muddy-art-f73b.bold-sun-3551.workers.dev/' data-cf-beacon='{"send":{"to": "https://static.cloudflareinsights.com/beacon.min.js"},"token": "0ef2d7c011f649d5b917d2186cbbec5a"}'></script-->

The “to” part of the attributes, under “data-cf-beacon”, e.g.:

{"to": "https://static.cloudflareinsights.com/beacon.min.js"}

This kind of setup will still be sending the data towards the cloudflareinsights.com domain, meaning that you haven’t followed the advice from the post you’re linking to 100%.

That “to” should also be pointing to an address that the Worker is intercepting, and under your own domain name, so you’re not depending on the cloudflareinsights.com domain at all.

Use your own domain name (or a sub-domain of it), would be my only advice.

Using the “workers.dev” addresses are likely also going to be a huge fiasco here.

These addresses share many different users (and use-cases), so such “shared-use” / “multi-tenant” domain names are likely to get blocked from time to time as well.

Opting for another solution won’t change a thing, as the well-known analytics / tracker addresses from other solutions would be blocked too.

1 Like
4

This topic was automatically closed after 43 days. New replies are no longer allowed.