Analytics and Tracking

Version

Also called Container version, snapshot

A dated snapshot of every tag, trigger and variable in a container, kept so you can republish or roll back.

Quick facts: Version

Category
Analytics and Tracking
Also called
Container version, snapshot
Level
Beginner
Affects
Rollback speed, tracking reliability, team accountability
Where to see it
Google Tag Manager (Versions tab, version comparison view)
In this article4
  1. How a version works
  2. Why versions matter
  3. Common mistakes with versions
  4. How to act on it

How a version works

Inside Google Tag Manager, the container you edit is a live working copy. Nothing you change there reaches the website until you save that work as a version. A version freezes every tag, trigger, variable, folder and setting exactly as they stood at that moment, gives them a number, and stores them permanently alongside the name and notes you typed.

Versions are cumulative snapshots, not a list of edits. Each one holds the whole container, which is why you can open one from months ago and see the full picture rather than a fragment. Tag Manager also shows a comparison between any version and the one before it, so you can read what actually changed without relying on anyone’s memory.

Creating a version does not affect the website on its own. Saving and going live are separate steps: a saved version sits in the list until someone chooses to publish it to the live site.

Why versions matter

They are the only reliable way back. Tracking breaks quietly — a conversion tag stops firing, a trigger starts matching the wrong page — and the damage usually surfaces days later in a report rather than on screen. With versions, recovery means choosing an older snapshot and publishing it, which takes minutes. Without them, you are rebuilding from guesswork.

They also create a record. When an agency, a developer and an in-house marketer all hold access to the same container, which is common on small business projects, the version list is the only honest account of who changed what and when. That matters most in the argument that follows an unexplained drop in reported conversions.

Common mistakes with versions

The most common is leaving the name and notes blank. A column of unnamed versions is close to useless in an emergency, because nothing tells you which snapshot was the last good one. A short name and one sentence describing the change cost seconds and save an afternoon.

The second is saving a version that bundles unrelated work — a new remarketing tag, a scroll trigger and a fix to a form event, all in one. If anything breaks, rolling back strips out the good changes with the bad. Keep a version to a single piece of work wherever the schedule allows.

How to act on it

Save a version before you begin a risky change as well as after you finish it, so there is a known-good point on both sides of the work. Name it in plain language: what changed, and for which campaign or page. Then test in preview before publishing, because a version records your intention, not proof that the intention was correct.

If you inherit a container from a previous supplier, read the version history before you touch anything. It usually explains more about the state of the tag management setup than any handover document, and it tells you which snapshot to return to when the current one misbehaves.

Do and do not

Do

  • Name every version and say what changed
  • Save a version before starting risky tracking edits
  • Read the version comparison before you publish

Do not

  • Bundle unrelated changes into a single version
  • Assume a saved version is already live
  • Restore an old version without checking the site first

Questions people ask about this

Does saving a version change my website?

No. Saving a version stores a snapshot of the container inside Tag Manager and does nothing else. The code running on your site keeps serving whichever version was published last. That separation is deliberate: it lets you save work in progress, hand it to a colleague for review, and make it live only once you are satisfied it behaves correctly.

How far back can I roll a container?

Tag Manager keeps every version you have saved, so you can open any of them and republish it. The practical limit is relevance rather than storage. A very old snapshot may point at tracking IDs, page paths or form fields that no longer exist, so check what has changed on the site before restoring anything from a long way back.

Should every small edit be its own version?

Group edits that belong to the same piece of work and separate ones that do not. A version covering a single campaign's tracking is easy to reverse cleanly. A version mixing three unrelated fixes forces you to lose good work in order to undo bad. Naming matters more than frequency, because an unnamed version is hard to trust in a hurry.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.