Google tag gateway explained: what it does and who needs it

Google tag gateway, or Google tag gateway for advertisers to give it the full name, serves Google’s tags from a path on your own domain and then forwards the measurement on to Google. The browser talks to your site instead of a Google domain, which makes the measurement first-party.

It can recover some measurement that would otherwise go missing. It won’t repair a broken tag, stand in for consent or tell you whether your conversions are real, so it belongs after the basics and never in place of them.

What does Google tag gateway actually do?

On a standard set-up, a visitor’s browser fetches the tag from a Google domain and sends its measurement back to Google domains. With the gateway in place, those requests go to a path on your own domain instead, and your CDN or load balancer passes them along to Google.

The tag’s job stays the same. It measures the same events, in the same account, against the same conversion actions. What changes is the address on the envelope, and browsers and blockers can treat a request to your own domain differently from one aimed at a well-known measurement domain.

What doesn’t Google tag gateway do?

Most of the disappointment around this feature comes from expecting it to do somebody else’s job.

How do you set up Google tag gateway on Cloudflare?

Cloudflare offers this as a one-click integration on every plan, free of charge. In outline, the job looks like this.

1. Confirm the site’s traffic is proxied through Cloudflare, since the gateway works on requests passing through it.
2. Find the Google tag ID you want to serve from your domain.
3. Switch on the Google tag gateway integration in Cloudflare and choose the path it should use.
4. Decide what to do about automated script set-up, using the consent section below.
5. Load the site with your browser’s network panel open and confirm the tag requests are going to your own domain.
6. Complete a test conversion and confirm it still arrives in Google Ads.

The setting applies zone-wide on Cloudflare. If one zone covers several subdomains or sites with different tags or different consent arrangements, plan for all of them and not only the main website.

Can you use it without Cloudflare?

Yes. Google lists other routes including Akamai, Fastly, Google Cloud Load Balancer and Amazon CloudFront. The set-up varies between them and some of it is manual, so don’t assume the one-click experience carries over. If you’re not on any of these, moving your DNS or CDN purely for this feature is a much bigger decision than the feature deserves.

Does Google tag gateway work with consent mode?

It does, although the one-click path needs changing first. Google’s help is direct about it: “If you use consent mode, you must turn off automated script set up”. If you run Google Ads to UK visitors, there’s a good chance consent mode is part of your set-up, which makes the one-click option a starting point and no more.

Google’s sentence doesn’t give a reason. Our reading is that it comes down to the order of events: consent defaults have to be in place before tags run, and a script added at the CDN isn’t something your page can easily sequence. With automated set-up off, your own code or GTM has to load the tag through the gateway path, after those defaults have been set.

Your obligations stay where they were, too. Under UK PECR, non-essential cookies need active, clear consent and advertising cookies aren’t exempt, whichever domain the request happens to come from. Our Consent Mode v2 guide for UK advertisers explains how those choices reach your tags, and it’s a developer’s view and not legal advice.

What about the 11% uplift figure?

Cloudflare says early testers saw “on average an 11% uplift in data signals”. That’s Cloudflare’s figure, from Cloudflare’s early testers, and it’s the only uplift number we’re prepared to repeat.

Read the last two words carefully. Data signals aren’t conversions and they aren’t sales, so nobody should take it as a promise of 11% more of either. How much you’d see depends on your visitors’ browsers, how your site is built and how much measurement you’re losing at the moment, and very few advertisers can put a number on that last one before they start.

Who should bother with Google tag gateway?

We’d suggest it if most of these sound like your account:

• Your site already runs through Cloudflare or another supported route, so the work is small.
• Your tags and conversion actions are in good order and you trust the numbers.
• Enhanced conversions are already running properly.
• Google Ads is a meaningful channel for you, so a modest gain in signal has something to act on.

We’d leave it for now if any of these apply:

• You have duplicate conversions, broken tags or unexplained gaps between systems, as those will cost you far more than the gateway could recover.
• Your cookie banner and consent signals are still unresolved.
• You’d need to change hosting, DNS or CDN just to make it possible.
• Your conversion volumes are small enough that a change in signal would be impossible to see.

In practice the order we’d follow is correct tags first, enhanced conversions second, consent third and the gateway last. If you’re not sure about the first of those, this tracking audit checklist will show you where you stand.

Is it worth paying someone to set up?

If you’re on Cloudflare, you don’t use consent mode and your site is simple, you can probably do this yourself with the steps above. Most businesses we’d speak to aren’t in that position, because consent mode is in the mix and automated script set-up has to come off.

We set up the gateway as part of a fixed-price enhanced conversions and Google tag gateway package, through Cloudflare or whichever CDN you use, and all of it sits in your own accounts so nothing is tied to us. If you’re not sure whether your account would see any benefit, ask us on a call and we’ll give you a straight answer.