Questions & answers. GTM Server-Side, hosting and CAPI.

FAQ - server-side tagging

Answers on GTM Server-Side, hosting (Stape, GCP, Zaraz), first-party subdomain, CAPI integrations and maintenance.

9 questions in 3 categories

Server-side basics

What is server-side tagging (GTM SS)?

A separate Google Tag Manager container running on a server (Stape, GCP, Zaraz, etc.) that receives data from the web container and forwards it to vendors (GA4, Meta CAPI, Google Ads). It limits browser-side data and extends first-party cookie lifetime.

When is server-side worth implementing?

With large ad budgets, ad-blocker issues, Meta CAPI/TikTok Events API needs or requirements to limit PII in the browser. Compare solutions in the SSC catalog.

Does server-side replace Consent Mode?

No. Consent signals must be passed to the server container and honored by server-side tags. CMP + Consent Mode v2 remain required in the EEA for Google advertising.

Hosting and costs

Stape.io or Google Cloud for GTM SS?

Stape - fast start, ready templates, managed hosting from ~$17/mo. GCP Cloud Run - full control, lower TCO at very high volume, higher DevOps overhead. Use the SSC selector to match.

How much does server-side tagging cost?

Managed (Stape, Addingwell): from $0-20/mo (low traffic) to hundreds at millions of requests. GCP: Cloud Run + load balancer cost varies by region and scale. Cloudflare Zaraz uses a different Workers model. Check vendor pricing in the catalog.

What is a first-party subdomain?

E.g. ss.yourdomain.com - the server container runs on your subdomain instead of Google’s domain. First-party cookies are less likely to be blocked and may last longer.

Rollout and maintenance

How do I connect web and server containers?

In the GA4 config tag (or dedicated client) set the transport URL to your SS subdomain. The server container needs a GA4 client receiving incoming requests.

How do I implement Meta Conversions API via GTM SS?

Use a Meta CAPI template in the server container (Stape community templates or native). Required: pixel ID, access token, event_id deduplication between browser and server.

How do I audit a server-side rollout?

Use the server-side checklist (16 items): architecture, DNS/SSL, tags, consent routing, monitoring. Test in GTM Preview for both containers (web + server).

Related resources