Google tag gateway on Webflow: what it does, how to set it up, and what to check.

What is Google tag gateway?

Google tag gateway (GTG), officially Google tag gateway for advertisers, is a Google feature that lets you "deploy a Google tag using your own first-party infrastructure, hosted on your website's domain." Your Google tag snippet then loads its script from your first-party domain instead of a Google domain, and some measurement requests go to Google through your domain too. Google's own summary: "Serve scripts and send measurement in a first-party context."

You can run it on infrastructure you already have: a content delivery network (CDN), a load balancer, or a web server that can forward requests to Google. Google's announcement page, last modified September 16, 2026, describes it as "upgrading your tags to serve from your site's own server to improve performance and resilience." It lists in-product integrations with Google Cloud (beta), Fastly, Akamai, Webflow, Duda, and Cloudflare, and says the upgrade "requires no changes to the existing tag code."

What it does not do matters as much:

• It covers Google tags, such as Google Analytics 4 (GA4), Google Ads, and a Google Tag Manager (GTM) container, not non-Google tags such as the Meta Pixel or the LinkedIn Insight Tag.
• It is not server-side tagging, and not a full replacement for server-side GTM. There is no server container to configure, and the tags still send their data to Google.
• It does not change whether you need consent. Your consent banner and consent mode settings still apply.

Our Webflow analytics guide covers where the gateway fits in a full measurement setup. This post covers turning it on, checking it, and the consent caveats.

What does Google tag gateway change for your data?

Google tag gateway changes the route your measurement data takes, not what you collect, and Google reports more measured signals as a result. When it launched the feature in May 2025, Google reported an 11% uplift in signals compared with tags not using the gateway, based on Google tag script loads in April 2025. Its current page says advertisers who adopted the gateway "on average observed conversions uplift of 14%" and saw "up to 7% lower Cost per Acquisition." Webflow's footnote describes that comparison as against advertisers using enhanced conversions without the gateway.

Read those as averages reported by the vendor, not a forecast for your site. Results vary, and a B2B SaaS site with low conversion volume may not see a measurable change for weeks. Google's announcement pages talk about performance and resilience, not about ad blockers or browser restrictions, so don't plan around the gateway as a fix for either.

Two other changes are easier to count on:

1. The user's browser makes fewer direct requests to Google's domains, because the script and part of the measurement traffic run through your website's server or CDN.
2. Google and Webflow both say tags deployed with the gateway get confidential computing by default, which they present as added protection for personal data.

For Google Ads, more accurate conversion data feeds automated bidding, especially alongside enhanced conversions. For Google Analytics, the aim is more complete event data and better data accuracy, which matters most when key conversions, like demo requests, are few.

How do you enable Google tag gateway on a Webflow site?

On Webflow hosting, you don't configure Google tag gateway yourself. Webflow's page, updated September 16, 2026, says it runs behind the scenes for tags added through the native Google tag integration in Site settings, and sites that already use the integration activate it on their next publish.

Path A, a site with no Google tag yet:

1. Copy your Google tag ID.
2. In Webflow, open Site settings, then Apps & Integrations, and find the Google tag section.
3. Click Settings, paste the tag ID, name it, and save changes.
4. Publish the site.
5. In Google Tag Manager, open Google tags, choose your tag, and go to Admin, where you find Google tag gateway. Confirm the status reads Active.

Path B, a site with the tag pasted into custom code:

1. In Site settings, open Custom code, copy your tag ID, and back up the full snippet.
2. Add the tag ID under the Google tag settings in Apps & Integrations. You can add more than one ID, for example a GTM container and a Google Ads tag.
3. Back in Custom code, remove the legacy tag snippets from the head and the body noscript section. Keep event snippets, such as conversion or form submit code, if you still use them.
4. Publish to the webflow.io staging domain and test with Google's Tag Assistant before you publish to production.

Two limits, as of October 2026: the automatic setup only covers Webflow hosting. To implement Google tag gateway on an exported or self-hosted site, follow Google's manual setup through a CDN, load balancer, or web server; for sites behind Cloudflare, Google announced a one-click integration with Cloudflare in May 2025. And Webflow lists support for its Google Ads app in the native integration as "coming soon."

How do you check that Google tag gateway is working?

To confirm Google tag gateway is working, check three things after you publish: the gateway status in Tag Manager reads Active, the tag script loads from your own domain, and your GA4 events and Google Ads conversions still arrive. Then compare a few weeks of data with the weeks before the change. To see the script source, open the Network tab in your browser's developer tools, filter by your tag ID, and reload the page.

The duplicate check matters most during a migration. A tag left in custom code while the same ID also loads through the integration can send duplicate page views and conversions.

How does Google tag gateway work with consent mode?

Google tag gateway changes where Google tags load from, not what they are allowed to do. Consent mode and your consent banner still govern data collection, meaning what the tags may store and send. Google's documentation is direct: "You are responsible for obtaining users' consent on your website or app."

The two consent mode setups behave differently:

• Basic consent mode stops Google tags from loading until the visitor responds to your banner.
• Advanced consent mode loads Google tags right away, and while consent is denied, "the Google tags send measurements without cookies."

Webflow recommends one of two setups with the gateway: advanced consent mode with a global default of denied, or a Tag Manager container that fires tags based on consent state, often through your consent platform's templates. Either way, set the defaults before any tag fires, and check that a denied state really stops cookies in your browser's storage panel.

Two caveats to settle with whoever owns privacy at your company:

1. Your privacy notice should describe Google measurement on your site, including that requests pass through your domain.
2. Routing tags through your own domain must not be used to get around a visitor's choice. Treat a denied state the same way with or without the gateway, and get legal review for the regions you sell into.

Our guide to Consent Mode v2 on a Webflow site walks through the banner and default settings in detail.

Google tag gateway vs server-side GTM: which do you need?

For most B2B SaaS marketing sites on Webflow, start with Google tag gateway, because Webflow runs it for you. Add server-side GTM, often called server-side tracking, when you need data control over what leaves your site, want to send first-party data to other vendors, or must remove personal data before it reaches anyone. Both are upgrades on a standard client-side setup, where the browser loads tags from Google and sends data straight to Google.

Google treats the two as steps that work together. Its gateway page lists two steps for server-side setups, mapping a custom domain and loading first-party scripts with the gateway, and says: "We recommend you complete both steps for the most durable tagging setup." Google's server-side documentation also says only you have access to the data in the server "until you choose to send it elsewhere."

We build Webflow sites for B2B SaaS companies and offer Webflow SEO, so we have an interest in the topic. Our growth services cover SEO, GEO, and CRO for B2B SaaS sites.

Questions about Google tag gateway