How-to · Updated October 11, 2026
Roll back a Tag Manager container to an earlier version
Updated October 11, 2026
15 minutes
In Tag Manager, open Versions, find the last version that worked by its Published date, preview it, and publish it from its Actions menu. That changes what visitors run, and Google lists resetting the draft as a separate step, so also choose Set as Latest Version, or the next publish can put the broken change back.
Before you start
- Publish permission on the container. Google's Edit role cannot create versions or publish, and the Approve role can create versions but cannot publish.
- Roughly when the problem started, such as the day the site or the tracking broke, to match against the publish dates.
Find the last version that worked
Every publish records a version, so the version that was live before the break is your rollback point, and its Published date is how you find it.
- Open the container at tagmanager.google.com and click Versions.
- Read the Published column. Entries with a date there are the publish history: when each version went live and who published it. If environments are set up, an Environments column shows where each one went; only Live matters to visitors.
- Pick the newest version published before the problem started. Click it to see what it contains, then open the version after it to confirm that one holds the change you suspect.
- Test it before it goes live: open the Actions menu on that version (Google's preview help calls it More Actions) and select Preview, then do on the site whatever broke. Preview shows the version only in your browser, so visitors are not affected.
If the earlier version fails in Preview too, the fault is probably outside Tag Manager, such as a site update, and rolling back the container will not fix it.
Publish the earlier version
Publishing the earlier version from the Versions list replaces the version your visitors run, and Google lists changing the draft as a separate step.
- In Versions, open the Actions menu next to the version you tested and select Publish To....
- If an environment menu shows, choose Live. Publishing to any other environment does not reach visitors.
- Confirm the publish.
- Write down every change published after this version. They leave the site too, including any that worked, and you will add the good ones back.
Reset the draft so the fault does not come back
Your workspace is still built on the newest version, the one with the broken change, so the next publish from it can ship that change again unless you reset it.
- In Versions, open the Actions menu next to the good version and select Set as Latest Version. Google says this replaces the current container draft with the content of that version.
- If other workspaces exist, each may say it is out of date. Either way, open each one before anyone publishes from it, and abandon anything that repeats the broken change.
- Re-add the good changes you wrote down, preview them, and fix the broken one before it goes back.
- When you publish next, click Submit, choose Publish and Create Version, and give it a Version Name and Version Description that say what changed. A named version is the rollback point the next person can find.
Check it worked
In Versions, the publish history should show the version you restored as published today.
Leave Preview first: click the X in the upper left corner of the Tag Assistant debug interface, then Stop debugging on the Tag Assistant activation page, so the browser no longer shows the previewed version.
Then open the live site and repeat what broke: load the page, submit the form, click the button. The site should behave as it did before the problem started.
If reports were affected, judge the fix on the site first, since reports usually fill in later than the site changes.
Undo the rollback
Rolling back is itself a publish, so it can be reversed the same way: open Versions, choose Publish To... from the Actions menu of the newer version, and publish it to Live again.
Why the Published column matters more than the version number
A version can be created without ever being published, so the newest version in the list is not always what visitors ran. The Published column is the record of what was actually live and when.