Google Tag Gateway (officially "Google tag gateway for advertisers") is a Google feature that serves Google tags through your own domain. Instead of loading scripts and measurement requests directly from googletagmanager.com or google-analytics.com, they run through a path on your website. Google first introduced the feature as "first-party mode".
How does Google Tag Gateway work?
A forwarding layer on your domain, usually on your CDN or load balancer, sits between the browser and Google. The browser only talks to your domain, and the requests are passed on to Google in the background. According to the Google Tag Manager release notes, Google expanded the integrations step by step in 2026:
- January 2026: Google Cloud integration in beta, shortly followed by Akamai
- May 2026: Akamai and Fastly with automatic routing rules
- June 2026: Google Cloud generally available, Amazon CloudFront setup via Tag Assistant
A direct Cloudflare setup was available before that.
What does Tag Gateway bring?
Requests to your own domain are blocked less often by ad blockers and browser protections than requests to well-known Google domains. Cookies can also be set as first-party cookies. In many setups, more measurement data arrives as a result. How big the effect is depends heavily on your audience and browser mix.
What Tag Gateway is not
- Not a substitute for consent: legally nothing changes. In the EU, ad tags may only process data for advertising after consent.
- Not full server-side tracking: data is only forwarded. You cannot enrich, filter or distribute it to other platforms as with server-side GTM.
- Google only: Meta, TikTok or LinkedIn do not benefit. For them you need their own server APIs.
According to analyses of Safari 27, Apple may in future scrutinise forwarding through first-party subdomains more closely. This is not officially confirmed.