Create the account in the business's name and a web container, install the snippet on every page, add the Google tag and your key event tags with triggers that fire on real success, name everything to one pattern, connect consent mode, test in preview with Tag Assistant, and publish named versions with notes.
How Tag Manager works
Google's introduction to Tag Manager describes a container as a collection of tags, triggers, variables and related settings. Tags are snippets of code that send data, such as the Google tag for GA4 or an ad platform's tag. Triggers cause a tag to fire when certain events occur, such as a page view or a form success. Variables supply the values tags and triggers use, such as a page path or a form name.
Step 1: Account, container and access
Ownership problems are the hardest to fix later:
- Create the account in the business's name, with at least two internal administrators.
- Create one web container per site (and separate containers for apps).
- Give agencies and suppliers user access with the least permission they need.
- Add the container snippet to every page, as high in the page as the instructions say.
Step 2: The first tags
Start small:
- The Google tag for GA4, firing on all pages; Google's GA4 setup guide lists Tag Manager as one way to add it.
- Key event tags for your real outcomes, with triggers on confirmed success.
- Ad platform tags only where you advertise, with their conversion events.
Step 3: Triggers that fire on success
Most bad tracking comes from triggers. Fire key event tags on the thank-you page or the success message, not on a button click that also fires when validation fails. Use a data layer event pushed by the site on success where you can; it is more reliable than watching clicks.
Step 4: Naming and housekeeping
Name everything to one pattern, so anyone can read the container:
- Tags: platform, type and what they measure, such as "GA4 - Event - Quote form success".
- Triggers: type and condition, such as "Custom event - quote_form_success".
- Variables: what they hold, such as "DLV - form_name".
- Folders by platform, and a note on each item saying why it exists.
Step 5: Consent
Connect the container to your consent banner so tags respect each visitor's choice. Google's consent mode passes consent states to Google tags and was updated in November 2023 with the ad_user_data and ad_personalization signals. Set default states by region, and check that non-Google tags also wait for consent where the law requires it. This is general information, not legal advice.
Step 6: Preview, then publish
Google's preview and debug guide lets you browse the site as if the current draft were live, while Tag Assistant shows which tags fired and in what order. Test every change this way, on a phone as well as a desktop, and with each consent choice.
When it works, publish a version with a name and a note. Google's versions guide describes a version as a snapshot of the container at a point in time, so a bad change can be rolled back by republishing the previous one. Approval workflows need Tag Manager 360.
Server-side tagging
Google also offers server-side tagging, where a server container receives data and forwards it to platforms, using the same tags, triggers and variables. It can improve control over what data leaves your site, but it adds hosting and setup work; most sites start with a clean web container and consider server-side later.
Conclusion
A clean Google Tag Manager setup starts with the business owning the account, one container per site, a few well-named tags for GA4, key events and active ad platforms, triggers that fire on confirmed success, consent mode tied to your banner, every change tested in preview with Tag Assistant, and named versions so you can roll back.
PromotEdge International is an international strategy, technology, marketing and design company, and our delivery team is in India. Our analytics team builds and documents Tag Manager containers and cleans up inherited ones, testing in preview before anything is published.
Facts we rely on: see our company facts for what we state about ourselves and where each fact comes from.