Web and server containers: setting them up, debugging them and keeping them clean. 14 articles
From empty container to published: the Google Analytics tag, a first-party loader and the switch that routes events to your server container.
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.
The Google tag, the Initialization trigger, the Tag Assistant check and the double-install test.
The data layer, the purchase event and its items, the test order and the five mistakes that break revenue.
How the linker works, what to configure in the Google tag and the Conversion Linker, how Measurebase domains fit, and what the audit checks.
The four signals, basic versus advanced mode, and what your server container has to do with the consent state.
Tracking before the banner is answered, or after a refusal: the usual causes and how to fix them in Google Tag Manager.
The five causes of page views and conversions counted twice, and how to remove each.
GA4 and Google Ads hits that go straight to Google instead of your tagging server, and how to set the server container URL right.
Where the debug session attaches, why the first server container URL matters, test hits from your site and from Shopify checkout, and what to check when the preview stays empty.
40+ checks across your web and server container, your site, your DNS and certificate · a site crawl for every script and pixel outside GTM · errors, warnings and info · proposed fixes that land in a workspace you publish yourself.
How the masked Enhanced loader works, how it carries ad blocker protection, and when the standard gtm.js pattern is used instead.
How the Client Event Signal and Server Event Signal GTM tag templates measure server-vs-client uplift and Consent Mode v2 state, per event.