Skip to content
TAGBRUT

Server-side tagging or Google Tag Gateway: which one do you need?

Guide6 min readUpdated October 27, 2026

In short

Both route measurement through your own domain, but not at the same depth. Google Tag Gateway serves Google tags from your domain through your content delivery network (CDN), such as Cloudflare: it is free on Cloudflare and requires no server of your own. Server-side tagging adds a measurement server you control, which can feed several ad platforms, at a monthly hosting cost. Neither one removes the need for consent. At TAGBRUT, we only recommend either one after putting a number on the gain.

In this guide

What each one does

Google Tag Gateway, which Google calls "Google tag gateway for advertisers", loads the Google tag from your domain and sends measurement requests to your domain, which then forwards them to Google. According to Google, this improves measurement signal recovery and data control. You turn it on through your CDN (Cloudflare, Akamai) or a Google Cloud load balancer. It only covers Google tags.

Server-side tagging adds a Google Tag Manager container that runs on a server, not in the visitor's browser. Your site sends its data to that server; you then decide what gets forwarded, and to which ad platform. Google recommends hosting it on Cloud Run, and installing it on your own domain before sending any production traffic.

Comparison

CriterionGoogle Tag GatewayServer-side tagging
What goes through your domainGoogle tags and requestsEverything you send to the server, for Google and other ad platforms
Ad platforms coveredGoogle onlyGoogle and other platforms, depending on the tag templates available
SetupSettings in Google Tag Manager (GTM) or Cloudflare; manual if you use Consent ModeServer container, hosting, subdomain, testing of every tag
Hosting costFree on CloudflareAbout $45 a month per server on Cloud Run, according to Google, with at least two servers recommended
Data controlData goes to GoogleYou filter, enrich and route data before it is sent
MaintenanceNo server to maintainOngoing: updates, server monitoring, logging costs at high volume
ConsentNo bypass; manual tagging if you use Consent ModeNo bypass; the consent state is passed to the server container

What neither one does

  • Bypass consent. A visitor who declines stays declined. Google states that turning on Google Tag Gateway changes how the Google tag fires: if you use Consent Mode, automated script setup must be turned off and the site re-tagged manually.
  • Recover declined conversions. Only Google's modeling restores part of them, provided Consent Mode runs in advanced mode and volumes are high enough.
  • Escape every Safari limit. Safari caps cookies created with JavaScript at 7 days. It applies the same cap to cookies set by a third-party server hidden behind a subdomain (a technique known as CNAME cloaking, a CNAME being a Domain Name System (DNS) record that points a subdomain to a third-party server). A measurement server hosted by a third party and connected to your domain with a plain CNAME can therefore keep the 7-day limit.

How to decide: four questions

  1. What share of your traffic comes from Safari and mobile? Check it in Google Analytics 4 (GA4). The higher it is, the more cookie lifetime weighs on attribution.
  2. Which ad platforms do you feed? If Google Ads and GA4 carry most of your conversions, Google Tag Gateway covers the need. If Meta, LinkedIn or other platforms matter, server-side tagging can feed them from a single stream, depending on the tag templates available.
  3. Do your volumes cover the cost? Server-side tagging has a fixed hosting and maintenance cost. It pays off when the conversions it recovers are worth more.
  4. Who maintains the server? A server container needs monitoring and updates. With no one to do it, an outage goes unnoticed.

How we put a number on the gain

We measure before we recommend. Over two to four weeks, we record conversions and sessions by browser and by device. We then turn on the chosen solution and compare the same period. On a site already behind Cloudflare, Google Tag Gateway comes first, because it adds no hosting cost on Cloudflare. Server-side tagging only comes next, if a measured gap remains or if several ad platforms need to be fed.

Frequently asked questions

What is Google Tag Gateway?

Google Tag Gateway, officially "Google tag gateway for advertisers", is a Google feature that serves Google tags from your own domain, through your content delivery network (CDN) such as Cloudflare or Akamai, instead of Google's domains. Measurement requests go through your domain before reaching Google. According to Google, this improves measurement signal recovery. It is neither full server-side tracking nor a way around consent.

Is Google Tag Gateway free?

On Cloudflare, yes: Cloudflare states that the feature is free and that its requests are not billed under its other products. On another CDN or a Google Cloud load balancer, the cost depends on the provider. The one certain cost is setup, especially if you use Consent Mode, Google's consent framework, which then requires manual tagging.

How much does a server-side Google Tag Manager container cost?

On Cloud Run, Google Cloud's hosting service, Google estimates each server at about $45 a month and recommends running at least two, to reduce the risk of data loss during an outage. Above one million requests a month, logging can get expensive. Specialized hosts such as Stape also offer managed hosting, at their own prices. Setup and maintenance come on top.

Can you migrate to server-side tagging without losing data?

Yes, if the move to server-side tagging (measurement through a server) happens in stages. At TAGBRUT, we first run the server alongside your existing tags. We then switch each tag over and compare it with the old one over the same period, before removing the browser version. Transaction IDs keep a sale from being counted twice during the transition. A single big-bang switch, with no comparison, loses conversions without anyone noticing.

Does server-side tagging let you skip consent?

No. Server-side tagging, measurement through a server, changes the path the data takes, not the rules that apply to it. A visitor who declines cookies must stay declined, whether measurement goes through their browser or your server. The Google tag passes the consent state to the server container, and the Google tags running there adjust the data they send. Other ad platforms must follow the choice made in the consent banner.

When to call in an expert

  • A vendor is pitching server-side tagging without quantifying what it recovers.
  • Your site runs on Cloudflare and Google Tag Gateway is not turned on.
  • You use Consent Mode and want to turn on Google Tag Gateway without breaking consent.
  • Meta, LinkedIn or other platforms are losing signal and you are considering a measurement server.
  • A server container is already running, but no one knows what it sends, or to whom.

The diagnosis is free: you get the share of signal lost by browser, the right solution and its cost, in writing, within 2 business days of account access.

For a first check in two minutes, test your site with the tracking self-check, or read your consent signals with the gcs and gcd decoder.

Get my free audit

Sources (9)
  • Google Ads Help, "Set up Google tag gateway for advertisers with your content delivery network (CDN)": measurement signal recovery, data control, Cloudflare and Akamai.
  • Google Ads Help, "Set up Google tag gateway for advertisers in the Google tag with Cloudflare": effect on how the Google tag fires, manual setup if you use Consent Mode.
  • Google Analytics Help, "Set up Google tag gateway for advertisers with Google Cloud Load Balancer".
  • Google Ads Help, "About consent mode modeling": modeling of declined conversions, volume thresholds.
  • Cloudflare documentation, "Google tag gateway for advertisers": free feature, requests not billed under other products. developers.cloudflare.com/google-tag-gateway/
  • Google for Developers, "An introduction to server-side tagging": server container, data control, installation on your own domain. developers.google.com/tag-platform/tag-manager/server-side/intro
  • Google for Developers, "Set up server-side tagging with Cloud Run": about $45 a month per server, at least two servers recommended, logging costs above one million requests a month. developers.google.com/tag-platform/tag-manager/server-side/cloud-run-setup-guide
  • Google for Developers, "Implement consent mode with server-side Tag Manager": consent state passed to the server container, Google tags that respect it. developers.google.com/tag-platform/tag-manager/server-side/consent-mode
  • WebKit, "CNAME Cloaking and Bounce Tracking Defense" (November 12, 2020): 7-day cap on cookies created with JavaScript and on cookies set by a CNAME-cloaked third party. webkit.org/blog/11338/cname-cloaking-and-bounce-tracking-defense/
Get my free audit
Your session, live
    Consent: Pending See details