Google Tag Gateway (full name: Google tag gateway for advertisers) is a Google feature that serves the Google tag and its measurement requests from your own website domain, using infrastructure you already run, such as a CDN, a load balancer or a web server. Google started rolling it out in May 2025 for Google Ads, Google Analytics and Search Ads 360.
How it works
Before: the browser loads gtag.js or gtm.js from googletagmanager.com and sends hits to Google domains such as google-analytics.com.
After: you pick an unused path on your domain, for example yourshop.com/metrics/. The tag loads from that path, hits go to that path, and your CDN or load balancer forwards them to a Google endpoint (<TAG_ID>.fps.goog) together with geolocation headers. To the browser, it is first-party traffic.
Google reports that advertisers who configured it “saw an 11% uplift in signals” (Google data, April 9 to 16, 2025, based on Google tag script loads).
Google Tag Gateway vs server-side GTM
| Google Tag Gateway | Server-side GTM | |
|---|---|---|
| What it does | Proxies Google tag requests through your domain | Runs a server container that receives, edits and forwards events |
| Setup effort | Low: a few clicks with Cloudflare | Medium to high: server hosting, container, tags, testing |
| Cost | Free with Cloudflare (gateway requests aren’t billed); other CDNs bill traffic as usual | Hosting costs every month |
| Data control | None: requests pass through unchanged | Filter, enrich, redact or transform events |
| Destinations | Google products only | Google plus Meta CAPI, TikTok and other vendors |
Tag Gateway is enough when you only run Google Ads and GA4 and want a quick measurement gain. You need server-side GTM when you also buy Meta or TikTok ads, want to enrich conversions with first-party data, or need control over what leaves your server. The two also combine: Google documents a setup that puts the gateway in front of a server container. Our server-side GTM setup guide covers the full build, and our tracking setup service handles both.
How to set it up
- Cloudflare (automatic): in Google Tag Manager go to Admin, then Google tag gateway, connect your Cloudflare account and confirm the measurement path. The same flow exists in Google Ads and GA4 tag settings.
- Other CDN partners: Google publishes guides for Akamai and Fastly.
- Google Cloud: route the path through a Google Cloud Load Balancer.
- Manual: configure any CDN or web server to forward your path to
<TAG_ID>.fps.goog, override the Host header and pass the geolocation headers. - Verify with the health check at
/your-path/healthy.
FAQ
Does Google Tag Gateway bypass consent?
No. Consent Mode and your consent banner still apply. With the automatic CDN setup the tag is injected at the top of the page, so check that consent defaults are set before tags fire. Advanced Consent Mode avoids most timing issues.
Does it beat all ad blockers?
No. It reduces blocking based on Google domains, but some extensions still detect and block the requests.
Does it replace server-side GTM?
No. It only proxies Google tags. It does not transform data, extend cookies under Safari ITP or send events to Meta and other platforms.
Sources: Google Ads Help: announcement, Google Ads Help: CDN setup, Google Ads Help: Google Cloud Load Balancer, Google for Developers: Tag Gateway, Google for Developers: setup guide, Cloudflare Docs, Analytics Mania, Loves Data, Secure Privacy