Recover the data consent —
and ad-blockers — take away.
A correct consent setup and modern browsers quietly delete 15–40% of your measured conversions. Server-side GTM moves tagging to a first-party server you control, so more of your real performance survives to reach Google Ads and GA4.
Client-side tags are leaking your measurement
Safari's ITP caps first-party cookies to 7 days (often 24 hours). Ad-blockers drop a large share of browser tags entirely. Consent Mode, done right, removes more. Server-side tagging is how you get the signal back — legitimately.
Resilient
First-party requests survive ITP and ad-blockers that kill third-party browser tags.
In your control
You decide what data leaves your site, strip PII, and stop over-sharing.
Better bidding
More complete, higher-quality conversion data feeds Smart Bidding and CAPI match rates.
A tagging server, done properly
First-party tagging server
A server-side GTM container on Google Cloud Run or stape.io, served from your own subdomain (e.g. sst.yourdomain.com) so requests are first-party.
GA4 + Google Ads server tags
Analytics and Ads conversions sent server-to-server, more resilient to ITP, ETP and ad-blockers than browser tags.
Meta Conversions API
Server-side Meta events (CAPI) deduplicated against the browser pixel — better match quality, less signal loss.
Consent-aware forwarding
The server honours Consent Mode state, so first-party power never becomes a compliance liability.
Payload control & enrichment
You decide what data leaves your infrastructure. Strip PII, enrich events, and stop leaking more than you mean to.
Cost & scaling setup
Right-sized Cloud Run configuration with logging and rollback, tuned so you're not overpaying for a tagging server.
Fixing consent honestly means your reported conversions drop to what you're actually allowed to measure — often a painful first look. Server-side GTM is how you recover most of it: paired with Consent Mode v2 modelling, it wins back the signal ad-blockers and browser limits were quietly deleting. You end up with numbers that are smaller, real, and finally worth bidding on.
From client-side to server-side, safely
- 1
Assess & scope
We map your current client-side tags, conversions and consent setup, then design the server container around them.
- 2
Provision the server
Stand up the sGTM container on Cloud Run or stape, map your first-party subdomain, and secure it.
- 3
Migrate tags
Move GA4, Ads and Meta to server tags with client/browser dedup, keeping consent signalling intact throughout.
- 4
Validate & monitor
Verify parity against the old setup, confirm consent behaviour, and hand over dashboards plus a runbook.
Server-side GTM, answered
No. Any advertiser losing measurement to ad-blockers and browser tracking limits benefits — which is most of them. We size the server so the cost fits an SMB budget.
It won't, and it shouldn't. Server-side GTM is consent-aware: it only forwards what the user has agreed to. It recovers signal you're legitimately allowed to measure — not signal you aren't.
They're complementary. Consent Mode v2 lets Google model the conversions consent hides; server-side GTM recovers the observed conversions that ad-blockers and ITP strip out. Together they close most of the measurement gap a correct consent setup opens.
Both work. Cloud Run gives you full control and tends to be cheaper at scale; stape is faster to stand up and manage. We recommend based on your traffic, budget and how hands-on you want to be.
Get your measurement back
Book a scoping call and we'll map what you're losing to browsers and consent — and what server-side can recover.