Skip to content
GetProfit
Log in

← All terms

Google tag gateway

Google tag gateway for advertisers is a setup that loads Google's measurement tags from the store's own domain and sends some of their requests through it.

How it works

Normally the page loads the Google tag from a Google domain, and the tag reports straight to Google. With the gateway, the store reserves an unused path on its own domain, such as /metrics. Its CDN, load balancer or web server forwards that path to Google’s endpoint and adds the visitor’s approximate location in request headers. The page then loads the tag from the store’s domain, and Google says some measurement requests go through it.

One path serves one Google Tag Manager container with all its tags, or one standalone tag such as a GA4 tag. Each further container needs its own path.

Google lists an interface-based setup for Cloudflare, Akamai, Fastly and Google Cloud. Cloudflare says the gateway is free to use. Google recommends it “for the most durable tag configuration” and advises adding server-side tagging on top (what each one recovers).

Where you see it

  • Cloudflare dashboard: the Google tag gateway page, where you switch it on and enter the tag ID and path (setup via Cloudflare).
  • Browser: /metrics/healthy on your domain returns “ok” when routing works. /metrics/?validate_geo=healthy checks the location headers.

Example

Example store, not client data.

The tableware shop runs on Cloudflare and has one Tag Manager container, GTM-ABC123, with its GA4 and Google Ads tags. It reserves /metrics, so the container loads from the shop’s own domain and both tags use that route. A second container would need a second path, such as /m2.

Not to be confused with

  • Server-side tagging — a server container you control that receives measurement data, runs its own tags and decides where to send it. The gateway only forwards the tag’s requests to Google.
  • Enhanced conversions — hashed customer data, such as an email address, added to a conversion. The gateway changes where the tag loads from, not what it sends.

Right and wrong readings

  • Wrong: “With the gateway on, our duplicate orders and wrong values are fixed.” Right: it changes the route, not the content. A duplicate or wrong purchase still arrives as before.

Sources