Search
Clear search
Close search
Google apps
Main menu
true

Publishing, versions, and approvals

In this article:

Publishing

When you publish a container, Tag Manager will make your changes active for the environment specified. Users with Publish permissions can publish a container. 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 Submit button at the top right hand side of the screen. The Submit Changes screen will appear, with options to publish the container and save a version of your container. Tag Manager 360 customers will see an additional option to Request Approval. Select Publish and Create Version if it is not already selected.
  2. Review the Workspace Changes section to see if everything looks as expected.
  3. Enter a Version Name and Version Description.
  4. If you have Tag Manager configured to use multiple environments, select which environment you'd like to publish to in the Publish to Environment section.
  5. Click Publish.
Note that you can review changes before you publish in the Workspace Changes section. You can use the More Actions () menu in the Workspace Changes section to view differences between versions for the element in question, or abandon the change. Click on the name of the element in the list to view an expanded detail screen, where you can review what has changed with each element, make last minute changes, or abandon the change.

Versions

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. Users with Approve access or higher can create versions.

Every time a container is published, a version of that container is recorded. As a result, you'll have a saved version of anything that has been previously published.

Versioning 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 (without publishing):

  1. Click on the Submit button at the top right hand side of the screen. The Submit Changes screen will appear, with options to publish the container and save a version of your container. 360 customers will see an additional option to Request Approval.
  2. Select Create Version.
  3. Enter a Version Name and Version Description.
  4. Click Create.

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. 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 example.com. 

Approvals (Tag Manager 360)

Containers owned by Tag Manager 360 accounts have "Approvals" functionality. Users with Edit access or higher will see an additional option to request approval for changes.

The user requesting approval can optionally assign a user to review the request, and leave a comment with instructions or context. Any user with Approve or Publish access can take action on the request, but assigning it to a specific user is a good way to earmark or flag the approval for a specific person.

Request approval

To request approval for a workspace:

  1. Click on the Submit button at the top right hand side of the screen. The Submit Changes screen will appear, with options to publish the container and save a version of your container. 360 customers will see an additional option to Request Approval.
  2. Select Request Approval.
  3. Optional: Click Choose Approver to identify someone to review and approve your approval request.
  4. Optional: Enter a comment in the Comment section.
  5. Click Request.

If you are working in a workspace that has a pending approval, you will see a banner indicating pending approval status. Click View Request to see the changes as they were requested.

Approve requests

The Approvals tab will list all approval requests that have been submitted for a given container. These items will include requests to publish workspaces, approve External Account Links, and add tags from DoubleClick Campaign Manager. When there are requests pending approval, the Approvals tab will have an indicator next to it:

  • A blue circle means there are requests pending approval that are either assigned to another user, or are available for anyone to review and approve.
  • A red circle means there are requests assigned specifically to you that are pending approval.

To review pending approval requests, click on the Approvals tab. A list of approval requests will appear.

To review and approve or reject an approval request:

  1. Click the Approvals tab
  2. Click the name of the entry to be approved. The Approval Request window will appear.
  3. Review the details of the request.
  4. Optional: If there is no assigned approver, you may select one by clicking Choose Approver.
  5. Optional: You may add a comment to the request details by clicking Add Comment.
  6. Click Approve to approve the request, Send Back to deny the request and have the original submitter make further edits, or Withdraw to cancel a request that you submitted.
The Approvals functionality gives Tag Manager 360 customers additional flexibility to help establish the right workflows for their organizations. Container owners may choose to grant Publish access to a smaller set of users that review and approve publish requests, to ensure they meet your organization's standards and free of errors. Approvals could be used to establish collaborative workflows and to allow 3rd party agencies or less technical users to be brought in to the tagging process in a way that keeps centralized control in the hands of key stakeholders.

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?