Google tag gateway vs server-side tagging: how to choose

Google tag gateway and server-side tagging both make Google Ads tracking more first-party, and a managed endpoint is the third route merchants ask about. The gateway changes where Google’s tag is served from, a server container changes where the data is processed, and a managed endpoint hands the whole server to someone else.

Moving Google’s tag to your own domain does not get it past ad blockers: they block Google tag gateway and server-side Google Tag Manager setups. Full Signal Tracking gets through. Every Google and Cloudflare claim links to the page it comes from.

Three routes, three different jobs

Google tag gateway serves Google’s own tag from your domain. Google says it “lets you deploy a Google tag using your own first-party infrastructure, hosted on your website’s domain” (Google Tag Platform). In its setup guide, your site loads the tag from your first-party domain and “some measurement requests will be sent to Google using your first-party domain”.

Server-side tagging is a server container you run. Google describes it as processing data “on a server you control, rather than in the user’s browser” (Google Tag Platform). It runs in your own Google Cloud project or another environment, and Google strongly recommends putting it on your first-party domain.

A managed endpoint is the same idea with someone else running it. Full Signal Tracking runs a unique endpoint on your own domain and sends every purchase from there into Google Ads, with no server container for you to host. If an endpoint is ever blocked, it auto-rotates to a fresh one.

What happens when a visitor runs an ad blocker?

Ad blockers block Google tag gateway and server-side Google Tag Manager setups. Full Signal Tracking gets through, and if an endpoint is ever blocked it auto-rotates to a fresh one.

Our lab ran real browsers with real extensions on 30 September 2026. The standard Google Tag Manager, GA4 and Google Ads tags were stopped or replaced by stubs in Brave Shields, uBlock Origin Lite and AdGuard with Tracking Protection. AdGuard on its default filters and AdBlock did not block the Google Ads tag. A Full Signal-style first-party endpoint was reached in all 6 setups.

Safari lets tags load but cuts their cookies to 7 days; Full Signal’s first-party cookie lasts 30 days.

To see what a request carries, decode it in the SDK debugger.

Test what your own browser blocks →

Side by side

Sources: the Google and Cloudflare pages linked in this post, and Product Metrics’ own product facts.

You don’t have to pick one. Google documents the gateway running through a tagging server, so the first two overlap.

Cost and setup

Google documents the gateway as free on its Google Cloud load balancer integration: “The Google tag gateway for advertisers integration is free. You’ll only pay for your standard Google Cloud Load Balancer usage, such as data processing and network traffic” (Google Ads Help). Cloudflare says it “is free to use” (Cloudflare docs, updated 17 April 2026). We found no cost statement for other CDNs.

A server container comes with a stated price. Google says “Each server costs approximately $45 /month (USD)” and recommends a minimum of two instances in case of an outage (Cloud Run setup guide).

Setup differs too, as the table shows, and a server container is also a server: someone has to keep it patched, paid for and awake. Full Signal Tracking has no container to look after and is included in the Pro subscription.

What none of them fixes alone

The gateway changes where Google’s tag is served from, and only “some” requests move. Google describes it as a way to serve the tag, not to add customer data. Enhanced conversions are a separate feature, covered in enhanced conversions vs server-side tracking.

Server-side tagging is a routing and processing layer. Google lists screening and modifying incoming requests, validating and normalising data, and removing personally identifiable information before passing it on (Google Tag Manager Help). It gives no product-level view.

Full Signal Tracking covers Google Ads only. Every purchase is sent marked NEW or RETURNING, and Product Metrics delivers new-customer, profit and LTV conversions to Google Ads.

None of the three replaces consent. What you need depends on your region and your consent setup; this isn’t legal advice.

Which should you set up first?

Measure your own gap first, then choose the lightest route that closes it, changing one thing at a time.

Lost purchases skew product verdicts

Smart Bidding and your per-product decisions learn from the conversions that arrive. A product that loses purchases on the way looks worse than it is, and can end up with its priority lowered because of it.

Break-even ROAS is 1 ÷ contribution margin and POAS equals ROAS × contribution margin, so break-even POAS is 1.0 (POAS vs ROAS). The maths is in break-even ROAS per product, the break-even ROAS calculator gives each product’s floor, and Product Segmentation then segments your products by clicks and return, using ROAS straight away and POAS once margins are connected.

Measure your own gap this week

Run the ad blocker test and compare your orders with your Google Ads conversions. If purchases are missing and you don’t want to host a server, read how Full Signal Tracking works per platform; it is included in Pro and not billed separately (see pricing). Google’s pages change, so check them again in a few months.