With server-side tagging, your tracking data goes to a server on your own domain first, and that server forwards it to Google, Meta and the other platforms. 14 articles
Server-side tagging means the browser sends one stream of events to a tagging server on a subdomain of your site. That server runs a Google Tag Manager server container, often called sGTM, which forwards each event to the platforms. Requests become first-party, cookies can be set by a server, and you decide what each platform receives. The plain-language explanation starts from zero.
A server container is configuration; it still needs a machine to run on. You can host it on your own cloud account or use managed sGTM hosting, and where it runs decides where your visitors' raw data is processed. Why host server-side GTM in the EU covers that choice, and the benefits and the costs help you decide whether it pays off.
Ready to build? The server container guide creates the container and its two clients. Below it are guides for GA4, Google Ads, consent, moving an existing container and debugging.
Start here: What is server-side tagging?
Since 17 November every G- and AW- tag opens in Tag Manager. What changes for gtag.js sites, access and your server container URL, and what to check.
From 11 January 2027, Google Ads and Floodlight tags in server-side GTM receive the full visitor IP. What it means for privacy and how to keep it shortened.
What a tagging server does, how it differs from browser tags, what it changes for cookies, ad blockers and consent, and what sGTM hosting means.
What you gain in data, cookies, control and EU hosting, what it costs to run and maintain, and how to work out whether it pays off for your site.
Create the container, choose manual provisioning, then connect Google Tag Manager or paste its config into Measurebase, plus the two clients every setup needs.
Host the same container, keep or change the hostname, switch DNS without a gap, keep cookies and click IDs, verify, retire the old host.
From the data layer to your reports: send, register and check the details of each event.
How events flow from your site through a server container to Google Analytics · and what to watch in debug mode.
Reprocessing delays, split tracking paths, server-to-server events without session data, missing referrers and consent: how to tell them apart and fix each one.
Schrems II, data residency and what it means for your analytics stack when tags leave the browser · and the continent.
Set it up in your web container and your server container: the four signals, default and update, basic or advanced mode, and Conversions API tags.
Plain definitions of the terms you meet when you set up server-side tracking, with a link to the article that goes deeper.
Self-hosted, Google's own guide for Cloud Run estimates about $45 per server per month and recommends at least two servers in production. Then come updates, the certificate, DNS and monitoring. Managed hosting takes the server side off your hands: Measurebase starts free for one domain and 15,000 requests a month.
Partly. A tagging server on your own subdomain gets past the blockers' domain lists, but its requests still end in fixed paths such as /g/collect, which pattern rules match. Measurebase's Enhanced script and Enhanced Ad Blocker Protection mask those paths. A visitor who refused consent must still not be tracked.
No. The web container keeps running on your pages and sends its events to your server container instead of to each platform. Only its loader changes, and the Google tag gets server_container_url set to your tagging subdomain. Setting up a server container shows how the two connect.