01 — Approach
Order is not a matter of taste
We have built tracking setups since Google Analytics existed, and GTM containers since their earliest days. If that time taught us one thing, it's this: a container doesn't rot out of malice, it rots through a hundred small quick fixes. A tag for that one campaign, a trigger created as a copy, a test that never got removed.
That's why we treat GTM like code. Naming conventions, one purpose per tag, no duplicates, every version with a meaningful description. That's not pedantry, it's the difference between a ten-minute change and an afternoon of archaeology.
02 — Current
What's changing in GTM right now
In 2026 Google is rebuilding Tag Manager more deeply than it has in years: GTM containers are merging with the Google tag. Announced at Google Marketing Live in May, the new structure has been rolling out gradually since late June. Instead of separate tags for GA4, Google Ads and Floodlight, there will be destinations in one shared model, plus central settings for things like cross-domain tracking and user-provided data in a single place. A visual event builder is in beta for Google Ads, and server-side tagging is increasingly becoming the default case.
That's convenient, but it also shifts responsibility: central settings affect several products at once, and anyone who clicks through them without understanding them changes their tracking in three places at the same time. The details and our assessment are in our blog post on the GTM update 2026.
Our recommendation: don't just wave the migration through, use it as the occasion for a container spring cleaning. Clean up now and you migrate a tidy container instead of a museum.
03 — Foundation
Data layer architecture
The data layer is the foundation every tag stands on. We define a schema before the first line gets implemented: which events, which parameters, which data types, who pushes them and when. Your development team receives the schema as a specification; we support the implementation or take it over entirely, together with our web tech team. That way the container measures data from one reliable source instead of hand-clicked DOM selectors that break with the next redesign.
04 — Practice
Container audit and cleanup on takeover
Most containers we take over are museums: orphaned tags, triggers in triplicate, and nobody remembers what tag 47 actually does or why it only fires on Tuesdays. Our audit inventories every tag, trigger and variable, checks what still fires and what is just ballast, and documents the result. Then we clean up in stages, each change as its own version, so a rollback is possible at any time.
A tag nobody understands anymore is not tracking. It's a risk with a version number.
If you want to know where your container stands: we run the audit pass as a free first check and tell you honestly whether it needs a cleanup or just a few adjustments. Get in touch briefly.
05 — Discipline
Web containers and server containers
Web and server containers have different jobs: the web container collects events in the browser, the server container processes them first-party, enriches them and distributes them in a controlled way to GA4, Meta and the rest. We build both so they share the work sensibly, with one common event schema instead of duplicated logic. The fundamental questions, hosting, cost and when the step is worth it, are covered on our server-side tracking page.
06 — Discipline
Trigger logic without surprises
Triggers are where containers most like to break: click triggers so broad they fire on every button, regex constructs nobody can decipher anymore, exceptions to exceptions. We keep trigger logic flat and predictable. A trigger reacts to a data layer event, not to CSS classes, and consent conditions are built in rather than patched on. How the consent signals arrive cleanly before the tags fire is covered on our Consent Mode v2 page.
07 — Process
Versioning, releases and documentation
Every change follows the same path with us: create a workspace, test in preview mode, publish a version with a description. On larger setups we separate roles so editing and publishing don't have to sit in the same hands. And we document the container so your team understands it: what each event measures, where it comes from, who may change what. What all of this ultimately pays into is on our overview of Tracking & Analytics. The event definitions themselves are born in the measurement plan together with GA4.
How many tags in your container do you still recognize?
Tell us briefly how old your container is and who last maintained it. We'll take a look and tell you honestly whether it needs a cleanup. First call free, 30 minutes.