GTM Server-Side is an architecture with distinct components that each require separate configuration. The full guide lives at GTM Server-Side architecture and complete setup guide. These notes break that guide into navigable pieces.
Start Here
GTM Server-Side Data Flow — How the architecture works: the browser-to-server-to-vendor request flow, multiplexing, and the four component types (Clients, Tags, Triggers, Variables/Transformations). Read this before anything else.
GTM Server-Side Cloud Run Deployment — Deploying the server container on Google Cloud Run: automatic vs manual provisioning, production configuration (CPU allocation, instance counts, the preview server requirement), custom domain setup, and multi-region architecture.
Vendor Integrations
Server-Side Cookies and Safari ITP Bypass — The FPID mechanism that sets first-party cookies via HTTP header, Safari 16.4’s IP address check that breaks many CNAME-based deployments, and three approaches that solve it (First Party Mode, reverse proxy, Stape Cookie Keeper).
Meta CAPI Server-Side Setup — Event deduplication with shared event_id, Event Match Quality scoring and user data mapping, forwarding _fbp and _fbc cookies, and consent enforcement for non-Google vendor tags.
Google Ads Enhanced Conversions Server-Side — The Conversion Linker tag and FPGCLAW cookie, Enhanced Conversions user data setup, and what realistic conversion uplift looks like.
Operations
GTM Server-Side Hosting Costs: Self-Hosted vs Managed — Cloud Run pricing by traffic tier, the Cloud Logging cost trap (often more expensive than compute), and a comparison of managed alternatives: Stape.io, Addingwell, and Cloudflare Zaraz.
GTM Server-Side Hosting: Decision Framework — How to choose between Cloud Run, AWS ECS Fargate, Azure App Service, and managed providers based on your existing infrastructure, operational capacity, and traffic volume.
GTM Server-Side Hosting on AWS — ECS Fargate architecture and cost breakdown, why the NAT Gateway makes AWS more expensive than it appears, where Savings Plans flip the economics, and why Lambda is incompatible.
GTM Server-Side Hosting on Azure — App Service tiers and SSL configuration, Container Apps as a Cloud Run-like alternative, and why Azure Functions won’t work.
GTM Server-Side Managed Hosting Providers — Stape (including Cookie Keeper and Custom Loader), Addingwell, TAGGRS, and Cloudflare Zaraz — what each includes, where each is the right fit.
GTM Server-Side Common Failures — Ten implementation mistakes across the full stack: missing custom domains, consent signals not flowing, the case-sensitive Client Name trigger trap, missing Meta deduplication, IP mismatch undermining FPID cookies, and duplicate tag implementations.
Related Context
These notes provide background for understanding why server-side tracking matters:
- Browser Cookie Restrictions in 2026 — Why client-side tracking misses 20-40% of visitors
- Consent Mode Server-Side GTM Propagation — How consent signals travel via
gcs/gcdparameters and why non-Google tags need manual consent enforcement - Identity Resolution Ad Measurement — What server-side tracking doesn’t solve (cross-device, cookie deletion) and what fills the gap