Google Tag Gateway: What It Is, How It Works and How to Set It Up
By Jason Dolan · · 10 min read
In short: Google Tag Gateway (officially “Google tag gateway for advertisers”) is a feature that loads your Google tag from your own domain and sends measurement requests through it, using a CDN or load balancer you already have. Because requests look first-party, they are harder for some blockers to filter and the setup needs no server of your own. It is not a replacement for server-side GTM. This guide explains what it is, how it works, how to set it up and when it is worth using. It draws on eight sources, including Google’s own documentation, Cloudflare’s docs, and independent guides such as Analytics Mania.
What is Google Tag Gateway?
Normally, when a visitor loads your page, the browser requests your tags and sends measurement data to Google’s own domains, for example google-analytics.com for GA4. Many ad blockers and privacy extensions block requests to well-known domains and URLs like these.
Google’s setup guide describes the feature as loading the Google tag from the advertiser’s own domain via an existing CDN, load balancer or web server, with some measurement requests going to Google through that first-party domain. Google recommends it for the most durable tag configuration. In practice, tags are served from a “measurement path” on your site, for example yourwebsite.com/metrics, and a CDN in front of your site forwards the requests to Google.
How does it work?
- A CDN or load balancer sits between visitors and your website’s server. Cloudflare was the launch partner, and Cloudflare’s announcement (May 2025) explains that it fetches the tag script from Google in the background, serves it from your domain, and rewrites later measurement requests back to the original Google endpoint.
- With the automated setup, the tag or GTM snippet is injected into your pages by the CDN, configured to use your measurement path. You do not have to change your site’s code.
- Requests from the browser go to that path on your domain and are passed on to Google.
Beyond Cloudflare, Google documents Cloudflare and Akamai CDN setups and a Google Cloud Global External Application Load Balancer setup, as well as a self-service route for other CDNs. According to trade publication PPC Land, the Google Cloud option arrived in January 2026 and Akamai followed at the end of that month. Google’s help centre also lists articles for Amazon CloudFront and Fastly.
Why use it?
- Fewer blocked requests. Some blockers that match on URLs such as
google-analytics.com/g/collectorgoogletagmanager.combecome less effective. Results vary: Analytics Mania found that some extensions stop blocking, while others, such as Ghostery, still do. - It is free and light. Cloudflare’s documentation says the feature is free to use and does not count towards billing for its other products, and its announcement says it is available on any plan. On Google Cloud you pay standard load balancer usage. There is no tagging server to build.
- It works on restrictive platforms. Because the CDN injects the snippet, it can help on website builders and CMSs that do not allow custom code.
- Tags set cookies under your domain. Cloudflare says scripts served this way create cookies under your own domain. Analytics Mania also notes that routing the GTM container through your domain can make non-Google tags in the same container load more reliably.
- Google reports gains. Google and Cloudflare’s May 2025 announcement cited an average 11% uplift in data signals for early testers. Treat that as a vendor figure: no method was published, and your results will depend on your audience and setup.
What it does not do
This is where expectations need care:
- It is not a full ad-blocker bypass. Sophisticated tools can still block requests, even on your own domain.
- It does not extend cookie lifetimes by itself. With a client-side setup, Safari’s tracking prevention still limits cookies written by JavaScript, as Analytics Mania points out. Google has a separate help article on how the gateway handles cookies, so read it before you promise anything to your stakeholders.
- It does not send everything through your domain. Analytics Mania observed that some requests still go directly to Google, such as regional endpoints when Google signals is on. Google’s explanation, as that article quotes it, is that this is expected for conversion optimisation and regional rules.
- It is designed for Google tags. It cannot route non-Google vendors.
- It does not change your data. There is no filtering, enrichment or privacy control as there is with a server container.
- It does not remove consent requirements. PPC Land stresses that the gateway does not eliminate consent obligations, so Consent Mode and a consent platform (a CMP in the EEA) still have to be set up properly.
Google Tag Gateway or server-side GTM?
| Google Tag Gateway | Server-side GTM | |
|---|---|---|
| Cost | Free feature (you need a CDN or load balancer) | Hosting costs that grow with traffic |
| Effort | Low, mostly in the UI | Higher, needs technical skill |
| Where tags run | In the browser; requests routed through your domain | On a server you control |
| Control over data | None: requests are passed through | Full: filter, enrich, transform |
| Non-Google vendors | No | Yes |
| Cookie lifetime under Safari | Not extended on its own | Can be improved with the right setup |
| Best for | Quick improvement for a Google-only, client-side setup | Control, privacy and many vendors |
Independent sources describe the two as different layers: the gateway changes where tags are served from (delivery), and server-side tagging processes and routes the data (processing). Agency Louder calls them “more complementary than competing” and suggests that large, high-volume sites may want both, while smaller teams may find the extra complexity outweighs the gain (note that Louder sells measurement services). PPC Land reports that Google itself describes the combination as the most durable setup. On the other hand, Analytics Mania argues that if you already run server-side GTM with a custom domain loader, you probably do not need the gateway. Our guide to server-side GTM for GA4 covers the other route.
How to set up Google Tag Gateway
Before you start
- You need an existing Google tag or Google Tag Manager container on your site.
- You need a CDN or load balancer that can forward requests to external endpoints. Cloudflare is the smoothest choice because of its native integration. If you do not use a CDN yet, adding one is often the hardest part.
- You need publish permission on the relevant GTM containers, and the right role in your CDN account. Cloudflare’s docs list Super Administrator, Administrator or Zaraz Admin, and a Google Cloud setup needs the Google Tag Gateway Admin role in the cloud project.
- Choose a measurement path that is not already used on your website, and write it down. Each tag or container needs its own unique path.
Set up from Google Tag Manager (Cloudflare)
- In GTM, open Admin and, under your container, find Google tag gateway. It shows Not set up.
- Read the overview and click Continue.
- Check the zones that are listed and the measurement path. Google’s suggested default is fine for most sites.
- Sign in to Cloudflare and click Allow to connect GTM to your Cloudflare account.
- Click Complete setup.
You can also configure it in the Cloudflare dashboard, on the Google tag gateway page, by choosing the domain, enabling it, and entering your Google tag ID and the measurement path, as described in Cloudflare’s documentation.
Set up with GA4 only (no GTM)
- In GA4, go to Admin, then Data collection and modification, then Data streams.
- Select your web stream and scroll to Configure tag settings.
- Open the Admin tab and select Google tag gateway, then follow the same steps.
Other CDNs and load balancers
- Akamai: set up through GTM (select Google tag gateway, continue, choose Akamai and authenticate). On the Akamai side, a rule is added in Property Manager with the Google Tag Gateway behaviour, then activated, as PPC Land summarises. It supports one Google tag configuration per property, so check Google’s docs for multiple containers.
- Google Cloud: requires your domain’s traffic to go through a Global External Application Load Balancer. The classic load balancer is not supported. See Google’s guide.
- Other CDNs: use Google’s self-service (manual) instructions in the setup guide.
Check that it works
- Reload your website and view the page source. You should see the snippet pointing at your measurement path.
- Open Tag Assistant: the Hits Sent section of the summary should show requests going to your measurement path, and the Google tag settings should show an Active status, as described in Cloudflare’s docs.
- Or open your browser’s developer tools, go to the Network tab, filter by your measurement path and reload.
- Check that events are not duplicated, especially if your site already had a GTM or GA4 snippet.
Gotchas and things to watch
- It works at zone level on Cloudflare. Cloudflare’s docs say it applies to all hostnames and subdomains in the zone, and you cannot switch it on for one subdomain. The workaround is to restrict tags in GTM, for example with a trigger on the page hostname.
- It can override an existing snippet. Cloudflare notes that if you already have a GTM script on your site, the first-party tag overrides it. Check for duplicates.
- It affects every page. Automatic injection adds the snippet to all pages that pass through the CDN, including admin areas.
- Reports can change. Some readers of Analytics Mania reported side effects such as location data showing “(not set)” and internal-traffic filters no longer matching, because requests reach Google from the CDN’s IP addresses. These are anecdotal and were not confirmed, so test your reports and filters after switching it on.
- It is not a data-residency solution. Some data still goes to Google’s regional servers. For EU-only processing you need a different setup.
Should you use Google Tag Gateway?
- Yes, if your setup is client-side, mostly Google tags, behind (or ready to move behind) a supported CDN, and you want a quick, free gain in data quality.
- Maybe later, if you will move to server-side tagging eventually. You can start with the gateway and add a server container later.
- No, if you already run server-side GTM with a custom domain, or you need data filtering, non-Google routing or EU-only processing.
It also works with Parallel Tracking, so you can combine a gateway setup with complete, unsampled GA4 data in your own warehouse.
FAQ
Is Google Tag Gateway free?
The feature is free. You need a CDN or load balancer, and Cloudflare says it can be used on any plan. On Google Cloud you pay normal load balancer usage.
Will it stop all ad blockers?
No. It reduces the effect of some blockers, not all of them.
Does it replace server-side GTM?
No. It cannot extend cookie lifetimes by itself, it cannot route non-Google tags, and it gives you no control over the data. The two are often seen as complementary.
Do I need a developer?
Usually not for the setup itself, which is done in the interface. You may still want technical help with CDN and DNS changes and with testing.
Need help with Google Tag Gateway?
Reflective Data can set up Google Tag Gateway for you: the CDN configuration, the measurement path, testing for duplicates and side effects, and a recommendation on whether server-side GTM would suit you better. We also consult on every other GA4 topic, from implementation and audits and Google Tag Manager to BigQuery and attribution. Book a free consultation.
Sources
- Google, Set up Google tag gateway for advertisers (developer documentation).
- Google, Set up Google tag gateway for advertisers with your CDN (Tag Manager Help).
- Google, Set up Google tag gateway for advertisers with Google Cloud Load Balancer (Tag Manager Help).
- Cloudflare, Google tag gateway for advertisers (developer documentation).
- Cloudflare, First-party tags in seconds: Cloudflare integrates Google tag gateway for advertisers (blog, May 2025).
- PPC Land, Google expands tag gateway reach with Akamai CDN integration (February 2026).
- Louder, Google Tag Gateway vs Server-Side GTM: why enterprise brands may need both (June 2026).
- Analytics Mania, Google Tag Gateway (updated August 2026).
Features and screens change often. Check Google’s current documentation before you set this up.
written by
Jason Dolan
Jason is an expert in digital analytics, data pipelines and data warehouses. Since 2009, he has helped numerous companies become more data-driven and gain full control over their data flows.
We love AI, but this article was written by one of our experts.
discussion
0 comments