content
Google Tag Gateway is that rare case where a tool is underrated and overhyped at the same time. Underrated by the businesses that genuinely need it. Overhyped in proposals that sell it as the fix for every tracking problem there is.
Every few months a client sends us a message that goes roughly like this:
“Heard about Google Tag Gateway. People say it’s new, it gets around ad blockers, and it’s free on top of that. Do we need it? And if we do, why haven’t you set it up for us already?”
It’s a good message. Good because it packs almost every common misunderstanding about GTG into three sentences. “New” – sort of. “Gets around ad blockers” – not really. “Free” – true, but that’s not the whole story. And the answer to “why haven’t you set it up” depends on things the message doesn’t mention.
So instead of writing a short reply to one client, this turned into an article on the Advantrise blog for everyone who has heard enough about GTG to be curious, but not enough to know whether it’s even about them.
What Google Tag Gateway actually is, briefly
Google Tag Gateway (it used to be called First-Party Mode) changes the route that Google tags load through and that data travels along. Instead of the browser reaching out to googletagmanager.com, requests go through your own domain, something like yoursite.com/metrics.
What changes is the domain the tag is served from. What doesn’t change is the events themselves, how they’re processed, or the tracking logic. An event is born in the browser the same way it always was. The path it takes to reach Google just looks internal now instead of third-party.
That’s everything GTG does at the level of principle. Everything else attributed to it is worth unpacking one piece at a time.
Myth one: “it blocks the ad blockers”
The most common exaggeration. GTG makes tags harder to block. It does not make your tracking invisible.
The logic behind the myth is easy to follow. Ad blockers often identify tracking by domain: they see a request to googletagmanager.com and they block it. GTG takes the third-party domain out of the equation, the request looks internal, and some ad blockers let it through.
The problem is the word “some”. Modern blockers can recognize tracking requests by more than just the domain. They look at request format, at the parameter set, at structure. A request to GTG can still be flagged as tracking even when it travels through your own domain.
GTG reduces data loss. That effect is real and it shows up in the numbers. But “reduces” and “eliminates” are different quantities, and any proposal that sells GTG as a final answer to ad blockers is describing a tool that doesn’t exist.
Myth two: “it’s the same as server-side GTM”
GTG and server-side GTM get confused constantly, because both have “first-party” attached to them. But they’re different layers of tracking work, and the difference is practical, not just terminology.
Three tools tend to get lumped together, so it helps to separate them:
- Google Tag Manager handles the logic. What to track, when a trigger fires, which events to send. This is the configuration layer.
- Server-side GTM handles processing. Data arrives at your server, and there you can clean it, modify it, enrich it, decide what gets passed along. This is the control layer.
- Google Tag Gateway handles delivery. It processes nothing. It only changes the route.
If someone tells you “we set up server-side tracking for you” and what they actually configured is GTG, then what they configured isn’t what they called it. GTG processes nothing on a server. It gives you no control over the data. It does one specific thing, and that thing is useful, but it isn’t the same as server-side.
For what it’s worth, these tools don’t compete. GTG works well alongside sGTM and complements it. It’s just a complement, not a replacement.
Myth three: “it gets around cookie consent”
This myth is the dangerous one, because there’s legal risk sitting behind it.
GTG does not bypass consent. If a user hasn’t agreed to data collection, GTG won’t make the data get collected anyway. The tool operates within the same privacy rules as ordinary tracking. It improves data delivery once consent has been given. Not before.
Reading GTG as a way to “collect more data from users who declined” isn’t just a technical mistake. It’s a route to GDPR trouble. If GTG is being sold to you with that subtext, the thing to change is your provider, not your tracking setup.
Myth four: “every site needs it now”
No. And this is the most expensive myth for a small business, because it pushes people to pay for a setup that won’t do anything.
The logic is simple. GTG recovers data that’s being lost. If your site loses very little data, there’s very little to recover. A small local business with no active advertising, minimal analytics, and traffic that comes mostly from direct visits won’t feel a difference from GTG. The setup will happen. The effect won’t.
GTG earns its place where data loss actually costs money. And that points to a specific kind of business.
So who actually needs GTG
After four myths, the constructive part. There are four situations where GTG produces a measurable result.
The first is active Google Ads spend. Google’s algorithms optimize bids and targeting based on conversion signals. The more conversions that reach the system, the more accurate that optimization gets. If you’re spending a serious budget, every lost percent of conversions means worse optimization and wasted spend. This is why accurate conversion tracking is one of the foundations of effective Google Ads management – the algorithm can only optimize on data it can actually see.
The second is a meaningful share of Safari and iOS traffic. Tracking restrictions are harshest in those environments. If a large part of your users are on an iPhone, that’s exactly where you’re losing data, and GTG closes part of that gap.
The third is multi-channel attribution. When you drive traffic from several sources and make decisions based on which channel brought what, incomplete data distorts the picture. One channel looks weaker than it is, another looks stronger. Budget gets reallocated based on an error.
Search terms report in Google Ads: the audit that saves your budget
The fourth is an existing or planned server-side GTM. Here GTG slots into the infrastructure naturally and reinforces it.
A quick example from our work. One of our clients sells a monthly subscription box for reptile care. The niche is narrow, but the audience is unusually steady. Owners of iguanas and bearded dragons buy regularly and stay for a long time. Almost all of their traffic comes from Google Ads, and around 60% of users arrive on an iPhone, because the audience skews young. Before GTG, the gap between actual payments in their billing system and conversions in Google Ads was around 18%. The algorithm was optimizing blind on nearly a fifth of the data. After GTG went live, the gap dropped to 6-7%. The rest is consent and offline factors, which GTG doesn’t address by design.
That’s what a fitting case for GTG looks like. If you don’t recognize your business in any of those four points, the tool may not be for you right now.
The setup, briefly, and why it isn’t the hard part
If you already have basic tracking through Google Tag or GTM, connecting GTG isn’t complicated. The fastest path is through Cloudflare, which has a ready-made integration. Step by step through Cloudflare it looks like this:
- In Google Tag Manager, open the Admin section and find the Google Tag Gateway block.
- Start the setup and pick Cloudflare from the listed platforms.
- Log into your Cloudflare account directly from that window.
- Choose the domain you’re connecting the Gateway for.
- Confirm the setup. Cloudflare configures the request routing automatically.
- Check the result: open the page source or the Network tab in DevTools and confirm the tag loads through an internal path on your site rather than through googletagmanager.com.
Alternatives through Google Cloud or your own proxy are more involved, and only needed for custom scenarios. For most sites Cloudflare is enough, and it’s a matter of minutes rather than days.
The technical setup is the easiest part of the whole thing. The hard part is answering the question that comes before the setup: how much data are you losing, and where. Without that number, GTG becomes a solution looking for a problem. You configured something, something started running, and whether it was worth it stays unknown, because there was no baseline.
What to do before you order the setup
Google Tag Gateway is a useful tool. Not a marketing mirage, not a cure-all. Somewhere in between, like most tools that are real.
But “set up GTG for us” is the wrong first question. The right one sounds different: how much data are we losing, on which devices, and what does that cost us at our current ad budget. The answer either shows that you genuinely need GTG, or it saves you the price of a setup that wouldn’t change anything.
At Advantrise we start with that measurement, not with the setup. We look first at the gap between actual sales and what Google Ads sees. If the gap is significant, GTG becomes one of the recommendations. If the gap is small, we say so, and we don’t sell a setup for the sake of a setup.
If you’re running ads and you’re not sure how accurate the data behind that optimization is, request a tracking audit, and we’ll start with measurement rather than with selling a tool.
Subscribe to our newsletter
