Previously, we mentioned how Google has added Workspaces to their Tag Manager – which allows users to create their own versions of the container to update specific elements. This enables multiple changes to be worked on but not impact each other. If you have leveraged them at all you have seen their value to your organization.
The Workspaces, however, are not without their own potential pitfalls if you aren’t fully aware of how they function.
Here are three best practices that you should incorporate into your tag management governance process to minimize problems:
In the free version of Google Tag Manager, you are provided with a maximum of three workspaces inside your container. One of the biggest advantages of workspaces is that they allow you to create your own copy of the container and then work on a tag deployment that may be rather complex.
While doing this, you will inevitably run into requests to publish a marketing pixel or to make some small change to an existing setup. As a result, we recommend you always keep one workstation available to make these incremental updates without accidentally publishing everything from your incomplete and larger tagging effort.
Concurrent changes on the same tag, trigger or variable and publishing them will result in a conflict error. Once you publish, be aware of whether the action completed successfully without any conflict notifications. If you do not address those conflicts, your workspace does not get published to production, and your site will not reflect the changes you made to the container.
Since your organization may have more than one person working with the Tag Manager, you always want to make sure you’ve provided as much detail as possible for a workspace you set up. Typically, I will include:
By incorporating these three steps into your Tag Management Workspaces workflow, you’ll ensure that your tag management process is well managed, conflict free and well documented.