Clear search
Close search
Google apps
Main menu

Publishing and versions


Changes made to a container's workspace do not take effect on a site or mobile app until you publish. Once you've added or edited tags, triggers, and variables in a workspace, you'll need to publish in order to make your additions and changes live on the site/app.

To publish your current workspace:

  1. Click on the publish button at the top right hand side of the screen.
  2. If you have Tag Manager configured to use multiple environments, select which environment you'd like to publish to.
  3. Click Publish Now.


A version is essentially a snapshot of a container. You can save the current state of a workspace as a version at any time. This allows you to save and preserve your work and go back to a previous version if you need to.

Saving a version is independent of publishing. You can save versions at any time and you never need to publish a version unless you want to. However, you cannot publish a container without first saving it as a version. As a result, you'll have a saved version of anything that has been previously published. This can make it easier to recover from mistakes. For example, if someone accidentally publishes a container version before it's ready for production, you can simply publish another version that has been debugged and is known to work.

To save the current state of the current workspace as a version, click the publish menu (next to the Publish button) and then choose Create Version.

To publish a previously saved version of a container to the site, click on Versions in the top navigation. Click the desired version in the table, then click Action → Publish. Google Tag Manager maintains a publish history, so you can see when versions were live and who published them.

To see the publish history, go to Versions and look for entries with a date in the Published column.

To replace the current container version with a previously saved version, go to Versions. Click on the Action link next to the desired container version and click the "Edit as new version" link in the Action drop-down list. This replaces the current container draft with the content of the container version you've selected. This action does not change the published container version.

To publish a specific version, go to Versions, identify the version you'd like to publish, and then select Publish To... from the Actions menu.

When publishing and/or creating a version, enter a Version Name and Description that will make it easy to know what changes are being made. For example:

  •      Version name: "GA page view tag initial launch"
  •      Description: "Launch the Google Analytics page view tag on 

Next steps

  • Learn about using workspaces to manage multiple sets of tag changes.
  • Learn about using folders to keep your work organized.
  • Learn how to best organize your containers.
  • Learn about using environments to control how tag manager publishes between testing and production servers.
Was this article helpful?
How can we improve it?