What Is a Server-Side GTM Container?
·
A server container is a Google Tag Manager container that runs on a server you or a managed service control, rather than in the visitor's browser, and receives events forwarded to it from a web container or sent directly via HTTP. It sits between the site and third-party endpoints, such as Meta, Google Ads, or GA4, as a first-party intermediary, letting requests to those platforms originate from your own domain and giving you a place to enrich, filter, or transform event data server-side before it's sent onward. It is a separate container type from the standard web container, with its own tags, triggers, variables, and publishing workflow.
In practice
A typical setup has the web container — running in the visitor’s browser, as with a standard GTM install — send events to the server container’s endpoint, often via a client-side GA4 or custom client configured to hit a subdomain such as https://sgtm.example.com. The server container then runs its own tags, such as a server-side GA4 tag, a Meta Conversions API tag, or a Google Ads conversion tag, that forward the event to each destination platform, now from the server rather than the browser. Because the request originates from infrastructure you control, it can attach data the browser doesn’t reliably have, such as a hashed email from your backend, and is less affected by browser-side ad blockers or Intelligent Tracking Prevention.
Common confusion
A server container is not automatically “more accurate” or a workaround for consent requirements — it still must respect whatever consent state the visitor gave, and if the browser never sends the event to the server container in the first place because a client-side tag was blocked or consent denied it, the server container has nothing to forward. It’s also not the same thing as Conversions API by itself; Conversions API is one tag that can run inside a server container, not the container itself. Running a server container requires ongoing hosting, commonly Google Cloud Run or a managed provider, and maintenance separate from the web container’s.
How to check
In GTM, container type is visible immediately on the container selection screen and in Admin > Container Settings — server containers show a “Server container URL” field the web container doesn’t have. The server container’s own Preview mode, a separate debug session from the web container’s, confirms which events actually arrive at the server and which tags fire from there.
Related entries
A server container is where a valid event_id typically gets attached to server-forwarded events, and it’s the infrastructure behind first-party tracking. For setup and hosting, see server-side tracking services.
Related entries
- Knowledge BaseWhat Is event_id? (Meta Pixel + CAPI Deduplication)What event_id is, why Meta uses it to deduplicate Pixel and Conversions API events, and where to check match status in Events Manager.
- Knowledge BaseWhat Is First-Party Tracking?What first-party tracking means technically — same-domain cookies and endpoints — and why it isn't a consent bypass.
- ServiceServer Side Tracking
Not sure whether your tracking is actually broken?
Start with a Health Check — a fast, read-only diagnosis that tells you what is wrong before you spend anything fixing it. Prefer email? Send your store URL and one sentence about what looks off.