> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/channels/google-tag-manager/gtg-faqs.md). # GTG FAQs ### Google Tag Gateway: What It Does, What It Doesn't, and Whether You Need It You may have recently heard from your Google rep about something called Google Tag Gateway, or GTG. They're recommending it to a lot of advertisers right now, and if you're already running server-side tracking, you're probably wondering whether you need to act on it. Here's an honest breakdown of what GTG does, what it doesn't, and what it means for you. ### What is Google Tag Gateway? GTG makes Google's tracking scripts load from your own website domain instead of from Google's servers. So instead of a request going out to google-analytics.com, it looks like it came from yourstore.com. The idea is that this makes tracking more reliable and harder for ad blockers to interfere with. But it's worth understanding what it actually covers before making any changes. ### What GTG covers - and where it stops? GTG works for GA4, Google Ads, and Google Tag Manager. That's the full scope. Every other platform you're running - Meta, TikTok, Pinterest, Klaviyo, Snapchat - is unaffected. If you're running ads on more than just Google, GTG only addresses one piece of your measurement. A few other things worth knowing: 1. **Ad blockers:** Basic ones may not catch it. But tools like Ghostery and uBlock Origin look at patterns inside the request, not just the domain it comes from. GTG doesn't change those patterns, so more sophisticated blockers still pick it up. 2. **Safari cookies:** Apple limits tracking cookies to 7 days. GTG doesn't change this - cookies are still written by JavaScript in the browser, so the restriction still applies. A customer who returns after 8 days still looks like a new visitor. 3. **Setup:** GTG requires changes to your root domain, DNS records, and CDN configuration. The steps vary depending on your hosting setup and aren't something that can be managed on your behalf - it's work your team needs to own. ### What server-side tracking already gives you? The problem GTG is trying to solve - making tracking more reliable and resilient - is exactly what server-side tracking was built for. If you're already running server-side, here's what that means in practice: 1. Conversions are captured even when the browser can't. Every event fires from both the browser and the server at the same time. If a user's browser blocks the pixel, or they close the tab before it fires, the server-side call already went through. Nothing is missed. 2. Cookies that aren't affected by Safari's limits. Server-side cookies are set via HTTP headers, not JavaScript. Safari's 7-day cap only applies to JavaScript-written cookies - so your returning customers are recognised correctly, even weeks later. 3. Every platform gets the same quality of signal. Server-side tracking isn't Google-specific. Meta, TikTok, Snapchat, Pinterest, Klaviyo, LinkedIn - every platform benefits from the same infrastructure. Nearly 70 in total. 4. Nothing for ad blockers to intercept. Because conversion events are sent directly from the server to each platform, there's nothing in the browser for a blocker to catch on that path. ### What this means for you? If you're already running server-side tracking, you've addressed the core problem at a deeper level - and across every platform, not just Google. GTG would mean making infrastructure changes on your end for a marginal improvement in one channel, when that channel is already being handled well. If your Google rep is pushing on this, a good question to ask them is: given that we're already sending server-side signals directly to Google's API, what specific gap does GTG fill? That usually gets to a more honest answer. If you're unsure about your current setup or want to understand exactly what's being captured, feel free to reach out - we're happy to take a look. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.edgetag.io/channels/google-tag-manager/gtg-faqs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.