Why your tag is blocked in some browsers but not others
It tracks fine in Chrome, then you test in Safari or Firefox and nothing fires. That is not random: different browsers block tracking to very different degrees, and your setup is only as reliable as the strictest one.
Who blocks what
- Safari (ITP) aggressively limits cookies and third-party scripts, and caps first-party cookie lifetimes to a few days.
- Firefox blocks known trackers by default.
- Ad blockers and privacy extensions block GA4, the Meta pixel and GTM outright for a big slice of users.
What actually survives
Client-side tags will always lose some share to this, and it is growing. The durable answer is server-side tracking: the data is sent from your server, under your own domain, so ad blockers and browser restrictions have far less to catch. Paired with first-party cookies set server-side, your measurement stops depending on which browser a customer happens to use. This same force is what is ending third-party cookies.
Want us to check your tracking in 10 seconds?
Pop in your domain and we will show you what is firing, what is not, and where data is leaking. Free, no signup.
Check my tracking freeGet a plain-English audit
We check your live GA4, Google Tag Manager and consent setup by hand and tell you exactly what is wrong. The audit comes off any build.
See how it works & pricingDatahound are analytics and ad-tracking specialists. We fix broken GA4, Google Tag Manager and server-side tracking so every sale, form and call gets counted. Back to datahound.agency · All tracking guides · What is server-side tracking?