Ad blockers and tracking: every blocker stops Google Analytics by default, but tracking from your own domain with masked requests gets past their filter lists. 4 articles
Every ad blocker stops Google Analytics by default. Visitors who use one do not show up in GA4, their purchases do not reach Google Ads or Meta, and no report tells you how many there were. Blockers work from filter lists that match two things: tracking domains such as googletagmanager.com, and fixed paths such as /g/collect on any domain.
A tagging subdomain of your own gets past the domain lists, but not the path patterns. The Enhanced GTM loader and Enhanced Ad Blocker Protection close that gap: the script loads from a path unique to your domain, and every request after that goes to a random path with an encoded payload. Start with what ad blockers cost your GA4 numbers, which also covers what no setup can recover.
Start here: Ad blockers and your GA4 numbers: what you lose and what you can recover
How the masked Enhanced loader works, how it carries ad blocker protection, and when the standard gtm.js pattern is used instead.
A masked route for your events from the web container to the server container, next to or instead of the Google tag, and how to set it up.
How the guard in your tracking script masks every request so ad blockers can't fingerprint them by URL, and how to switch it on.
Partly. Loading Tag Manager and sending hits through your own tagging subdomain gets past the domain lists, because your subdomain is not on them. It does not get past path rules: a request to your subdomain ending in /g/collect still matches, and plenty of blockers stop it. Masked requests leave no fixed pattern to match.
It depends on your audience: technical and younger audiences on desktop block far more than shoppers on a phone. With Enhanced Ad Blocker Protection on, its page shows which share of the masked requests came from browsers with an ad blocker. Read that share as a minimum, because DNS blockers and Brave's default mode cannot be detected from the page.
Masking only changes what a request looks like on its way to your tagging server. It does not change what you are allowed to collect: consent rules stay the same, and a visitor who refused tracking must not be tracked, whatever browser or blocker they use. A refusal is a choice to respect, not data to recover.