TagCommander, from European company Commanders Act, is a tag management product designed to handle website tags - and also SDKs in a single SDK container - through a management interface without the need for technical expertise.
The company has partnerships with WebTrends, Criteo, and over 200 tag solutions worldwide.
N/A
Google Tag Manager
Score 8.8 out of 10
N/A
From Google, the Google Tag Manager is a tag management application that facilitates creating, embedding, and updating tags across websites and mobile apps, thus gaining the benefits of data standardization and speed of deployment. Google touts an agency friendly system with multiple user access, and tools to improve tags performance like debugging, and rules, macros or automated tag firing. The Google Tag Manager also integrates with Google product DoubleClick. Moreover, Google Tag Manager is…
If you need a single place where you can handle all the third party pixels, this is a well-suited platform. As well as if you want to keep the deployment independent from all other (and more complex) deployments driven by IT. If you need a pixel to be fired not just when the page loads, but based on user actions, you should use the events and that's pretty complex to handle.
Google Tag Manager is well suited when the marketer or marketing team does not work closely with the developers. In this scenario, it means that the marketer can deploy 3rd party tools such as live chat widgets, advertising pixels, and much more themselves in a timely manner. Google Tag Manager may be less relevant in an organization where the marketer is also the developer or has a strong development background, where they can implement the 3rd party tags directly on the site when they need. But even in this instance, there's still great benefit in using Google Tag Manager.
Selecting elements on a site [object, class, cookie, etc] (to later fire an event, send some data, etc) is very easy with triggers. Want to add an event when someone clicks on a button? Super easy. It was many many DOM selectors and you can even add custom functions if you need to do something more specific
In general, firing events in different circumstances is very easy mixing triggers and tags. You can track almost any element of the DOM and do whatever you want with it.
Testing is a great functionality. Only you can see what's on the site and you can debug it easily by seeing which events or tags were triggered and all the DOM elements involved (and why they matched the trigger).
Working in environments (staging, production) and versioning is easy to do, deploying changes in 2 clicks.
Reports. Tag Commander lacks in term of reports of what's happening. There is an additional module called Attribution Management System that gives you a lot of insights, but more basic reports to understand what has been fired will be useful.
Support. Tag Commander support is very low responsive. It took several days to have the first feedback and generally, it takes a lot of emails to get what you need.
Deduplication engine flexibility. The engine is there and it works pretty well, until you have a slightly different need. In that case you need to implement something custom in terms of implementation, reports, etc. A more flexible approach would be useful.
There are several good integrations, but there can always be more. Native tracking for call tracking solutions, analytics providers, non-Google advertisers would be top of my list.
Documentation is just dreadful. Luckily there are some awesome folks out there doing crowdsourced tutorials (shout out to Simo Ahava) but by and large the Google Tag Manager instructions are worth what you pay for them.
Google Tag Manager makes tracking traffic to our websites effortless, which enables our developers to focus on other tasks. Setting up a new instance takes only minutes and additional scripts can be added/modified without touching the source code of a site in production. This enables our marketing directors to coordinate tests and experiments with minimal effort.
Google Tag Manager is the definition of a learning curve. At the beginning, you can barely do the minimum and it can seem questionable as to why you would use it. However, as users begin to learn its offerings and see how it can do much more, they will have a moment where GTM becomes a tool that empowers their ability to track and efficiently collect data for important business questions.
Planning and communication will help greatly with an in-house implementation. If there are large teams, try to limit the number of people involved to 1-2 developers (back-end dev may be necessary depending on your platform), one analytics marketer and one project manager.
We moved to GTM from a standard Google Analytics implementation. GTM is much more flexible and easier to make changes, especially as the changes relate to multiple sites and environments. While there is a learning curve when figuring out how to use GTM, I believe the change has been worth it because it helps us understand at a more fundamental level how our tracking works and gives us a lot more control over what we track and how.
It let us deploy new pixels/fixes to pixels independently from the IT deployment process.
It let us easily turn on/off and sort the pixel execution based on partners' priority, assuring better data tracking for more important partners.
It provides out of the box pixel implementation for tons of partners, but really often we need to rewrite the pixel from scratch as they're not up to date.
GTM is very useful to determine if a particular element on the site is useful (i.e. is it being watched, is it being clicked, does it help customers navigate through more pages). As an SEO person, I can use this information to decide what to optimize for but also to track progress and see improvements in engagement.
With the use of Google Tag Manager, I was able to easily inject an A/B testing tool which lead to several improvements in lead generation.