Avoiding Google tag manager GA4 blocking by adblockers

In this guide

Why they are blocked Check what is being blocked The fixes, in order of effort Do it in Open Tracked What not to expect Frequently asked questions

Check these first

Ad blockers match addresses (googletagmanager.com, google-analytics.com) and file names (gtm.js, gtag/js, /g/collect), not what the script does.
Serving the loader and the collection endpoint from your own subdomain, under neutral paths, avoids most matches.
It will never reach 100 percent. Measure the gain against your store's orders, and keep consent rules in place.

Open your site with an ad blocker on, look at the Network tab, and you will often see red lines for gtm.js, gtag/js or collect. Those are scripts and requests that a filter list recognised and cut. When that happens to GA4 and Tag Manager, the data never reaches you, and tags that rely on them (including your Meta and Google Ads tags) never run. This page explains why it happens and lists the fixes in order of effort. It pairs with bypassing ad-blocker detection and what server-side tracking is.

Why they are blocked

Address lists. Filter lists such as EasyPrivacy name googletagmanager.com and google-analytics.com directly.
Pattern rules. Some rules match file names and paths: /gtm.js, /gtag/js, /g/collect, /analytics.js.
Heuristics. Browsers such as Brave and Firefox with strict protection use their own lists and, in some cases, behaviour checks.
Browser extensions that block by keyword. A path containing track, analytics or pixel can be caught by a generic rule.

Check your setup

Check your tracking in one pass

This is an example. Run the check on your own site to see where yours stands.

Check what is being blocked

Open a private window

Turn on an ad blocker such as uBlock Origin or use the Brave browser.

Open developer tools, Network tab

Reload the page and filter for gtm, gtag and collect.

Look for blocked or failed requests

They show as red, cancelled or "blocked by client".

Note which part fails

The loader script, the collection request or both. The fix depends on which one.

The fixes, in order of effort

SymptomThe Tag Manager script is blocked

Likely causeThe browser asks for googletagmanager.com/gtm.js, which is on filter lists.

FixServe the loader from your own domain. In Open Tracked the Custom Loader power-up (on every plan, including Free) generates a renamed loader address on your own tagging domain and the head code to use. Then remove the old Tag Manager code from the page.

SymptomGA4 collection requests are blocked

Likely causeThe browser posts to google-analytics.com/g/collect.

FixSend GA4 to your own tagging subdomain instead, with a server container. The browser only talks to your domain and your server forwards the event.

SymptomA neutral subdomain still gets blocked

Likely causeThe subdomain or path contains a word such as track, analytics, pixel or ads.

FixUse a plain name for the tagging subdomain (for example data.yourstore.com or go.yourstore.com) and avoid revealing paths.

SymptomThe Meta pixel script is blocked

Likely causeconnect.facebook.net/.../fbevents.js is on filter lists.

FixServe the file from your own tagging address with File Proxy (on every plan in Open Tracked), and send the Conversions API from the server as a back-up.

SymptomBlocking comes back after a few weeks

Likely causeFilter lists are updated and your path was added.

FixChange the path or subdomain, and rely on server-side events so one blocked path does not cost you everything.

The short version

3 things to remember

Scroll and the points stack up.

Ad blockers match addresses (googletagmanager.com, google-analytics.com) and file names (gtm.js, gtag/js, /g/collect), not what th

Serving the loader and the collection endpoint from your own subdomain, under neutral paths, avoids most matches.

It will never reach 100 percent. Measure the gain against your store's orders, and keep consent rules in place.

Do it in Open Tracked

Open the Custom Loader page and type your Web GTM ID (GTM-XXXXXXX).
Pick the platform your site runs on and press Generate.
Paste the first code block as high as possible inside <head> and the second right after the opening <body> tag.
Remove your old Tag Manager code. Only the new code may stay.
Press Test this power-up: it asks for your loader file and expects the Tag Manager script back.
View the page source and check the script address is on your own domain, then confirm status 200 in the Network tab.

What not to expect

Zero blocking. Some users block by behaviour or block every third-party-looking request. Server-side events reduce the loss, they do not remove it.
Permission to ignore consent. A script that loads is not a script that may collect. Consent rules still apply. See Consent Mode v2.
A fix for bad data. If events are wrong, a better route will deliver wrong events more reliably.

0 of 5 done

The Tag Manager loader comes from my own domainThe tagging subdomain has a neutral nameGA4 and the Meta tag also send from the serverI tested with uBlock Origin and BraveI compared platform counts with store orders for a week

Measure the effect. Count orders in Meta, Google Ads and GA4 for a week before and after the change, and compare them with your store.

For online stores

Orders from your store, back to the ad that earned them

Your store sends the order once. Open Tracked passes it on to each ad platform, cleaned and deduplicated.

Frequently asked questions

Why does Tag Manager get blocked?

Filter lists name Google's domains and file names. Serving the script from your own domain under a neutral path avoids most matches.

Does a server container stop all ad blocking?

No. It reduces losses because the browser talks to your own domain, but some blockers also block by pattern or behaviour.

Is it legal to bypass ad blockers?

Serving your own scripts from your own domain is normal. Consent and privacy laws still apply to what you collect. Respect an explicit opt-out.

Will the Custom Loader slow my site?

It loads the same container from a different address. Speed is usually similar, and a cached, nearby address can be quicker.

Which browsers block most?

Brave and Firefox with strict protection block the most by default, and extensions such as uBlock Origin do so in any browser.

Do I need spreadsheets to read my results?

No. Once tracking is live, the Open Tracked analytics shows spend, revenue, ROAS and profit, and you can ask Ari, the built-in AI assistant, questions about your own numbers in plain words. Ari's allowance depends on your analytics plan.

Is Open Tracked different from Open Track or Open Space Track?

No. Open Tracked is the official name of our server-side tracking platform, and the website is opentracked.io. Many people search for it as Open Track, OpenTrack or Open Space Track. All of them lead to the same product: server-side Google Tag Manager hosting, first-party analytics and a CRM pipeline.

Fix your tracking at the source

Open Tracked hosts your server-side Tag Manager, keeps first-party cookies alive and shows what each ad is really worth.

Start free More in Troubleshooting →

Written by

The Open Tracked team

We build Open Tracked: server-side tracking hosting, analytics and the tools around them, for stores that spend on ads. Questions about this guide, or an idea for the next one?

Write to us Read the docs

Was this article helpful?

Comments

Loading comments...