Undo a bad change in a few clicks.
Found a bad publish? Pick an older version that worked. You see what will change, then you confirm.
Fixing a bad publish is slow
You dig through old versions. You try to remember which one worked.
Every hour you wait, you lose data you can't get back.
How rollback works
Step 1: Pick a version that worked
Open the container's version list. Pick the one you want, then click Roll back to this version.
Step 2: Give one more permission
The first time, Google asks you to let us publish. We use it only when you confirm.
Step 3: See what will change
A page shows you what will change on the live site. Nothing happens yet.
Step 4: Click to confirm
That version goes live again. It reaches your site within a few minutes.
Step 5: It is logged
We log who rolled back and when. Your Slack alert names you, too.
Questions you may have
Whose account does the publish use?
Yours. Google Tag Manager checks that you are allowed to publish that container.
Can I roll back to any version?
You can pick any version we saved. We save each version from the day you connect a container.
Can two people roll back at once?
No. One rollback runs at a time on a container. That keeps a second click from undoing the first.
Have a way back ready
Connect your containers now. When something breaks, the version that worked is one click away.
See what else it does
Change alerts in Slack
Know when someone publishes. Get a short note that says what changed, in plain words.
Learn more10 safety checks
Each new version gets 10 checks. They flag risky changes, like a lead tag that was removed.
Learn moreBrowser checks
A real web browser opens your pages, like a visitor would. It makes sure your tags still fire.
Learn moreDrop alerts
Hear when your sales or leads fall. The alert points to the publish that came just before.
Learn moreBring your own AI
Plug in the AI helper you already use. It can find the cause and draft a fix. A person says yes first.
Learn more