Server-side GTM in 2026: why (and how) to make the move

Draft — reviewed and completed by Yoann before publishing.

Browser-side tracking leaks everywhere: ad blockers, Safari’s ITP capping cookie lifetime at 7 days (or 24 hours), extensions, and increasingly restrictive consent. The result: a chunk of your conversions never reaches the ad platforms. Server-side GTM (sGTM) is today the most solid answer to that problem.

The problem: client-side collection

When everything runs through the browser, you depend on an environment you don’t control. Requests to google-analytics.com or facebook.com are easy targets for blockers, and cookies set by third-party JavaScript are the first to go.

What server-side GTM really is

sGTM moves collection onto your server (a GTM container running on Google Cloud, Addingwell, Stape…). The browser sends events to your domain, and your server relays them to GA4, Meta CAPI, Google Ads, and so on.

The concrete benefits:

• First-party cookies set over HTTP server-side → restored lifetime.
• Data control: you decide what leaves, where it goes, and in what shape.
• Performance: fewer third-party scripts in the browser.
• Resilience: your collection endpoint is on your domain, not a URL blocked by default.

The steps of a clean migration

1. Map what exists: which tags, which events, which critical conversions.
2. Deploy a server container and a collection subdomain (gtm.yourdomain.com).
3. Duplicate then switch tags one by one, keeping client-side running in parallel while you compare.
4. Reconcile: confirm server-side conversions match (or beat) client-side.
5. Retire the redundant client-side tags gradually.

Pitfalls to avoid

• Migrating in one shot with no comparison phase.
• Forgetting deduplication (the same purchase counted twice, via client + server).
• Neglecting consent: sGTM does not exempt you from Consent Mode (see the dedicated post).

The checklist

• First-party collection subdomain
• Consent Mode v2 wired upstream
• Deduplication (event_id) in place
• Conversions reconciled vs client-side
• Server error monitoring

Server-side isn’t a fad: it’s become the foundation of reliable measurement. Done well, it recovers conversions you thought were gone — without breaking GDPR.