Google tag gateway for UK shops: first-party tagging without the jargon

You've spent money on Google Ads, a sale comes through, and the conversion doesn't show up in the account. Or Analytics looks quieter than the order list. One common reason is that the shop is loading its tracking from a Google domain, and browsers or privacy tools treat that as a third-party request. Some of those hits never arrive.

The short answer: Google tag gateway serves your Google tag from your own shop domain, so more of those measurement requests look first-party. The official name is a mouthful, Google tag gateway for advertisers, but the idea is straightforward.

What is Google tag gateway?

It is a way to deploy your Google tag using your own site, on your own domain. The tag still talks to Google. It just takes a first-party route to get there.

In the usual setup, the page asks a Google domain for the tag. When the tag fires, it sends measurement straight back to Google. With the gateway in place, the page loads the tag from a path on your shop, and some of the measurement requests go to Google through that same first-party domain. You do this with a CDN, load balancer or web server you already have. Google's setup guide walks through the options.

It is not Google Tag Manager

People mix these up, and the names don't help.

Google Tag Manager is the box where you decide which tags fire, and when. You still need that, or a Google tag on the page (a G- or AW- ID), before the gateway can do anything.

The gateway does not replace Tag Manager. It changes how those tags are served, and how some of the hits travel: from your own domain, first-party, often through Cloudflare or another CDN.

Think of Tag Manager as the list of tools in the warehouse. The gateway is the loading bay on your own site. You still need the list. The loading bay is what sends the traffic out under your own name.

That first-party route is the point. More of the events you think you are collecting should actually arrive. It is not a promise that every blocker will give up, and it will not repair a purchase event you never set up.

Who should bother

It's worth a look if you already have a Google tag or a Tag Manager container, and you spend on Google Ads or rely on GA4 for conversions. You also need something in front of the shop that can forward requests, usually a CDN or a load balancer.

If you are not running ads, and your numbers already match the till, you can leave it. The gateway will not fix a broken tag, a missing purchase event, or a cookie banner that blocks everything before anyone clicks Accept. For the wider conversion picture, speed, checkout and the product pages still do more of the heavy lifting.

Google has said advertisers who set up the gateway saw an 11% uplift in signals, measured on tag script loads from 9 to 16 April 2025. Cloudflare, which launched the integration with Google, has said early testers saw an average 11% uplift in data signals. Those are figures for signals, not a guarantee that your conversion rate will rise by 11%. Treat them as a reason to test, not a forecast.

You also need the right kind of hosting in front of the shop. A store already proxied through Cloudflare can usually use the toggle we describe below. A shop on a platform's own hosting, with no CDN of your own, may not get that one-click path. Don't force a proxy onto a platform that does not support it. Ask whoever looks after the hosting first.

How to switch it on

If the shop is on Cloudflare, this is the straightforward route. Cloudflare's docs say the feature is free to use, and that requests through the gateway do not count towards CDN, WAF or Bot Management usage.

You can turn it on in Tag Manager or in the Cloudflare dashboard, and they lead to the same result. In Tag Manager, go to Admin and open Google tag gateway, then follow Google's Cloudflare walkthrough for the clicks. You'll sign in to Cloudflare with an account that can administer the zone, pick the domains, and choose a measurement path that is not already used on the shop. You can do the same from the Cloudflare dashboard: turn on the toggle, add your Google tag ID and an unused path, then save. If a Tag Manager script is already on the site, the first-party tag will override it. That is expected, but it is worth knowing before you click.

If you use the Google tag directly, rather than Tag Manager, there is a matching flow in the Google tag settings. You still need a tag already on the site, a Cloudflare login, and an unused path.

Then check it. Open Tag Assistant, walk the shop, and look at Hits Sent. Those hits should go to a URL on your domain, under the measurement path you chose, not only to googletagmanager.com.

If you are not on Cloudflare

You don't have to be on Cloudflare. Google has guided setups for other CDNs and load balancers, including Akamai, Fastly, Amazon CloudFront (through Tag Assistant) and Google Cloud Load Balancer, plus a self-service setup for anything else that can forward requests. In every case you reserve an unused path on your own domain and forward those requests.

Google's recommended "most durable" setup later adds server-side Tag Manager on a second path, so you can tidy and control the data before it is forwarded. That is useful, and it is a bigger job. You do not have to do both on day one.

One practical catch, from Google: with the gateway, Google may see your CDN's IP address rather than the visitor's, unless the CDN sends location headers. That can skew region reports, and it can confuse region-specific Consent Mode defaults. The official one-click integrations are meant to handle this for you.

If you sell to customers in the European Economic Area, there is one more wrinkle: Google says Analytics measurement from those visitors goes straight to Google's regional endpoints, bypassing the gateway, while Google Ads conversion hits still go through it. The detail is in Google's note on how the gateway sets location.

Consent still applies

This is the bit people hope they can skip. You can't.

Serving the tag from your own domain does not make those cookies strictly necessary. Advertising cookies still need a genuine choice before they are set.

Since 5 February 2026, PECR has a narrower exception for some statistical analytics, but only if that is the sole purpose, you tell people clearly, and they have a simple, free way to object. It does not cover advertising. For shops using the gateway for Google Ads or richer measurement, the cookie banner still has to work.

The Information Commissioner's storage and access guidance is the place to start, and the exceptions sit in Schedule A1 of PECR. We also have a wider practical GDPR overview if you want the rest of the picture.

Google is explicit on this point: turning the gateway on affects how the Google tag fires. If consent already changes how your tags fire, adopt Consent Mode and review the settings so those choices are still respected.

The gateway also has its own cookie rule. Google says it uses only Google first-party cookies through the gateway, and that any other first-party cookies forwarded that way are dropped. That is about what Google keeps. It is not a substitute for your banner, and it is not a reason to collect more than you need.

Common questions

Is Google tag gateway the same as Google Tag Manager?

No. Tag Manager decides which tags run. The gateway is how those tags are served from your own domain, and how some of the measurement is sent.

Do I need a developer?

If the shop is already on Cloudflare and the tag is healthy, an admin who can log into both Tag Manager and Cloudflare can usually do this without a code change. Other CDNs, or a self-service setup on a load balancer, are more likely to need whoever looks after the site. We help with that kind of work on eCommerce builds when it is part of a wider shop project.

How do I know it is working?

In Tag Assistant, hits should be sent to your measurement path. In the Google tag gateway screen, the domain should show as active and first-party. Give reports a little time after that, and compare conversions against real orders rather than hoping for a headline jump.

The bottom line

If your conversion numbers have looked thin compared with real sales, and the tag is already on the site, this is one of the first things worth checking. Keep the cookie banner honest, use Consent Mode, and test the setup in Tag Assistant before you trust the new numbers.

If you want a hand setting it up on a UK shop, get in touch, we're happy to talk it through.