Turning on Enhanced Ad Blocker Protection
Server-side tagging already moves your requests off Google's domains and onto your own — but that alone doesn't make you invisible to every ad blocker. Filter lists don't just block known hostnames; many also pattern-match known tracking paths, like GA4's /g/collect. A request sitting on your own first-party domain can still get flagged if the path underneath it looks familiar.
How it works
Enhanced Ad Blocker Protection rewrites every request your tracking script sends after the initial page load into a masked format, so there's no fixed signature left for a blocklist to match. The code that does this travels inside your Enhanced script: before Tag Manager runs, it wraps fetch, XMLHttpRequest, sendBeacon and the src setters on images and script tags. Every request goes to a random path and parameter name on your tagging subdomain, with an encoded payload that is different every time, so no two requests look alike. Requests for Google Ads and Google's ad-serving domains are masked the same way.
On the server, Measurebase decodes each request back to its original form before it's forwarded on — nothing changes on the receiving end. Your GTM containers, GA4 property and ad platforms see exactly the same requests they always did; only the path an ad blocker would have inspected in between has changed.
On by default
Enhanced Ad Blocker Protection is on by default for new domains. For an existing domain, switch it on under the domain's Power-ups. If your site already runs the Enhanced script, that's it: the script picks up the protection on its next load, with nothing to change on your site.
- No Enhanced script yet? Generate one from the domain page's Generate script button and install it. The protection needs it: the standard
gtm.jspattern can't carry it. - Tracking outside Tag Manager? A plugin or a hard-coded Google tag that doesn't run through Tag Manager isn't covered by the protection in the script. The power-up's page has an optional separate protection tag for that case: add it directly above your GTM snippet.
Once it's running, the power-up's page shows when the last masked request arrived and which share of them came from browsers with an ad blocker: the traffic this protection recovers. Blockers that only work at the network level, like Brave's default mode or a DNS blocker, can't be seen this way, so read that share as a minimum.
If you turn it off later
Switch it off on the same page. Visitors' browsers keep their copy of the Enhanced script for up to 15 minutes, and requests that still arrive masked in that window keep being decoded, so nothing is lost. If you added the optional separate protection tag, remove it from your site.
It's one layer, not the whole story
Running your tagging server on a subdomain of your own domain already reduces ad-blocker interference on its own, simply by keeping requests first-party. Enhanced Ad Blocker Protection is the additional layer on top, for the requests that would otherwise still get caught on path alone.
To go one step further, Same-Origin Tracking serves your tagging from a path on your own website instead of a subdomain, so there is no separate tracking hostname left for a filter list to match. Paths can still be matched, which is why the masking above stays useful with Same-Origin Tracking on.