How-to · Updated October 11, 2026
Fix Tag Manager changes that aren't showing on your website
Updated October 11, 2026
10 minutes
Click Submit in Tag Manager and publish. A change saved in a workspace is not on your website: visitors keep running the last published version until a new one is created and published to the Live environment. If it was published, check that the site loads the same GTM- container ID you edited.
Before you start
- Publish permission on the container. Google's container roles are Read, Edit, Approve and Publish. Edit can change tags but cannot create a version or publish; Approve can create a version but cannot publish.
- Your website address, to test the live site with Tag Assistant.
See whether the change was ever published
Every change in Tag Manager is made in a workspace. Google is explicit that workspace changes must be published to become operational on the site, and Preview mode shows them only in your own browser or to people you share a preview link with.
- Open the container at tagmanager.google.com and click Versions.
- Find the version with the most recent date in the Published column. That is the version published last, and the one your visitors run. If environments are set up, the list adds an Environments column: the date must be for Live.
- Open it and look for your new or changed tag. If it is not there, the change is still sitting in a workspace or in a version nobody published.
Publish it
Publishing turns the workspace into a new version and sends that version to the Live environment your visitors load.
- Go back to the workspace that holds the change and click Submit at the top right.
- Choose Publish and Create Version if it is not already selected.
- Read the Workspace Changes list. It shows every change in this workspace, including ones other people made in it; abandon anything that is not ready. Changes in newer versions created elsewhere go live too (see below).
- Enter a Version Name and Version Description that say what changed. The version is your rollback point.
- If a Publish to Environment menu shows, choose Live. Publishing to any other environment does not change the version your visitors see.
- Click Publish.
If Tag Manager says the workspace is out of date, a version was created since this workspace was last updated. Proceeding merges its changes into yours (you are asked to resolve any conflicts), and they go live with your publish, finished or not.
Check the site loads the container you edited
If the change is in the published version and still does nothing, the site may be loading a different container.
- In Tag Manager, on the Workspace tab, find the container ID. It starts with GTM-.
- Go to tagassistant.google.com, click Add domain, enter your website address and click Connect. Check the Google tags found list for the containers and tags on the page.
- If the GTM- ID listed is not the one you edited, make the change in that container instead, or ask whoever manages the site to replace the snippet. If no container is listed at all, the snippet is probably missing from that page; Google says it belongs as high in the head of every page as possible.
Check it worked
In Versions, your new version should now show today's date in the Published column.
Then connect Tag Assistant to the live site, outside Preview, and do what should fire the tag: load the page, submit the form, click the button. The container listed should be the one you edited, and your tag should usually appear among the tags that fired. The Published date in Versions remains the firmer proof.
If the tag sends data to Google Analytics or Google Ads, give it time before judging the reports: Google says data collection may take up to 30 minutes to start after a Google tag goes live, and a first Analytics install can take up to 24 hours to show in the Realtime report. Use Tag Assistant, not the reports, to judge whether the tag fires.
Why Preview showed it working
Preview mode runs the current workspace as if it were deployed, but only in the browser that started it or in a shared preview link. Regular visitors never see it. A tag that fires in Preview proves the setup works, not that it is live.
Publishing your version can ship someone else's work
A container has one line of versions. When you publish, your workspace is updated with every version created since the workspace was last updated, including versions someone saved and never published. Check Versions before you publish: if the newest version has no date in Published, find out whether it is ready, because publishing yours will put its changes live too.
Undo a publish that broke something
Open Versions, find the last version that worked, and choose Publish To... from its Actions menu. Google keeps a publish history, so you can see when each version was live and who published it.