How a server container works and what it changes for your data. 10 articles
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.
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.
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.
Conversion Linker, server-side conversion tags, enhanced conversions, click IDs and what the Google Ads connection audits.
Schrems II, data residency and what it means for your analytics stack when tags leave the browser — and the continent.
The four signals, basic versus advanced mode, and what your server container has to do with the consent state.
Plain definitions of the terms you meet when you set up server-side tracking, with a link to the article that goes deeper.
How the Client Event Signal and Server Event Signal GTM tag templates measure server-vs-client uplift and Consent Mode v2 state, per event.