- Our Blog
What do you do when you’re stuck with Legacy GA tracking on a third-party platform? When a website is running an old version of Google Analytics (GA) code, our first step is to upgrade them to the current code set, Universal. But, on occasion, part of the user journey may happen on another domain on some third-party platform where updating code is not feasible.
This is an exhaustive overview of every change, big and small, introduced in the new version of Google Tag Manager (GTM v2). You won’t find any change discussed in detail; there are already great articles that walk through the major changes. This post simply aims to make you aware of every nuance and new concept and feature that is different from v1 (and hopefully inspire you ...
Using the auto-migration tool to migrate to Google Tag Manager v2 (GTM v2) is fine, and perfectly safe. It’s the best method for migrating, and if you haven’t already, I highly recommend you become acquainted with your options as soon as possible (before June 1st, 2015). Although GTM v2 is fully compatible with Accounts/Containers created in GTM v1, automatically migrated Co ...
If you’ve logged into Google Tag Manager (GTM) recently, you already know that a new version (GTM v2) is now available. Here’s the skinny: GTM v2 includes a revamped interface and a few functional enhancements. Even though GTM v2 is fully backwards-compatible with old Accounts and Containers, GTM v1 Accounts need to be migrated to GTM v2.