How do ad blockers affect Google Analytics?
Ad blockers work from filter lists -- long, community-maintained catalogues of advertising and tracking domains. Google Analytics sits near the top of every major list. When a visitor with uBlock Origin, AdGuard, Brave's built-in shields, or a network-level blocker like Pi-hole loads your site, the request to google-analytics.com or googletagmanager.com is cancelled before it leaves the browser. The script never runs. To GA4, that visitor simply does not exist.
This is not a niche behaviour. Industry surveys have put ad blocker usage at roughly a quarter to a third of internet users, and much higher in some groups -- technical audiences, gamers, younger users, and privacy-conscious northern European markets all over-index. If your site serves developers or IT decision-makers, blocking rates above 40% are realistic.
What do Safari and Firefox block by default?
Even visitors with no ad blocker installed are increasingly shielded by their browser. Safari's Intelligent Tracking Prevention caps script-set cookies -- the kind Google Analytics uses -- at seven days, and in some cases 24 hours. The script still loads, but a returning Safari visitor is regularly counted as a brand-new user because the cookie that would have recognised them has already been deleted. Your "new vs returning" split and user counts drift further from reality with every Safari visitor.
Firefox ships Enhanced Tracking Protection, which blocks known tracking scripts outright in its stricter modes, and Brave blocks Google Analytics out of the box. Between them, a substantial slice of your audience arrives in browsers that are actively working against your measurement tool.
This cookie churn is one of the reasons GA4's unique visitor numbers are unreliable -- something we unpacked in detail in unique visitors in Google Analytics.
The consent banner cuts what remains
After blockers and browser protection take their share, the cookie banner takes another. GA4 legally requires prior consent in the EU, and rejection rates of 20-40% are normal -- higher when the decline button is honestly presented next to the accept button. These losses stack: a visitor who would have accepted cookies may still have a blocker, and a visitor without a blocker may still decline the banner.
Put plainly: a European site can easily end up measuring barely half of its actual audience, and -- worse for decision-making -- the missing half is not random. Privacy-conscious users, technical users, and mobile Safari users disappear at much higher rates, which skews every segment, source, and conversion report you look at.
Why does this matter for your business decisions?
Because you make decisions on the numbers. If organic search visitors block trackers at a higher rate than paid social visitors (they do -- technical queries attract technical people), GA4 systematically undervalues your SEO and overvalues your ads. If your checkout conversion rate is computed against only consenting visitors, your real rate is different from the one in the report. Budget flows to the wrong channel, and nobody notices, because the dashboard looks precise.
Can you get the blocked traffic back in GA4?
There are workarounds -- server-side tagging through Google Tag Manager, proxying GA requests through your own domain -- but they are technical, they add cost (server-side GTM needs paid cloud infrastructure), and disguising Google's tracker so blockers cannot see it moves against the visitor's explicit wishes, which is an uncomfortable position and, in the EU, does nothing to remove the consent requirement anyway.
The simpler answer: use analytics nobody needs to block
Blockers target Google Analytics because it builds advertising profiles. A tool that collects no personal data, sets no cookies, and shares nothing with ad networks is a different category of thing -- and measuring with one gets you close to complete data honestly:
- No consent banner, so there is no decline path -- every visitor is counted. See analytics without a cookie banner.
- No cookies for ITP to expire, so Safari visitors do not inflate your "new user" count.
- Nothing for filter lists to object to -- there is no advertising profile being built, which is the entire reason blocklists exist.
This is how TrackTrendy works: a 1.4KB cookieless script, anonymous aggregated counts, EU-focused, from €4/month. When sites switch, the first thing they notice is that the visitor numbers go up -- not because anything is inflated, but because the measurement finally includes everyone.