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.
- with its own
- tagstriggersvariablespublishing workflow
- ongoing hosting
- Google Cloud Runa managed provider
Daniil Maximkin Published Reviewed
- In practice
How does a server container work 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. Once an event arrives, the server can enrich it with permitted backend data, such as a hashed email, and control vendor delivery. The incoming request typically still comes from the visitor’s device: a first-party endpoint does not bypass consent, blockers or browser privacy protections by default. Safari also limits cookies set via third-party CNAME cloaking.
- Not to be confused with
Not to be confused with Is not Is a workaround for consent requirements still must respect whatever consent state the visitor gave Conversions API by itself a Google Tag Manager container that runs on a server you or a managed service control 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.
- Where to check
How to check
- GTMAdminContainer Settings
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.
