Adobe Audience Manager is a data management platform (DMP) that is integrated into the Adobe Marketing Cloud.
N/A
Adobe Experience Manager
Score 8.6 out of 10
N/A
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 9.3 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.
Adobe Experience Manager proofs to be the right solution for large corporations with multiple business units and brands, since most of the functionalities are oriented to that. Other similar tools are more basic with regards to the available options and are also not that …
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.
AEM provides a better way to control user permissions which Content Marketer is lacking. Moreover, the ability to integrate with the Adobe Target product provides a wider range of audience segments that can be targeted besides the default author-targeted functionalities. It …
If you are already using multiple other pieces of the Adobe Experience Cloud stack, adobe audience manager is an easy choice. It allows for quick and easy data activation for your first and potentially brokered 2nd party data. However this product will likely be absorbed into the adobe experience platform (AEP) soon. In the end I would wait to see where adobe is truly headed with this product before investing heavily without additional heavy adobe investments.
I'll answer the second one because I mean, the first one I don't have an issue with. The second scenario is we oftentimes have the need to spin off very small campaign style sites or sites that generate leads but are unbranded and that sort of thing. So that's hard to do in AEM because you have to then create another organization within AEM to do that. And we're talking about sites that are maybe five to 10 pages in size. So we've been investigating Edge, but then that's a different workflow, so we'd have to train people on that. So it would be nice if there was something within the AEM structure that could allow you to do something very similar to Edge, where you make some small micro sites that are not necessarily branded, that you could still host within the platform and not have to retrain everybody on a completely different platform.
I have found Google Tag Manager as the go to solution for managing all of your event and conversion tags for your website. Not only does it make it easy to manage all of your tags in the one place, it is fairly intuitive to use and there is plenty of videos and help documentation online to help set up what ever you need. No scenarios come to mind at the moment on where it is less appropriate to use.
We are able to generate reports that provide valuable insights into potential customer behavior, allowing us to better focus our marketing efforts.
By allowing us to understand who are key audiences are and how they overlap with other brands and products, AAM allows us to get a fuller picture of how we should target our audience.
Reporting in AAM is wonderful in that it is easy to understand and exportable. The use of graphics and updates make it easier to share insights with various team members--even those with minimum experience in marketing and analytics.
It allows us to scale so that we can make a change on a global footer. And it applies to all of the different property websites. It allows us to set up components and compartmentalize things in a way. The big thing is that it's scalable. And then it also ties into Adobe Analytics and other Adobe products. So we are a complete Adobe shop. Every Adobe product that we can use, we use. I don't think we do it for marketing so much, but for doing target testing and analytics, data scientists are using the same product and so it all speaks.
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.
There are some glitches in permissions inheritance that require us to toggle a save on permissions in groups that inherit from a group that was recently updated.
Large packages require stopping the workflow launcher OSGi components or many workflows will slow down the server.
Locked pages are hard to find unless I use /siteadmin... I often hear that the CQ tools will go away, but if we lose that, some small things might be harder to do, like finding locked pages.
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.
I haven't found another option for us to use especially one that is free. Down the road we may go a different route but for now GTM is a good option and does what we need it to do. It'd be nice to get more support or more integrations but with the free version there's only so much one can expect to get I suppose.
Overall usability is great, as are most of Adobe's software. Maybe a UI refresh could make it a bit easier to do advanced functions or reporting but, overall, it works very well. This is something you take for granted with Adobe solutions because when you try another vendor you realize how bad it can be.
Adobe Experience Manager overall is fairly easy to use and caters to a wide range of users when it comes to their technical abilities. It has the flexibility to enable UI/UX designers to pop in and easily design new content with drop in components. It also has sufficient capabilities for those who are more technically inclined and want to dig more into custom code or solutions
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.
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.
AAM has good support, but the support is not as available, due to waiting time and queue. The instructions presented are available, but it navigation is not easy between pages. However, instructions are usually direct and straightforward, but any underlying thoughts or questions won’t be easily answered without support from their service.
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.
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.
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.
I personally like the Adobe Audience Manager interface and it's easier to use for beginners. It also has some features that Google does not, nor do its other competitors. It is worth the money and time spent, overall. I feel like it gives a bigger and more in-depth picture to our company's audience than other programs.
SSO is one fits all, so we don't have to have a separate SSO for each application of Adobe The integration with Analytics works perfectly and bring directly value really quickly Target remains more complicated to set up, but can also bring a lot of value once integrated with the rest of the Adobe platform The fact that the solution is Cloud services is also a big advantage for maintenance
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.
too soon to tell on increased conversion rates based on external marketing factors in play but having increased visibility into customer engagement trends will most likely lead to improvement of our conversion rates.
There have been productivity gains from the perspective of actually migrating all of our externally managed sites to the same in-house Adobe Experience Manager platform and then being able to utilize those universal components.
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.
