Google Tag Gateway vs. Google Tag Manager: What's the Difference?

Google Tag Manager (GTM) is a tag management system, which is a container that lives on your website and controls what tags fire and when. The container holds three things:

1. Tags (the tracking snippets that send data somewhere — GA4, Google Ads, Meta Pixel, LinkedIn Insight Tag, custom scripts),
2. Triggers (the rules that determine when each tag fires — page views, form submissions, scroll depth, button clicks), and
3. Variables (the data those tags pass along — transaction IDs, product names, event values).

The most important thing GTM does is separate tag deployment from development work. Your marketing and analytics team can add, update, test, and publish tags without touching the site’s source code or opening a ticket with a developer. Adding tagging to a website used to be very tedious before GTM came along!

GTM is also platform-agnostic: it works with Google and non-Google tags. Yes, you can send data to Google Analytics, but also to Meta, LinkedIn, TikTok, custom scripts — it’s really up to you and your tagging needs. This matters because it’s directly relevant to what Tag Gateway can and can’t do.

Google Tag Gateway (GTG) is a content delivery network (CDN) based routing layer that sends your Google analytics data, including Google Analytics, Google Ads, and Floodlight, through your own domain instead of directly to Google’s servers. It doesn’t change what data you collect or when, it only changes the network path that data takes after you collect it.

That might sound very similar to what server-side GTM does, and we’ll get to that!

Here is how GTG works: when your browser sends data off to Google Analytics, that request travels directly to Google’s servers, using a URL pattern that looks something like google-analytics.com/g/collect. Unfortunately for marketers, many browser extensions and ad blockers recognize this pattern and since they know exactly what it’s doing, they block it. When that happens, the person using the ad blocker is totally invisible to Google Analytics. That’s one of the many reasons why marketing analytics data isn’t totally accurate.

With Google Tag Gateway enabled, those requests are routed through a path on your own domain first — something like yoursite.com/gtg/. From the browser’s perspective, it looks like a something on your own site (called a first-party request). That data is then sent off to Google without the browser or ad blocker realizing that’s what is happening.

What Google Tag Gateway covers (and what it doesn’t)

Google Tag Gateway works only with Google products: GA4, Google Ads, and Floodlight. If you have a non-Google tool like the Meta Pixel, LinkedIn Insight Tag, or TikTok Pixel in your GTM container, those aren’t included. They still route directly through their respective platforms’ servers and thus can be blocked by browser privacy and ad blocking tools. If you want to route those through a first-party system, you’ll need to use server-side GTM (sGTM) instead.

Does Google Tag Gateway improve performance?

According to Google’s own internal data — and to be clear, this is an aggregated year-over-year comparison, not a controlled study — advertisers using Tag Gateway saw a 14% increase in measured conversions and a 7% reduction in cost per acquisition. Keep in mind that this is self-reported internal trends from Google, not an independent third-party study. So while yes, there were improvements by implementing GTG, your experience will vary and does depend a lot on how technologically-savvy your audience is. One thing that I do like about this data is that it doesn’t show an absolutely massive change, which it shouldn’t. Implementing something like GTG can give you incremental improvements in data collection, not massive increases.

CDN support

Setting up Tag Gateway requires a CDN. If you don’t have one already, native integrations are available for Cloudflare (including the free tier), Fastly, Akamai, Google Cloud CDN (currently in beta), Webflow, and Duda. Cloudflare is usually the most accessible path for most sites and it’s what we use. The free tier will work well for most small and mid-sized website traffic without any problems.

How much does Google Tag Gateway cost?

Tag Gateway is free from Google’s side, but you’ll need to handle any CDN costs. As I mentioned, Cloudflare’s free tier is sufficient for many sites. If you have more traffic than Cloudflare’s free tier can handle, you might already have a CDN set up for other purposes, so check with your IT team.

Google Tag Gateway limitations

In addition to what I noted earlier about how GTG doesn’t cover your non-Google tracking, one big misconception is people think it will extend how long your analytics cookies are stored on your user’s devices. That isn’t the case, Google Tag Gateway does not extend cookie lifetime, nor does it change how cookies are set on the browser side. If Safari’s Intelligent Tracking Prevention (ITP) is capping your attribution window at 7 days and causing you to miss conversions, Google Tag Gateway won’t fix that.

Keep in mind that Google Tag Gateway is a measurement accuracy tool, not a user privacy tool. The data still goes to Google at the end. The routing change reduces the chance of a browser extension interrupting the signal in transit, but it doesn’t reduce the amount of data being sent or who receives it. If your organization’s priority is minimizing data flows to third parties, Google Tag Gateway isn’t the solution you’re looking for.

Here’s how to think about GTG vs GTM: GTM is the management layer — it controls what data you collect and when. GTG is the routing layer — it controls where those signals travel on the network after collection.

GTM and GTG are also complementary. You configure Google Tag Gateway from inside GTM, in the Admin panel under Google Tag Gateway. If you set up GTG, you don’t replace GTM. Rather, GTG is a capability you enable within your existing GTM setup, and it applies automatically to all Google destinations in that container.

Here’s how I go about answering this question when working with a client.

If you’re running client-side GTM with GA4 and/or Google Ads, Google Tag Gateway is worth trying out. It’s free, it requires no changes to your tag configurations (everything stays in GTM as-is), and the setup time is pretty minimal. For a standard WordPress or other CMS site, I’d look at this fairly soon.

If you’re on Shopify, this is more complicated. Shopify manages its own CDN and doesn’t expose the CDN layer for custom proxy configuration the way a standalone Cloudflare setup would. Getting Google Tag Gateway running on Shopify typically means routing all your Shopify traffic through Cloudflare as a proxy, and that’s a bigger infrastructure decision than just enabling a feature. For Shopify merchants who want first-party routing benefits, server-side GTM with a managed hosting option is usually the better call.

If you already have server-side GTM running with a custom loader set up, you’re likely already getting similar (and likely greater) benefits through that setup. You likely don’t need Google Tag Gateway.

If you need more than what Google Tag Gateway supports, such as non-Google tracking, and you want to benefit from first-party routing, or you need extended cookie lifetime for better Safari attribution, then it’s time to look at server-side GTM. sGTM works for any vendor, gives you server-side cookie control, and lets you process or filter data before it leaves your infrastructure. The tradeoff is cost and complexity: you’ll have to host sGTM somewhere (which has a cost), and the initial setup is more involved than setting up GTG.

Before making that decision, I’d suggest reading what you actually need before going server-side to get a clearer picture of what’s involved.

If your focus is improving conversion tracking accuracy for Google Ads specifically, and you’re on client-side GTM, Google Tag Gateway is most likely the right next step.

Data collection keeps getting harder. More browsers restrict third-party signals by default, more users have blockers running, and the gap between what’s happening on your site and what your analytics actually shows keeps growing. Google Tag Gateway won’t close that gap entirely (nothing truly does!) but for the Google-specific tracking you’re already relying on, it’s a useful, free start.