Container Versioning
Data & TrackingAlso: Tag Manager Versioning · GTM Version History
Quick definition
Container versioning is the practice of saving a snapshot of a tag management system's configuration each time it's published. Each version records exactly which tags, triggers and variables were live at that point, so a team can compare, audit or roll back to an earlier setup if something breaks.
How it varies across Australia
Data and tracking maturity varies widely across Australian businesses. Teams with disciplined container versioning tend to score well on Data & Tracking generally, while teams that publish tags directly with no version notes tend to also be missing basics like consent mode or a clean data layer.
See data and tracking maturity across Australian industries →The moving parts
A locked snapshot of the container at the moment it was published.
The draft area where changes are made before publishing creates a version.
The action that turns a workspace into a live, numbered version.
Republishing an older version to undo a broken change.
What it actually means
Every time you publish a change in a tag management system like Google Tag Manager (GTM), the platform saves a numbered version. Think of it as a save point in a video game. If the next change breaks conversion tracking, you don't have to rebuild the working setup from memory. You republish the last good version and the site is back to normal in minutes.
The problem is that most teams treat this as an automatic safety net rather than a discipline. Versions get created with no name, no notes, and no record of why the change happened. Six months later nobody knows which version added the new pixel, which one broke attribution, or which one is safe to roll back to.
Done properly, container versioning works like commit messages in software development. Each version gets a short note describing what changed and why. That habit turns your tag manager's history into a debugging tool instead of a black box. It also protects the data layer, your consent mode setup, and every conversion event downstream of the container, because you can always prove what was live on any given date.
A tag manager without version discipline is a live production system with no undo button.
How it shows up
Container versioning shows up as the version history tab inside Google Tag Manager, listing every publish with a version number and timestamp. It also shows up indirectly whenever conversion data breaks after a site change and someone asks 'what did we publish last', or when an agency handover includes no context on why certain tags exist. Good versioning shows up as a container where every published change has a name and a one-line reason attached.
The Australian context
Australian businesses juggling the Privacy Act amendments and ACMA's spam rules increasingly need to prove what consent settings and tracking scripts were live on a given date, particularly around consent mode changes. A clean version history with dated notes is the easiest way to answer a compliance question without guessing.
Where people get this wrong
Related terms
Common questions
How many container versions should I keep?
Google Tag Manager keeps every version by default, so there's no need to delete old ones. What matters is naming them clearly so the history stays useful rather than becoming a long list of unlabelled numbers.
Can I roll back a container version myself?
Yes. In Google Tag Manager, open the version history, select an earlier version and republish it. This immediately replaces the live container with that earlier setup, which is why clear version notes matter before you roll back.
Does container versioning affect my data layer?
The version records which tags, triggers and variables were live, including anything reading from the data layer. It doesn't change the data layer code on your site itself, only which tracking configuration is listening to it.
Is container versioning the same as a website backup?
No. It only covers what's published inside the tag management system, like tags, triggers and variables. It has no record of your site's code, design or content, so it can't replace a proper website backup.
Debrief
Get the next one
No spam. No fluff. Just the next article, straight to your inbox.
Keep exploring
About New Rebellion
New Rebellion is a marketing intelligence consultancy. We build tools, score Australian businesses on how their marketing actually performs, and publish Debrief every day. This dictionary is part of how we work in the open.
How we think →