Client-side tracking — a tag in the browser sending hits to Google — is how nearly everyone starts, and for many sites it remains enough. But browsers are an increasingly hostile place for measurement: ad blockers, tracking prevention (ITP), consent-driven gaps and slow third-party scripts all eat data before it leaves the device. Server-side tagging exists to take the measurement hop out of the browser’s hands.
How server-side tagging works
With server-side GTM (sGTM) you run a second container, not in the page but in a cloud environment you control — typically on your own subdomain like gtm.yoursite.com. The browser sends a single stream of events to that endpoint; the server container then cleans, enriches and forwards them to GA4, Google Ads, Meta’s Conversions API and anything else — server to server.
Because the endpoint lives on your own domain, its requests are first-party: less likely to be blocked, unaffected by third-party cookie restrictions, and under your control. You decide what each vendor receives — stripping PII before it ever leaves your infrastructure, which is a genuine privacy and compliance win rather than just a data-recovery trick.
Client-side
Server-side
One first-party stream out of the browser; the fan-out to vendors happens on infrastructure you control.
data direction →
Google Tag Gateway
Tag Gateway is Google’s lower-effort sibling to full sGTM: instead of operating a tagging server, you route Google’s scripts and hits through your own domain via your CDN (Cloudflare and others have one-click integrations). You get the first-party delivery benefit — scripts served from your domain, fewer blocked hits — without maintaining a container, but also without sGTM’s transformation and multi-vendor routing powers.
Where the Measurement Protocol fits
The Measurement Protocol is the third door into GA4: a plain HTTP API for sending events from any backend — no browser, no tag. Its natural jobs are offline and out-of-band conversions: a subscription renewal, a refund, a call-centre sale, a point-of-sale purchase. Events need the client_id from the user’s original browser session to stitch to a real user, which is why the usual pattern is capturing that id into your CRM at form-submit time.
When to bother
A rough ladder. Stay fully client-side while your decisions survive a 10–15% data haircut. Add Tag Gateway when blocked hits start to bite and you want a cheap first-party win. Move to sGTM when you have meaningful paid spend to protect (Conversions API destinations alone often justify it), PII you must control, or an engineering team that can own one more piece of infrastructure. Add Measurement Protocol whenever revenue happens away from the website. The costs are real — hosting, maintenance, debugging becomes two-step — so let the value of recovered and protected conversions make the case.