Commanders Act offers Enterprise Tag Manager, a product designed to handle website tags - and also SDKs in a single SDK container - through a management interface without the need for technical expertise.
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. It is a free option, vs. the company's enterprise-tier Google Tag Manager 360.
$0
Pricing
Commanders Act Enterprise Tag Manager
Google Tag Manager
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Commanders Act Enterprise Tag Manager
Google Tag Manager
Free Trial
No
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Commanders Act Enterprise Tag Manager
Google Tag Manager
Features
Commanders Act Enterprise Tag Manager
Google Tag Manager
Security
Comparison of Security features of Product A and Product B
Commanders Act Enterprise Tag Manager
7.0
1 Ratings
15% below category average
Google Tag Manager
6.4
56 Ratings
24% below category average
Role-based user permissions
7.01 Ratings
6.456 Ratings
Tag Management
Comparison of Tag Management features of Product A and Product B
Commanders Act Enterprise Tag Manager
7.0
1 Ratings
14% below category average
Google Tag Manager
8.1
67 Ratings
0% above category average
Tag library
9.01 Ratings
8.062 Ratings
Tag variable mapping
7.01 Ratings
8.654 Ratings
Ease of writing custom tags
8.01 Ratings
5.666 Ratings
Rules-driven tag execution
8.01 Ratings
6.761 Ratings
Tag performance monitoring
3.01 Ratings
10.056 Ratings
Page load times
00 Ratings
8.148 Ratings
Mobile app tagging
00 Ratings
10.033 Ratings
Library of JavaScript extensions
00 Ratings
8.137 Ratings
Data Management & Integrity
Comparison of Data Management & Integrity features of Product A and Product B
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.
I use Google Tag Manager (GTM) daily and create tags/triggers for all of our client's websites. It is easy to set up but for some of my tasks, the process does get repetitive so it'd be nice to have a default setting I can use when I have to create accounts, and then tweak/add things to them as needed. It is a great way to collect data and have code on the site without having to log into the site builder all the time. It makes it convenient to make edits or add code after our client's sites go live with us.
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.
No difficult obstacle to overcome but Google Tag Manager can still be difficult for many users to deploy. Sure the basic HTML script can be deployed quite easily, but when you start to require triggers, variables, etc, it can be a little daunting.
GTM does not provide support. This is one of GTM's biggest issues but it's due to the level of customization for each website. If your team thinks they would heavily rely on the need for a support staff it is probably better to invest in a paid service with a team that can support your needs.
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.