How Ad Blockers Are Destroying Your Analytics

Most people think ad blockers just remove banner ads and pop-ups. That was true 10 years ago. Today’s ad blockers, especially tools like uBlock Origin and Ghostery, target a much wider set of scripts.

Modern ad blockers work by matching network requests against filter lists. These lists contain URLs of known advertising networks, tracking services, and analytics platforms. When your visitor’s browser tries to load a script from one of those URLs, the ad blocker kills the request before it executes.

The key distinction in that table is the last row. Server-side tracking operates from your own domain, so ad blockers can’t distinguish it from regular site functionality. We’ll come back to that.

The problem isn’t that your data disappears. The problem is that it disappears selectively.
Ad blocker users aren’t a random cross-section of your audience. They skew younger, more tech-savvy, and more likely to be in B2B or technology sectors. That means you’re not just missing 15-30% of your traffic. You’re missing a specific and often high-value segment of it.

Here’s what that looks like in practice. Your GA4 might show 10,000 monthly sessions. But the actual number could be 12,000 to 13,000. Those missing 2,000-3,000 sessions aren’t evenly distributed. They’re concentrated among users who are often your most valuable prospects: technically literate, privacy-conscious decision makers.

Your traffic numbers drop, obviously. But the downstream effects are worse. Conversion rates appear higher than reality because the denominator (total sessions) is artificially low while your CRM still captures the actual purchases. Your channel attribution breaks because you can’t see the full journey. And your audience demographics tilt away from the tech-savvy segments that ad blockers attract.

One telling signal: if your CRM consistently shows more orders or signups than GA4 reports as conversions, ad blocker interference is almost certainly part of the gap.

Understanding who blocks ads helps you estimate how exposed your specific audience is.

The top three reasons people give for installing ad blockers: too many ads (63.2%), obstructive ad formats (53.4%), and privacy concerns (40.3%), according to GWI data via Backlinko (https://backlinko.com/ad-blockers-users).

If you’re marketing a B2B SaaS product to developers or IT professionals in Europe, you could be losing close to half your analytics data. If you’re running an e-commerce site targeting a general consumer audience in the US, the impact is still there but much smaller.

In mid-2025, Google completed its transition to Manifest V3, the new Chrome extension framework. As a result, uBlock Origin was removed from the Chrome Web Store (https://ublockorigin.com/), and Chrome permanently disabled all remaining Manifest V2 extensions in July 2025.

What does this mean for analytics? It’s a mixed bag.

Manifest V3 replaced Chrome’s webRequest API with a more limited declarativeNetRequest API. This restricts the number of filtering rules ad blockers can use and removes their ability to dynamically intercept network requests. For simple ad blocking (hiding a known banner), it still works fine. But for the aggressive tracker-blocking that power users relied on, it’s significantly less capable.

For marketers, this means ad blockers on Chrome are somewhat less effective at blocking analytics scripts than they used to be. That sounds like good news, but there’s a catch. Privacy-conscious users, the ones most likely to block your analytics, are also the ones most likely to have switched from Chrome to Firefox or Brave, where full-power ad blocking still works. Firefox maintains indefinite Manifest V2 support (https://adblock-tester.com/ad-blockers/manifest-v3-ad-blocker-impact/), and Brave has built-in blocking that doesn’t rely on extensions at all.

So while Chrome’s ad blocker users might be somewhat easier to track now, the most aggressive blockers have simply moved to browsers where they’re even harder to reach.

You have a few options, and they aren’t mutually exclusive. The right approach depends on how much data loss you can tolerate and what resources you have available.

This is the most effective solution. With server-side Google Tag Manager, your tracking requests go from the visitor’s browser to your own server first, then from your server to Google Analytics, Facebook, and other platforms. Because the browser only sees requests to your domain (not to google-analytics.com or facebook.com), ad blockers have nothing to filter.

Server-side tracking also helps with Safari’s Intelligent Tracking Prevention (ITP), extends cookie lifetimes, reduces page load times by moving heavy scripts off the client, and provides a layer of data governance that client-side tracking can’t.

The trade-off: it requires technical setup and ongoing server costs. But for businesses that depend on accurate analytics data, it’s quickly becoming the standard approach.

If full server-side tracking isn’t feasible yet, you can configure a subdomain (like data.yourdomain.com) to proxy your analytics requests. This makes GA4 calls look like first-party traffic. It’s less robust than a full server-side setup, but it catches a good portion of blocked requests.

Tools like Matomo (self-hosted), Plausible Analytics, and Fathom Analytics are designed to minimize tracking footprint. They don’t use cookies, don’t collect personal data, and are rarely included in ad blocker filter lists. They won’t give you the full event-tracking depth of GA4, but they’ll give you more accurate baseline traffic numbers.

No single tracking method is going to capture everything. The smart approach combines multiple measurement frameworks. Use Multi-Touch Attribution for digital touchpoints, Marketing Mix Modeling for cross-channel impact, and incrementality testing to measure real ad-driven results. Together, these fill gaps that any single analytics tool leaves open.

You can’t fix what you don’t measure. Simple scripts exist to detect whether a visitor has an ad blocker active (by testing whether a known ad-related resource loads). Tracking your ad block rate over time gives you a correction factor to apply to your analytics data. If you know 25% of your visitors block GA4, you can adjust your traffic estimates accordingly.