By Jeff Lukey

On Monday 1st June Google automatically started to migrate users from GTM interface v1 to v2. Here's a very quick summary of what you need to know.

Back to blog home

Google Tag Manager Logo

For some time now, Google have been displaying the following notification within the GTM v1 interface to all users:

Consequently this news shouldn't come as a great surprise to any user who regularly logs into their GTM account. For those that haven't seen this notice, Google have provided more information on the migration here.

But What Does This Mean?

Basically, GTM is getting a huge face lift with a significant overhaul of the user interface (UI). See below for before and after shots:

Before

GTM v1 Interface

After

GTM v2 Interface

Besides the change in appearance, the other key point to know is that Macros are being renamed 'Variables' (hurrah!), Rules are being renamed 'Triggers' and Tags are, well, still called Tags.

Whilst the core concepts are still very much in play, Google have also tweaked the workflow to make it more intuitive and encourage a choose tag > configure tag > choose when tag fires approach. This flow has essentially now been integrated within the 'Add a new tag' wizard rather than having the Tag, Rules/Triggers and Variables/Macros as more detached entities as they were in GTM v1.

GTM v2 also surfaces some new features that were not available in v1 so look out for future blogs on these.

Will This Impact My Published Container?

Google have confirmed to us that the migration process won't have any impact on a published container.

So Do I Need To Do Anything?

The key takeaway from Google's help page is that:

“You do not need to retag your site or otherwise make any code or configuration changes when you migrate”.

Having said this, the interface is quite different and containers that are migrated from v1 to v2 won’t necessarily make the slickest use of the new tools/ways of working. We therefore recommend completing an update/cleansing exercise when creating your first new container version post-migration (it's a great opportunity to get rid of those unused assets!) and that you implement an even more rigorous testing regime than normal before publishing this.

Need Some Help With This?

If you are interested in bespoke training which covers the new v2 interface or if you would like assistance in converting containers to make best use of the latest features, please get in touch.

Share this article