Google Tag Manager: containers, previews and versions for safe tracking changes

The parts that make changes safe

Tag Manager gives you three safeguards, and most tracking accidents come from skipping them. A workspace holds edits that do not affect the site until published. Preview shows, for your own browser, which tags fire and what triggers them. And every publish saves a version, which Google documents you can republish directly, or set as the latest to continue from.

The data layer is the other half. Google's documentation says it should be declared above the container snippet, only ever pushed to, and use consistent names; tags that read it break when those rules are broken.

• Edit only in a workspace.
• Preview before publishing, and keep before and after screenshots.
• Name versions so a stranger can follow them.

Where the common faults sit

An unexplained container is a documentation fault, fixed by an inventory and a clean-up. A form that counts failures is a trigger-choice fault. Stale items on an ecommerce event are a data layer clearing fault. Consent that arrives late is an ordering fault covered by the Consent Initialization trigger and consent checks. A server container is an optional route to forward events, not a repair.

Each has a guide on this site, and a bounded outcome where one fits.

• Read the guide for the symptom before changing anything.
• Do not publish a change you have not previewed.

Priced routes and boundaries

Bounded routes: Clean up one GTM container, £395; Banner choices reach Google tags, £395; Track one form's submissions, £245; Set up server-side tagging from £995; and a standing change-testing service at £145 a month with up to four changes. A full rebuild of a site's measurement starts from £4,500. All are untested proposals with payment after sign-off. We prepare changes in a workspace and you publish. Send the tag count and the events you must keep; no logins, exports or account IDs.