Is Google tag gateway worth setting up for B2B lead gen, and how do I set it up?
TofuAnswer by the Tofu team · checked
Set it up if your site runs behind Cloudflare, Akamai, Fastly, Amazon CloudFront, a Google Cloud load balancer or Webflow, and Google Ads bids on conversions from your website. Tag gateway serves the Google tag from your own domain. It's free on Cloudflare and Webflow, and Google says advertisers who switch see 14% more observed conversions on average. You start it in your Google tag or Tag Manager container, under Admin, then Google tag gateway. Wait if most leads reach Google Ads as CRM imports, or you can't change your CDN. It covers Google's tags only, not LinkedIn or Meta.
As of October 2026.
Quick answer by situation
| If you… | Use | Why |
|---|---|---|
| Are deciding whether it's worth it | Google's numbers, read as averages | Cheap to try, but Google counts observed conversions, not pipeline |
| Run your site on Cloudflare, Akamai, Fastly or a Google Cloud load balancer | The automated setup in your tag's Admin screen | Google adds the routing for you |
| Use Amazon CloudFront, Webflow or another CDN | Tag Assistant's CloudFront flow, Webflow's built-in support, or self-service setup | Self-service works with any CDN or load balancer that can forward a path |
| Already run server-side Tag Manager, or are choosing between the two | Both | They do different jobs, and Google recommends combining them |
| Send most conversions to Google Ads from your CRM | Enhanced conversions for leads first, then tag gateway | Tag gateway only changes the tag on your site, not your uploads |
| Can't change your CDN, or your forms sit on another domain | Skip it for now | Without a supported route, Google says you can't adopt it |
If you are deciding whether it's worth it
With tag gateway, Google says, "your website loads the Google tag from your first-party domain. When the tag fires, some measurement requests will be sent to Google using your first-party domain." You reserve a path on your site, such as /metrics, and your CDN or load balancer forwards it to Google. It works with the Google tag, Tag Manager containers and Floodlight tags. It was called first-party mode until May 8, 2025.
Google has published three sets of numbers:
| Google's claim | Where Google said it | What it measures |
|---|---|---|
| "11% uplift in signals" | Tag gateway announcement, May 2025 | Google tag script loads with and without tag gateway, April 9 to 16, 2025 |
| 14% more observed conversions on average, and up to 7% lower cost per acquisition | Data Strength Best Practices, Google Ads Help | The 14% footnote reads "Google Internal Data, Global, Finance, July-Dec 2024 vs Jan-June 2025." The CPA footnote compares advertisers that had enhanced conversions and added tag gateway with those that had enhanced conversions only, March 2025 to February 2026 |
| "Over 20% conversion uplift" in Demand Gen campaigns | Google Ads & Commerce blog, October 13, 2026; the Data Strength page repeats it | Google internal analysis, June 3 to 17, 2026 |
How to read them for B2B lead gen:
- They are Google's averages, not B2B or lead gen results.
- They count conversions Google observes. More observed form fills don't mean more pipeline.
- Small numbers move slowly. At 20 form fills a month, a 14% lift is about three more, which is hard to spot.
- Google doesn't say tag gateway gets past ad blockers or browser privacy features. Its pages talk about "resilience against signal loss" and "signal measurement recovery." For what Safari 27 did to tags, see Is Safari 27 breaking my LinkedIn, Google or Meta conversion tracking?.
The cost is low on most routes. Cloudflare says tag gateway is free, and its requests don't count toward billing for its other products. Webflow turns it on free of charge. On Google Cloud you pay standard load balancer usage, and Google says Google Ads covers any extra processing costs. On Akamai, Google says serving costs are waived only if you use Akamai's native tag gateway template. Google gives no cost for Fastly or CloudFront, so check your CDN contract.
If your site runs on Cloudflare, Akamai, Fastly or a Google Cloud load balancer
Use the automated setup. Google connects to your CDN account or Cloud project and adds the routing, with no change to the tag code on your pages.
- Open your tag's Admin screen. In Tag Manager, open the container and go to Admin. In Google Ads, click the Tools icon, then Data manager, then Manage under "Google tag", then Admin.
- Select Google tag gateway, then Continue.
- Enter your site in Scan your site, select Scan and confirm the CDN it found. If yours isn't shown, select Show all platforms.
- Confirm the measurement path. By default it's a mix of four letters and numbers. A custom path must not already be in use on your site.
- Sign in to your CDN or Google Cloud account and grant access.
- Choose the domains to turn on, select Done, then Complete setup.
- Test it. Open Tag Assistant, browse your site, and check Summary > Output > Hits Sent: hits should go to your measurement path. A working domain shows the status First-party.
Each automated setup supports one tag per domain. For several tags, put them in one Tag Manager container or use the self-service setup. What each provider needs:
| Provider | What you need | Notes |
|---|---|---|
| Cloudflare | A Cloudflare role of Super Administrator, Administrator or Zaraz Admin, or Domain Administrator if you use domain-scoped roles | Cloudflare applies it to the whole zone, including every subdomain |
| Akamai | Admin permissions on your Akamai account | Google added Akamai on January 29, 2026, and the automated integration on May 14, 2026 |
| Fastly | A Fastly login that can grant Google permission | Google's release notes call the integration available from May 14, 2026, but its Tag Manager help page for Fastly still says it's in beta |
| Google Cloud | The Google Tag Gateway Admin role in your Cloud project, publish permission on the Tag Manager container, and all site traffic on a Global External Application Load Balancer | Generally available since June 1, 2026. The classic Application Load Balancer isn't supported |
If the Cloudflare setup keeps failing, Google suggests setting it up from the Cloudflare dashboard instead, or using the self-service steps.
If you use Amazon CloudFront, Webflow or another CDN
- Amazon CloudFront. Since June 3, 2026, Tag Assistant walks you through it. Scan your site from the Google tag gateway screen, then select Set up with Tag Assistant. You need the Tag Assistant Chrome extension, a CloudFront distribution for the site and access to your AWS account. At the end, you replace the tag script on every page with the one Tag Assistant gives you.
- Webflow. If you added your Google tag ID in Webflow's settings, republish the site, and Webflow turns tag gateway on through its CDN. It doesn't work for tags added as custom code, or for exported sites hosted elsewhere. The Google tag gateway section of your tag's Admin screen should say "Active"; Google says "Incomplete" likely means the tag also runs on other domains.
- Any other CDN, a load balancer, or several tags. Use Google's self-service setup. It has steps for Google Cloud, Cloudflare (using Snippets, on Pro plans and higher), Akamai, Amazon CloudFront, Fastly and "Other":
- Reserve one path for each Tag Manager container or standalone tag. It can't be in use, can't be
/and can't be longer than 100 characters. One container covers every tag inside it. - Route that path to your tag's endpoint (for example
G-12345.fps.goog), override the Host header to match, forward all cookies and query strings, and pass the visitor's country and region in headers. - Check that
https://yourdomain/metrics/healthyandhttps://yourdomain/metrics/?validate_geo=healthyboth show "ok". - Change the tag snippet on every page to load from your path. The
<noscript>snippet isn't supported, so keep the standard one if you use it. - Test in Tag Assistant as above.
- Reserve one path for each Tag Manager container or standalone tag. It can't be in use, can't be
If you already run server-side Tag Manager
Keep it and add tag gateway. They do different jobs:
| Tag gateway | Server-side tagging | |
|---|---|---|
| What you run | A path on your CDN or load balancer that forwards to Google | A server container that you host in a cloud environment |
| What changes | Google's scripts load from your domain, and some measurement requests go through it | The browser sends events to your server, which sends them on |
| Can you edit data before it's sent | Google's docs describe no way to. It drops any non-Google first-party cookies forwarded through it | Yes. You can screen, validate and change data, and remove personal information |
| Which platforms | Google's tags | Google and third-party endpoints |
Google recommends doing both "for the most durable tagging setup." Its implementation flowchart says that if you use server-side Tag Manager, you turn on tag gateway within your server container.
If most of your conversions reach Google Ads from your CRM
Start with enhanced conversions for leads, then add tag gateway. If your account bids on qualified leads imported from a CRM, tag gateway doesn't touch that upload. It only changes how the Google tag on your site loads and sends data, including the tag that captures form data for enhanced conversions for leads. Google's 7% CPA figure is measured on top of enhanced conversions. For imports, Google also suggests capturing GBRAID with the GCLID when the GCLID "is at risk of being dropped."
If you can't change your CDN, or your forms live on another domain
Skip it for now. Google's implementation flowchart checks for server-side Tag Manager, a Google Cloud load balancer, Webflow, or a CDN you have login credentials for. If you have none of them, it ends with "You are unable to adopt Google tag gateway for advertisers." Tag gateway also works only on the domains you set it up on, so a demo form or thank-you page on a domain you don't route, such as a hosted landing page tool, won't go through it.
What to avoid
- Picking a path that's in use. Google warns that the setup "reroutes all traffic with the chosen path."
- Ignoring consent. Google says turning it on "affects Google tag firing behavior." If your tags depend on consent choices, use consent mode and recheck your consent settings after setup. On Akamai, Google says to turn off automated script setup if you use consent mode.
- Deleting in a hurry. Deleting the setup in Tag Manager turns tag gateway off for every active domain.
- Changing tags you haven't checked. Make sure your conversions fire correctly first: see how to check that conversion tracking works on Google Ads, LinkedIn and Meta.
Sources (21)
- What is Google tag gateway for advertisers? (Google for Developers), checked October 26, 2026
- Set up Google tag gateway for advertisers, in-UI setup (Google for Developers), checked October 26, 2026
- Set up Google tag gateway for advertisers, self-service setup (Google for Developers), checked October 26, 2026
- Google tag gateway guide (Google for Developers), checked October 26, 2026
- Release notes for Google Tag Manager (Tag Manager Help), checked October 26, 2026
- Data Strength Best Practices (Google Ads Help), checked October 26, 2026
- Build your data strength with October's Demand Gen drop (Google Ads & Commerce blog, October 13, 2026), checked October 26, 2026
- Enhance your conversion measurement and ad performance with Google tag gateway for advertisers (Google Ads Help, May 2025), checked October 26, 2026
- Set up Google tag gateway for advertisers in Google Tag Manager with Cloudflare (Tag Manager Help), checked October 26, 2026
- Set up Google tag gateway for advertisers with your content delivery network (CDN) (Tag Manager Help), checked October 26, 2026
- Set up Google tag gateway for advertisers using Akamai (Tag Manager Help), checked October 26, 2026
- Set up Google tag gateway for advertisers in Google Tag Manager with Fastly (Tag Manager Help), checked October 26, 2026
- Set up Google tag gateway for advertisers with Google Cloud Load Balancer (Google Ads Help), checked October 26, 2026
- Set up Google tag gateway for advertisers in Amazon CloudFront with Tag Assistant (Google Ads Help), checked October 26, 2026
- Set up your Google tag with Webflow (Tag Manager Help), checked October 26, 2026
- Google tag gateway for advertisers implementation flow (Google Ads Help), checked October 26, 2026
- Google tag gateway cookie handling (Google Ads Help), checked October 26, 2026
- Client-side tagging vs. server-side tagging (Tag Manager Help), checked October 26, 2026
- About enhanced conversions (Google Ads Help), checked October 26, 2026
- Set up offline conversions using GBRAID (Google Ads Help), checked October 26, 2026
- Google tag gateway for advertisers (Cloudflare docs), checked October 26, 2026