How it works
Normally the visitor’s browser loads the Google tag or Tag Manager container from a Google domain such as googletagmanager.com and sends data straight to Google. With tag gateway, your own infrastructure — a CDN or load balancer — sits between your site and Google:
- The browser loads the tag from your domain at a path you choose, e.g.
example.com/metrics/….
- Some measurement requests also go to your domain.
- The CDN forwards them to Google. Google still processes the data.
The feature appeared in 2025 as Google tag gateway for advertisers and works with Google Analytics and Google Ads.
What it gives you
- More resilient measurement. Requests to your own domain are less likely to hit rules that block well-known third-party domains, so some Analytics data and Google Ads conversion signals may come back.
- Simpler than server-side tagging. No separate server or server container — just the CDN already in front of your site.
What tag gateway doesn’t do
- It doesn’t bypass ad blockers as such. In an independent test in 2025, most popular blockers kept blocking measurement with tag gateway too.
- It doesn’t override visitor consent. The cookie banner and consent mode work exactly as before: if a visitor declines, their choice must be respected. How to check consent mode — in a separate article.
- It doesn’t replace server-side Tag Manager. Its request handling capabilities are far more limited.
- It doesn’t make third-party tags first-party. Social media pixels and other services keep loading as before.
What you need
- A Google tag or Tag Manager container already installed on your site. If not, start with installing Tag Manager.
- A CDN or load balancer that can forward requests to external endpoints. Google supports Cloudflare, Akamai, Fastly and Google Cloud.
If your site already runs through Cloudflare, that’s the easiest option: setup takes a few clicks, and according to Cloudflare, tag gateway requests aren’t billed as CDN traffic.
How to turn it on via Cloudflare
- In Tag Manager, open Admin → Google tag gateway and start the setup.
- Choose Cloudflare, make sure the suggested measurement path isn’t already used on your site, sign in to Cloudflare and authorise access.
- Select your domain and complete the setup.
You can do the same from the Google tag settings in Google Analytics (data stream → Google tag settings) or in Google Ads, or directly in the Cloudflare dashboard on the Google Tag Gateway page.
How to check that it works
- Open your site, press F12, go to the Network tab and reload the page. The Tag Manager script should load from your path, not from
googletagmanager.com.
- In Tag Assistant, the tag source should show tag gateway with your path.
- Some requests still go directly to Google — for example, data from EEA visitors goes to regional endpoints. That’s expected.
Don’t load the container twice. Cloudflare can add the container to your pages itself. If the old code is still in your template, tags will fire twice. Keep one way of loading.
Is it worth turning on?
If your site already runs through Cloudflare and you actively use Google Ads — yes, it’s an inexpensive way to make measurement more resilient. If you don’t have a CDN, moving your site just for tag gateway usually isn’t worth it: get the basics right first — tag installation, consent mode and conversion tracking.
In short
- Tag gateway loads Google tags and some requests through your domain; Google processes the data.
- Measurement becomes more resilient, but blockers and consent don’t go away.
- You need a Google tag or container and a CDN — Cloudflare is the simplest.
- Turn it on in Tag Manager: Admin → Google tag gateway.
- Check via the script source in the Network tab and in Tag Assistant.
If you want to set up tag gateway on your hosting without breaking your current analytics, we can set up Google tag gateway: run an audit, choose the setup and verify that visitor consent is still respected.
