Google tag gateway for advertisers loads your Google tag and Tag Manager scripts from your own domain, through your CDN or load balancer, instead of from Google’s domains. Google reported an 11% average uplift in signals in 2025. It is free on Cloudflare, needs no code changes, and works alongside server-side tagging rather than replacing it.
- Tag gateway serves Google tags from a path on your own domain, like yoursite.com/abc123, through your CDN.
- Google measured an 11% signal uplift in its 2025 launch data. That number counts tag script loads, not sales.
- On Cloudflare it is free and takes a few minutes from Google Tag Manager. Akamai, Fastly and Google Cloud are also supported.
- It does not replace consent, a CMP or server-side GTM. Use server-side GTM when you need to control or enrich the data itself.
What is Google tag gateway?
Google tag gateway for advertisers is a free feature that lets your website load Google’s measurement scripts from your own domain. Normally your Google tag and Google Tag Manager container load from googletagmanager.com. With the gateway, they load from a path on your site, for example yoursite.com/metrics-7f2/. Your CDN or load balancer passes those requests to Google behind the scenes.
Google launched it in May 2025 with Cloudflare as the first partner. It works with the Google tag behind Google Ads and Google Analytics 4, and with Google Tag Manager containers. You do not change your tags, triggers or conversion actions. You only change where the scripts are served from.
Why first-party serving matters
Browsers and privacy tools treat third-party requests with more suspicion than requests to the site you are on. When the tag loads from your own domain, it looks like part of your website. That can mean fewer script loads blocked, and cookies that are treated as first-party. More scripts loading means more page views, leads and purchases reach Google Ads and GA4.
| Standard Google tag | With tag gateway | |
|---|---|---|
| Script loads from | googletagmanager.com | Your domain, e.g. yoursite.com/path |
| Who serves it | Google directly | Your CDN or load balancer, forwarding to Google |
| Code changes on the site | None | None on Cloudflare; snippet path update in some setups |
| Extra cost | None | None on Cloudflare; normal traffic costs elsewhere |
| Data processing changes | No | No |
How much signal does Google tag gateway recover?
Read the footnote before you put that number in a slide. Google measured script loads: how often the tag actually loaded with the gateway versus without it. It is not 11% more conversions, and it is not 11% more revenue. It means more of your visits produced measurement data in the first place.
Independent results are smaller and vary a lot. Loves Data, an analytics training company, saw an increase of almost 7% in reported GA4 users in one real-world comparison. They also tested five ad blocker extensions in August 2025 and found the gateway did not get past any blocker that already blocked the normal setup. Your gain depends on your audience, browser mix and consent rates.
Where the extra signal comes from
- Network and privacy filters that block requests to known Google tag domains but not to your own domain.
- Browser rules that shorten or restrict cookies tied to third-party domains.
- Corporate firewalls and DNS-level filters on office networks.
That share is the ceiling of the problem, not the size of the fix. Popular extensions like uBlock Origin and Ghostery still block many gateway setups. Treat the gateway as a cheap way to recover part of the gap, not as a way around ad blockers.
Google tag gateway vs server-side GTM: what is the difference?
People mix these up all the time. The gateway changes where the script comes from. Server-side Google Tag Manager changes where the data goes and what happens to it on the way. They solve different problems, and Google recommends using both for the most durable setup.
| Google tag gateway | Server-side GTM | |
|---|---|---|
| What it does | Serves Google scripts from your domain | Receives events on your server, then forwards them |
| Can edit or filter data? | No | Yes: remove fields, enrich, hash, add CRM data |
| Works for Meta, TikTok, etc.? | No, Google tags only | Yes, with the right server tags |
| Setup time | Minutes on a supported CDN | Days, plus testing |
| Running cost | Free on Cloudflare | Hosting, about $45 per server per month on Cloud Run |
| Maintenance | Almost none | Ongoing: updates, monitoring, scaling |
For a small business, that means server-side GTM usually starts around $90 a month in hosting before anyone’s time is counted. Managed hosts exist and can be cheaper, but someone still has to build and maintain the container.
When is Google tag gateway worth it?
For most small businesses running Google Ads, the answer is yes, if you already use Cloudflare. It is free, it takes minutes, and there is little downside. The question is really whether you also need server-side tagging.
| Your situation | What we recommend |
|---|---|
| Site on Cloudflare, Google Ads or GA4 only | Turn on tag gateway. Done. |
| Site on Akamai, Fastly or Google Cloud CDN | Use the in-product setup for your CDN. |
| Shopify, Wix or Squarespace without your own CDN | Check if you can route your domain through Cloudflare. If not, skip it for now. |
| Heavy Meta or TikTok spend too | Gateway for Google, plus Conversions APIs for the others. |
| Leads close offline in a CRM | Gateway plus offline conversion imports or enhanced conversions for leads. |
| Need to strip PII, enrich events or control vendors | Server-side GTM, with the gateway in front of it. |
How do I set up Google tag gateway on Cloudflare?
The fastest route is from inside Google Tag Manager. You need admin access to the GTM container and to the Cloudflare account that manages your domain.
- 1In your GTM web container, open Admin, then Google tag gateway, and click Continue.
- 2Choose Cloudflare as your platform.
- 3Accept or set the measurement path. Make sure no real page, folder or redirect on your site already uses it.
- 4Sign in to Cloudflare and authorize Google.
- 5Pick your domain and click Complete setup.
- 6Check how your container loads. If the snippet still points to googletagmanager.com, update it to the new path or let Cloudflare inject it. Never load the same container twice.
- 7Open your site, open DevTools, go to the Network tab and confirm gtm.js or gtag.js now loads from your own domain. Confirm in Tag Assistant that tags still fire.
You can also turn it on from the Cloudflare dashboard by entering your tag or container ID and a path. Cloudflare says requests through the gateway do not count toward CDN, WAF or Bot Management billing.
Other setup options
- Akamai: supported in-product since early 2026, with automatic zone detection.
- Fastly: supported since April 2026.
- Google Cloud load balancer: generally available since June 2026.
- Any other CDN or web server: a manual setup where you proxy a path on your domain to Google. This needs a developer.
Does Google tag gateway affect consent and privacy?
No, and that is important. The gateway does not change what data is collected or whether a visitor agreed to it. Consent Mode and your consent banner work exactly as before. If a visitor declines, the gateway does not override that choice. You still need a privacy policy that explains your use of Google measurement tags.
If you serve visitors in California, other US states with privacy laws, or the EU, keep your consent setup in place and tested. A first-party path is a delivery change, not a legal basis.
How do I know if it is working?
- In DevTools, the Google scripts load from yoursite.com/your-path, not googletagmanager.com.
- Google Tag Manager or the Google tag settings show the gateway as active for that domain.
- Tag Assistant shows tags firing normally on key pages and the thank-you page.
- Over two to four weeks, compare GA4 users and Google Ads conversions with the period before. Expect a modest change, not a jump.
What Google tag gateway will not fix
The gateway helps Google see more of what happens on your site. It cannot see what happens after. If your sales close on the phone or in a CRM, Google still does not know which leads turned into revenue. That is a pipeline problem, solved with offline conversion imports or enhanced conversions for leads. It also does nothing for Meta, TikTok or LinkedIn tracking. Those platforms need their own server-side connections.
Think of tag gateway as the cheapest first step in a stronger tracking stack. Turn it on, verify it, then spend your real effort on getting sales data back to the ad platforms.
Frequently asked questions
Google does not charge for it. On Cloudflare, gateway requests do not count toward CDN, WAF or Bot Management billing, so it is effectively free. On other CDNs or load balancers you pay your normal traffic costs.
Not reliably. Some network filters only block known Google domains, so the gateway gets through those. Popular browser extensions like uBlock Origin and Ghostery blocked gateway setups in independent tests in 2025.
Only if you need to control the data: remove personal data, enrich events with CRM fields, or send events to non-Google platforms. For a small business on Google Ads and GA4, the gateway alone is often enough to start.
It can raise them modestly because more tag loads succeed. Google’s average was an 11% uplift in signals, measured as script loads. Your conversion change will usually be smaller and depends on your audience.
Only if your domain runs through a supported CDN you control, like Cloudflare, or through a manual proxy. Many hosted site builders do not let you add the path, so check your DNS and hosting setup first.
- Google Ads Help: Google tag gateway for advertisers announcement (2025)
- Google Tag Platform: Google tag gateway
- Google Tag Platform: Server-side tagging on Cloud Run
- Cloudflare Docs: Google tag gateway
- Loves Data: Google Tag Gateway setup guide, pros and cons
- PPC Land: Google tag gateway hits general availability on Google Cloud (2026)
