What Is Server-Side Tagging in Google Tag Manager?

Server-side tagging in Google Tag Manager uses a server container, hosted in a cloud environment you control, to receive and process tag data instead of firing every tag directly from the visitor's browser. The website only runs a lightweight web container that captures user interactions and sends them as HTTP requests to your server container, which then forwards the data on to Google products or third-party endpoints.

Two Containers, Not One

A standard (client-side) Google Tag Manager setup runs entirely in the browser: every tag, trigger, and variable executes on the visitor's device. Server-side tagging splits that work across two containers — a web container on the site that dispatches events, and a server container you own that receives those events and decides what to do with them before passing data along.

Why It Exists

Google introduced server-side tagging in 2021 specifically to address signal loss from iOS App Tracking Transparency, Intelligent Tracking Prevention, and browser ad blockers, all of which interfere with tags running client-side in the browser.

What the Server Container Adds

• An owned intermediary endpoint between the browser and any third-party destination, rather than the browser talking to those destinations directly
• Processing rules you control, applied to data before it leaves your server container
• The same tag, trigger, and variable model as standard GTM, so existing configuration knowledge carries over

The Tradeoff

Server-side tagging requires standing up and paying for cloud infrastructure to host the server container — it's a meaningfully bigger technical lift than a browser-only setup, and it's typically adopted by sites already hitting real tracking-accuracy problems rather than as a default starting point.

Bottom Line

If ad blockers or browser privacy restrictions are visibly cutting into your conversion tracking, evaluate server-side tagging as the fix — but budget for the cloud hosting and setup work before committing to the migration.

Source: Google for Developers, "Server-side tagging" and Tag Manager Help, "Client-side tagging vs. server-side tagging" (developers.google.com/tag-platform/tag-manager/server-side; support.google.com/tagmanager/answer/13387731).