Adobe Experience Manager is a combined web content management system and digital asset management system. The combined applications of Adobe Experience Manager Sites and Adobe Experience Manager Assets is offered by the vendor as an end-to-end solution for managing and delivering marketing content.
N/A
Google Tag Manager
Score 8.4 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…
This tool was not very helpful. We switched to unbounce since Experience Manager was not a complete solution. Our team members have worked with several of these tools and found this one to be the least comprehensive.
So one of the primary focuses in the company has been SEO, and it does not seem well suited to SEO. For instance, how we set up the alt image tags. It's pretty tricky and there are multiple steps to do that. So I would like to see an Adobe Experience Manager that is more focused on out-of-the-box solutions for SEO, schema coding, alt image tags, and other sorts of SEO functionality to have that more built into the vanilla version of the product. Well suited? It's very good at scalability. And because we're managing such a large number of hotel properties, it works well for an enterprise.
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.
It is able to support our incoming volume. We're one of the largest in what we do in the country, and we've not had any issues in terms of how it performs, or how it scales our customers coming in. It's a fairly stable platform. It is also a very intuitive platform in us being able to give our business users the ability to come make changes and request additions without going through a huge lift in getting those requests implemented. It has also been a very developer-friendly platform for my team to be able to develop, adapt, and build. We're also expanding on being able to use AEM both as a pure content management solution and also as a headless content solution. So that way we are trying to build a unified content platform that would allow us to create, publish, and manage content across channels from one place. So it's fairly intuitive that way. It's fairly scalable. Obviously, the modern tooling helps, but overall I think it's been a good experience.
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.
I think some of the key things that can be done better is today we have more point solutions for different things like personalization. We have Adobe Target and for email marketing, we have Adobe Campaign Marketer and all that kind of stuff. But truly I have worked both as an implementation partner for Adobe as well as now I'm a client of Adobe. Being in both those shoes, I can say that we can do a lot better in terms of beefing up the capabilities of AEM, bringing personalization and search and content search experience closer together. It would definitely put Adobe Experience Manager in a different league if we can bring all those personalization capabilities together. I think initially the content management systems, the market was mostly meant to serve static sites. It never matured into that full-scale content personalization being married together. I think that's one area where if those integrations rather than being point solutions, if those capabilities can be made more native to AEM, I think it would definitely be a big sell for a lot of customers.
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.
We had and still have a fantastic experience using Adobe CQ. Lots of flexibility, great integration with other Adobe products we already use and a powerful technology make it a great fit for our corporate environment. Also as the community grows, it makes it easier to network with other developers and users to get new ideas on how to continue to get the best out of the software.
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.
From our learning curve until we got better. I'd say as we're moving forward and we're making more customizations and we're getting used to it, I'd say it's about a seven or an eight. But as more innovations and more information comes out from Adobe as they make more changes and they make improvements, I'd say they're getting probably about an eight right now.
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.
Being part of Adobe Suite means you are already notified when the tool has any outages. However, I have never faced unplanned outages. Whenever you face any issue with the site, it is clearly stated if there were any planned outages and how quickly you will be back to normal. So, I will say that even the outages are planned and managed in a great way like their other services.
With respect to performance, Adobe experience manager is one of the best in the CMS space. We didn't observe frequent slowness on platform, however the systems which are accessing experience manager should be of good specifications without which slowness would be observed. Adobe experience manager works well in integration with other solutions, unless the destination application is designed to trigger frequent calls to AEM.
Adobe Experience Manager, in all its capacity, is a great alternative to any other CMS you are using. It helps in rapid development and makes life easier for maintaining the website for multi-language sites. Technical know-how is eliminated at content authoring. Better documentation in terms of live examples with videos would be appreciated.
Depending on your individual needs, It is really quite simple to create an authoring experience for a website that looks really good. I have been part of many implementations and many teams and have seen many projects that were super successful and others that were not implemented well. AEM has room for a lot of flexibility in the implementation process compared to other CMS like SharePoint
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.
At Canadian Tire Financial, in the time I've been there, we've always used AEM, but in past places I've used WordPress, I've used Squarespace. Things that are more general user-friendly where you're like building your own blog or you're creating a small business website where it's basically just text, you're not intaking information or something like that. I think the customization options in AEM are huge. My experiences with WordPress were pretty straightforward. Again, it was like, I don't know, like college newspaper website or something like that where you're just like putting content up for people to look at. You're not necessarily taking in any other information. Maybe you might allow people to log in or something and save articles or something pretty straightforward, but then even then I remember that stuff taking me forever to do, to figure out and scroll through tons and tons and tons of documentation. It's just not fun. No one enjoys doing that and then even then you might not have the answer available to you. And that's so frustrating. Hey, it's super user-friendly, figuring out the content editor is pretty straightforward. You're not clicking around and being, "what the heck am I looking at?" Or you're not looking at a bazillion menus to be like, "maybe the thing I want is in here." I can't stand that. I want to be able to look at a page, see what I'm going to be getting in production, and then publish it. I don't want to look around in menus to figure out how to add something to a page.
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.
Instead of being directly involved in the tool purchase, I am involved in analysis or what we can use to maximize the tool. Small organizations may find it expensive. However, if the team or organization focuses more on your ROI or the features you will get, then it will definitely be worth it. Pricing is based on a number of factors, including team size or the use of the tool. The user can select the pricing option that best fits their needs based on the number of form submissions they make or the number of pages they wish to publish on their global/multisite sites.
The professional services team within adobe is one of the best in terms of technical and solutioning knowledge. However, considering the billing charges of adobe professional services team, it is always recommended to involve them during platform initial setup or when a complex solution is to be built with platform customizations.
This actually has been great for our websites. In the time that I've been with the company, we've seen at least the profitability of our websites because we are measuring that through analytics. We've seen it double since using it. We were using it when I first started with the company, but we've gotten better at how we're using it and really optimizing the use as well as the design. I think that that's made a huge difference. We've seen a huge jump in the performance of our websites with maintaining users and the e-commerce side of it.
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.
