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 — the same masking already used for the loader path itself — so there's no fixed signature left for a blocklist to match. On the client, a small guard script wraps fetch, XMLHttpRequest, sendBeacon, and the src setters on images and script tags. Same-origin requests get base64-encoded and rewritten to a masked path; requests destined for Google Ads or Google's ad-serving domains get rewritten the same way, to a separate masked path reserved for that traffic.
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.
Turning it on — three steps
This isn't a single toggle. The guard script only gets added to your tracking snippet at generation time, so turning the feature on in the dashboard doesn't retroactively touch code you've already pasted onto your site.
- Generate an Enhanced script at least once. The toggle stays disabled until a domain has an Enhanced loader to work with — if you're still on the Standard script, generate an Enhanced one first from the domain page's Generate script button.
- Turn on Enhanced ad blocker protection under the domain's Advanced Tracking tab.
- Go back to Generate script, choose Enhanced again, and reinstall it on your site. This step is what actually adds the guard script to the snippet — the toggle alone changes nothing until you regenerate.
It has no effect on the Standard script — if your site is running the Standard loader, this feature simply doesn't apply until you switch.
If you turn it off later
Disabling the toggle removes the guard script from your account, so an already-installed snippet that still references it will start failing to load that file. Regenerate and reinstall the Enhanced script again after disabling, the same way you did to turn it on, so the snippet on your site matches what's actually configured.
It's one layer, not the whole story
Choosing your own domain over a Measurebase-generated subdomain 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.