Tag gateway or server-side GTM?

Google's free tag gateway and a server-side Tag Manager container both put tracking on your own domain. They are not the same thing. What each does, what it costs, and which one you need.

The short answer

Google tag gateway serves Google's tag from your own domain through your CDN. It is free on Cloudflare, and Google reports an average 14% conversion uplift for advertisers using it, but Google's documentation describes it for Google's own tags only. Server-side GTM is a server you control: it receives your site's events, can strip personal data, sets cookies from your own domain and forwards events to Google, Meta and others. Turn the gateway on if Google is your only ad platform; add server-side GTM when Meta or other platforms matter too. Google recommends both together.

By Yannis Spanenburg, founder of Proof of Pixel. Facts checked on 1 October 2026.

Side by side

	Google tag gateway	Server-side GTM
What it is	Loads the Google tag from your own domain through your CDN, load balancer or web server	A tagging server you control that receives events and forwards processed data
Where it runs	Cloudflare, Akamai, Fastly, Amazon CloudFront or a Google Cloud load balancer	Google Cloud Run, or a host such as Stape
Cost	Free on any Cloudflare plan; on Google Cloud, only normal load balancer usage	About $45 a month per Cloud Run server, two recommended; Stape free up to 10,000 requests, then from $20 a month
Setup	A toggle in the Cloudflare dashboard, or a sign-in from the Google tag settings	Tagging and preview servers, a custom domain, then clients and tags
Which tags	Google's tag and Tag Manager container. Meta and others stay third-party, according to Stape	Any vendor with a server tag: GA4, Google Ads, and Meta's own Conversions API tag
Cookies	Set by the script in the browser, under your domain	Set by your server on your own domain or subdomain, with full durability
Control over data	Forwards Google measurement to Google	Can remove personal data before passing anything to partners
Consent	Adopt consent mode; turn off the automated script setup if you use it	Set consent in the web container; Google's server tags respect it
Google's figure	14% average conversion uplift (Google data, July 2024 to June 2025)	No separate Google figure
History	Launched as first-party mode; renamed and opened to all on 8 May 2025	Google's Cloud Run setup guide added in November 2022

Checked on 1 October 2026 in Google's tag platform documentation and Help Center, the Tag Manager release notes, Cloudflare's documentation and Stape's price page. Google's 14% compares July to December 2024 with January to June 2025, from Google's own data.

Who should pick which

Gateway alone if

Google Ads and Google Analytics are your only paid channels
Your site already runs on Cloudflare or another supported CDN
You want better Google measurement without running a server

Server-side GTM if

You also advertise on Meta, TikTok or LinkedIn
You want to decide what personal data leaves your site
People take more than a week to buy, so cookie lifetime matters

Both if

You want the most durable setup Google describes
Ad spend justifies a small monthly hosting bill
Someone will check the tags after every site change

What the gateway changes

Normally your site loads Google's tag from Google's servers and sends measurement straight to Google. With the gateway, the tag loads from a path on your own domain, such as /metrics, and some measurement requests go through your domain before they are forwarded to Google. It started as first-party mode and was renamed Google tag gateway for advertisers on 8 May 2025, when it opened to everyone.

On Cloudflare it is a toggle, free on every plan, and applies to the whole zone: you cannot switch it on for one subdomain and off for another. Google reports that advertisers who strengthened their data with the gateway saw a 14% average conversion uplift.

What it does not change: the cookies are still set by a script in the browser, and Safari limits script-set cookies to seven days. Google's documentation describes Google's tags only; Stape, a server-side hosting company, states plainly that the Meta Pixel and other tags remain third-party requests.

What server-side GTM adds

A server container runs in your own Google Cloud project or with a host such as Stape. Your website sends events to it, and it decides what goes on to Google, Meta and others. Google's own Help Center notes you can remove personal data there before anything reaches a marketing partner, and that a server on your own domain keeps the data and cookies within that domain.

Cookies set by the server on your own domain or a subdomain get what Google calls full access to the security and durability benefits, unlike the default Cloud Run address, which can only set script cookies. And Meta maintains its own Conversions API tag for server containers, so one container can feed both ad platforms.

Our own site works this way: Google Tag Manager in the browser, a server container on our own subdomain hosted at Stape, and Meta events sent from both sides with a shared event ID.

What each costs

The gateway is free on Cloudflare, and requests through it do not count toward other Cloudflare usage. On Google Cloud the integration is free and you pay only for normal load balancer usage.

Server-side GTM costs hosting. Google estimates about $45 a month per Cloud Run server and recommends at least two, so roughly $90 a month before traffic. Stape's hosted plans start free up to 10,000 requests a month, then €20 or $20 for up to 500,000 and €100 or $100 for up to five million, billed monthly. The bigger cost is setting it up correctly and checking it after every change to the site.

Consent comes first, either way

Neither setup changes what consent requires. Google says enabling the gateway affects how its tags fire, that you should adopt consent mode if consent changes your tags' behaviour, and that the automated script setup must be turned off if you use consent mode. In a server container, consent is set in the web container, and Google's server tags respect it; tags for other vendors need their own consent triggers.

Questions about Tag gateway vs server-side GTM

What is Google tag gateway?

A Google feature that loads the Google tag from your own domain through your CDN, load balancer or web server, and sends some measurement requests through that domain to Google. It used to be called first-party mode and is free on Cloudflare.

Is Google tag gateway the same as server-side tagging?

No. The gateway re-routes Google's own tag and requests through your domain. Server-side tagging runs a container you control that receives events, can change or filter them, sets cookies from your server and sends them on to many vendors.

Does Google tag gateway help my Meta ads?

Google's documentation describes the gateway for Google's tags only, and Stape states that the Meta Pixel and other tags stay third-party. For Meta, use the Conversions API, for example through Meta's tag in a server-side GTM container.

Do I need server-side GTM if I turn on the gateway?

Not if Google is your only ad platform and you are happy with browser cookies. You need it when you send events to Meta or other platforms, want to filter personal data, or want cookies set by your own server. Google recommends using both for the most durable setup.

What does each cost?

The gateway is free on Cloudflare; on Google Cloud you pay normal load balancer usage. Server-side GTM on Cloud Run costs about $45 a month per server, with two recommended, or from free to $20 a month and up at Stape.

Is Google tag gateway the same as first-party mode?

Yes. Google launched it as first-party mode in 2024 and renamed it Google tag gateway for advertisers on 8 May 2025, when it became available to everyone for both browser and server tags.

How do I turn on Google tag gateway in Cloudflare?

In the Cloudflare dashboard, open Google tag gateway, switch it on, and enter your tag ID and a measurement path such as /metrics. You can also start from the Google tag settings and sign in to Cloudflare. It applies to the whole zone, including every subdomain.

Does the gateway get around cookie consent?

No. Google tells you to adopt consent mode if consent affects your tags, and to turn off the automated script setup when you use consent mode. The rules on what you may collect without consent stay the same.

Which fits a store, and which fits a business that runs on enquiries?

A Shopify store gets Google and Meta connections from Shopify's own apps, so the gateway is a cheap addition. A business that lives on enquiries usually runs Meta and Google together and needs to send leads from forms and the CRM, which is what a server container does well.