Skip to content
Analytics

How ad blockers block your analytics: a technical guide

Learn how filter lists can block analytics scripts and event requests, then diagnose the failure on your own page with a controlled test.

By Introtrace··12 min read
Browser requests meet a filter; one is blocked and another reaches an analytics endpoint

In this article

  1. 1. Diagnose blocking on your page
  2. 2. How filter lists work
  3. 3. What gets blocked
  4. 4. The GTM cascade problem
  5. 5. Why first-party proxies work
  6. 6. Frequently asked questions

Diagnose a blocked script versus a blocked event

Start with a working baseline: use the same page, event, and accepted analytics consent with the blocker disabled. Then enable the blocker and repeat. Check the loader request and the event request separately; a missing event alone does not establish which stage failed.

For a specific error, follow the GA4 ERR_BLOCKED_BY_CLIENT diagnostic. If gtm.js is blocked, use the GTM container troubleshooting guide. The free scanner can check an anonymous public-page visit with uBlock Origin.

We also published a Brave test with GA4 receipt verification. It records a baseline, a blocked run, and recovery on Introtrace with accepted consent. Its result is limited to that test configuration.

1. How filter lists work

Strip it down and most ad blockers run on nothing more than a list of URL patterns. Every network request your browser makes gets checked against one or more of those lists, and a match kills the request before it ever leaves.

The major filter lists relevant to analytics are:

EasyPrivacy

The most widely used tracking-specific filter list. Maintained by the EasyList team, included by default in uBlock Origin and AdBlock Plus. Contains explicit entries for virtually every analytics and tracking service. Updated multiple times per week as new tracking endpoints appear.

uBlock Origin's built-in filters

uBlock ships with its own curated lists beyond EasyPrivacy, including specific filters for Google Analytics, GTM, and other services. It also includes Peter Lowe's Ad and Tracking server list.

Disconnect.me Tracking Protection List

Used by Firefox Enhanced Tracking Protection and some other browsers. Classifies domains into categories (Advertising, Analytics, Social, Content) and blocks the Analytics and Advertising categories by default.

Brave Shields

Brave compiles filter list content into a high-performance native engine. It uses uBlock's lists plus Brave's own additional rules, applied at the browser level without requiring any extension.

The syntax handles wildcards and domain matching, so an entry like ||google-analytics.com^ catches every URL on google-analytics.com, subdomains included. Changing the query string or path won't get past that; the domain itself is what's blocked.

2. What gets blocked and why

The exact endpoints every major ad blocker targets, tool by tool:

Google Analytics 4

||google-analytics.com^ (blocks all GA4 data collection) `` ||googletagmanager.com/gtag/ (blocks gtag.js loading) `` ||analytics.google.com^ (browser filter example; server-to-server calls are a separate path)All GA4 events — pageview, scroll, click, purchase, custom events — are sent to google-analytics.com/collect or analytics.google.com/g/collect. Both are explicitly blocked.

Google Tag Manager

||googletagmanager.com^ (blocks gtm.js container loading) `` ||www.googletagmanager.com/gtm.js (explicit GTM container block)GTM itself is the container. When the GTM script is blocked, every tag inside it fails to execute — GA4, Meta Pixel, Google Ads, LinkedIn, Hotjar, all of it.

Meta Pixel

||connect.facebook.net^ (blocks fbevents.js and all pixel events) `` ||facebook.com/tr/ (blocks browser measurement requests)The Meta Pixel script and every event it fires (PageView, Purchase, AddToCart, Lead) are blocked. Custom conversions, custom audiences, and event deduplication all fail.

Other Common Tools

||static.hotjar.com^ (Hotjar script blocked) `` ||cdn.amplitude.com^ (Amplitude SDK blocked) `` ||api.mixpanel.com^ (Mixpanel event collection blocked) `` ||sc-static.net^ (Snapchat Pixel blocked) `` ||snap.licdn.com^ (LinkedIn Insight Tag blocked)Most tracking and analytics services are blocked. The filter lists are comprehensive and maintained by large communities who actively add new trackers.

3. The GTM cascade problem

Google Tag Manager is a single point of failure for every analytics and marketing tool deployed through it. Here's what happens when GTM is blocked:

  1. The browser attempts to load googletagmanager.com/gtm.js
  2. The ad blocker intercepts the request and blocks it — the script never downloads
  3. The GTM container never initializes
  4. No tags inside the container can fire: GA4, Meta Pixel, Google Ads conversions, LinkedIn Insight Tag, Hotjar, custom HTML tags — all silenced
  5. The dataLayer still receives pushes from your site code, but with no GTM to consume them, nothing happens

If the GTM container is blocked, tags that depend on that container cannot run. The effect depends on which tools you deploy through GTM; it does not establish a site-wide percentage of missing visitors.

4. Browser-native blocking (no extension needed)

No extension required for a growing share of blocking these days — modern browsers just ship tracking protection out of the box.

Brave Browser

Brave ships with a built-in ad blocker that compiles uBlock Origin filter lists into a native Rust-based engine (called 'Brave Shields'). It runs before the browser's network stack, blocking analytics requests with essentially zero overhead. No extension required, on by default for all users.

Impact on analytics

Shields is enabled by default and blocks google-analytics.com and googletagmanager.com via EasyPrivacy — no extension required. Brave has ~3-4% browser market share globally, higher in developer and tech audiences.

Firefox Enhanced Tracking Protection (ETP)

Firefox ships with ETP enabled by default since version 69 (2019). In 'Standard' mode, it blocks known trackers in third-party contexts using the Disconnect.me list. In 'Strict' mode, it also blocks tracking content in first-party contexts and fingerprinting scripts.

Impact on analytics

Standard ETP blocks tracking content in Private Windows; Strict mode also blocks it in regular windows. Extensions and custom settings can change the result, so test the configuration your visitors use.

Safari Intelligent Tracking Prevention (ITP)

Safari's ITP works differently — it uses machine learning to classify domains as trackers and then restricts their ability to set and read cookies. JavaScript-set first-party cookies are capped at 7 days. Cross-site tracking is prevented entirely. ITP doesn't block network requests outright, but it severely limits attribution and user identification.

Impact on analytics

Less severe for pageview counting, but significant for attribution, returning user identification, and any analytics that depends on cookie persistence beyond 7 days. Safari has ~18-20% browser market share.

Edge Tracking Prevention

Microsoft Edge includes a Tracking Prevention feature with three modes: Basic, Balanced, and Strict. Strict mode blocks all detected trackers including analytics tools. Balanced mode (the default) blocks trackers that appear to cause security or compatibility issues.

Impact on analytics

Strict mode users get analytics blocking similar to uBlock Origin. Edge has ~5% market share.

Add it up and even a site where nobody installed an ad blocker extension still loses a meaningful chunk of analytics to browsers doing it automatically, with zero effort from the visitor.

5. Why first-party proxies bypass blocklists

A filter list can only match what it knows about — domains and URL patterns it already has entries for. A domain it's never heard of simply isn't in the list.

A proxy can route a request through a custom subdomain such as analytics.yoursite.com and forward it to the analytics provider. This changes the hostname visible to the browser; it does not guarantee delivery under every filter configuration.

Request flow with a first-party proxy

Browser sends event to

analytics.yoursite.com/collectTest recovery

Proxy receives and forwards to

google-analytics.com/collectServer-to-server, never seen by the browser's ad blocker

GA4 receives

Recovered event payloadConfirm receipt in your analytics platform

A custom hostname is one part of a recovery setup. Verify both script downloads and outbound measurement requests, and confirm that recovered events reach the provider with the context you need.

Visitor context preservation

Proxies aren't interchangeable here. A naive one forwards requests with its own server as the apparent source, and that corrupts analytics in a way that's easy to miss: GA4 and Facebook lean on geographic context for location attribution, anti-fraud filtering, and session data. Show GA4 a datacenter in Virginia instead of an actual visitor in Berlin, and your geographic reports go wrong while anti-bot filters start behaving unpredictably.

Forwarding visitor context depends on the proxy and provider. Verify session identifiers, consent parameters, and geographic reports in a controlled test. An event arriving through the proxy does not prove that every field is unchanged or that attribution is complete.

6. How to check if your analytics are being blocked

A few practical ways to measure the actual gap on your own site:

1

Brave browser test

  1. Open your site in Brave browser with Shields enabled (the default)
  2. Open DevTools → Network tab
  3. Look at requests: any request to google-analytics.com, googletagmanager.com, or connect.facebook.net will show as blocked (often with a red X or simply absent)
  4. Compare against Chrome with no extensions — the difference is what Brave users are blocking
1

Compare GA4 sessions vs server logs

  1. Pull your GA4 session count for a date range from Google Analytics
  2. Pull your server-side request count for the same pages and period from your web server logs or CDN logs
  3. Compare equivalent metrics; total server requests and GA4 sessions have different denominators
  4. Account for bots, repeat requests, caching, consent, and tag errors; the difference is not a blocking rate
1

Check the browser console

  1. Open your site with uBlock Origin installed and enabled
  2. Open DevTools → Console
  3. Look for failed network requests (usually shown in red)
  4. You'll see entries like 'Failed to load resource: net::ERR_BLOCKED_BY_CLIENT' for analytics endpoints

7. Solutions compared

Once blocking is confirmed, there are a handful of ways to actually get that data back:

Do nothing

Pros
  • No effort required
Cons
  • Leave measured blocked requests unresolved
  • Marketing campaigns optimize on wrong data
  • A/B tests run on a biased sample

Not recommended for any site where data quality matters

Server-side tracking (move analytics to backend)

Pros
  • Can work with GA4 Measurement Protocol
  • Full control over data
Cons
  • Significant engineering effort — weeks of work
  • Loses client-side context (scroll depth, click events, etc.)
  • Requires per-platform implementation
  • Expensive ongoing infrastructure

Viable for large engineering teams with dedicated analytics infrastructure

Full analytics proxy (route all traffic through proxy)

Pros
  • Works for most analytics tools
Cons
  • Routes ALL analytics traffic, not just blocked — high cost at scale
  • Adds latency for every visitor, not just blocked ones
  • DNS/CNAME required regardless of blocking
  • Single point of failure for your analytics

Works but is expensive and over-engineered for the problem

Targeted signal recovery (Introtrace approach)

Pros
  • Only intercepts signals that are actually blocked — normal traffic unaffected
  • One script tag, 2-minute setup
  • Supports tools such as GA4, GTM, Meta Pixel, Mixpanel, and Amplitude
  • Verify visitor context and geographic attribution after recovery
  • Free to start, low cost at scale
  • The recovery script adds browser-side work; measure performance
Cons
  • Requires adding a script to your site

Lowest overhead approach — you only pay for what's actually recovered

Summary

None of this is mysterious: ad blockers match your analytics URLs against maintained filter lists, deterministically. GA4, GTM, Meta Pixel, and most of the rest have sat on those lists for years, and there's no version of using them that dodges users who have those lists switched on.

Introtrace serves blocked scripts and relays blocked events through cdn.introtrace.com by default. Paid plans support a custom subdomain through CNAME configuration. Test recovery on your own pages and confirm event receipt before estimating the resulting analytics coverage.

That's the gap Introtrace closes. Add the script tag and you'll see how much of your own site's data was missing, recovered starting immediately.

See how much data you're losing

One script tag, and analytics signals blocked by ad blockers start coming back. Free up to 20,000 recovered signals per 30 days.

Create a free account

Frequently asked questions

Can filter lists be updated to block first-party proxies?

Yes. A custom subdomain does not guarantee delivery under every filter configuration. Test your proxy with the browsers and filter lists your visitors use, and repeat those checks when your integration changes.

Does using a proxy affect visitor location data seen by analytics?

It can. Check the visitor context your proxy forwards and compare recovered events with a controlled test visit. Do not assume geographic reports remain accurate solely because the event arrived.

Are server-side tracking tools like GA4 Measurement Protocol immune to ad blockers?

A browser extension cannot intercept a request sent directly between servers. You still need a way to collect the event and supply the relevant session and consent context. Browser-generated data may require client-side collection, and any combined tracking setup needs duplicate handling.

Will Google penalize my site for using a first-party analytics proxy?

This article does not establish how a proxy affects search rankings. Evaluate performance, user experience, consent, and analytics delivery separately; Introtrace does not promise an SEO outcome.

How do I know how much data my site is currently losing to ad blockers?

Compare a test visit with an ad blocker enabled and disabled, using the network panel to identify blocked requests. To investigate broader gaps, compare equivalent analytics and server-side metrics for the same period, accounting for consent, bot filtering, and counting differences.