Adobe Dynamic Tag Management (DTM) was a tool used by marketers to manage tags, and for collecting and distributing data across digital marketing systems. Adobe DTM is a legacy, and it will not receive feature updates. Adobe invites users to upgrade to Launch on the Adobe Experience Platform.
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.
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 …
If you're on the Adobe stack at all, you absolutely need DTM. It will make your life infinitely easier. It's so simple to update your Adobe Analytics code and have version control, and when we implemented Adobe Target, it took literally less than 15 minutes for me to do. I also think it's significantly simpler than Google Tag Manager. I went through all manner of difficulty when implementing tags on that and have not had similar problems on DTM. If you're frequently placing pixels, it's a great tool that will speed their deployment. The only situation in which I think a tag manager is not appropriate is if you have a dev with too much time on their hands. Otherwise, get a TMS and get DTM.
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.
It is a rules based tag management system that allows the application of tracking pixels much easier than hard coding.
By placing 2 pieces of code on the top and bottom of each page of a website, we can create rules that track certain events and relay the information back to Adobe Media Optimizer and Google analytics.
It has simplified the coding process so one doesn't have to generate tons of gory javascript to deploy on each individual page to get tracking.
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.
Can sometimes be difficult to troubleshoot bugs/issues as they arise
Sometimes difficult to set up restrictions on how components can be designed to make sure they fit in with existing content
While the integration with Adobe target works fairly well, the process can be a bit opaque and hard to understand, making it difficult to troubleshoot when issues arise
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.
It depends if it is from an administrator point of view or from a business content author point of view. I think from business author point of view the solution is good and with the GEN AI capabilities coming it is doing better and better, however from an administration point of view there are still a lot of improvements to ease the maintenance of user access management and as well as the integration configuration aspect.
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.
Although it is a newer product to Adobe, they seem to truly care about our challenges and are very proactive in making sure that we have the most knowledgeable support available in a timely manner.
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
Adobe DTM provides a more secure data analytics solution. It is customized and best used on large scale deployments of websites with pages 10,000+. The Adobe Analytics tool, once learned, is very easy to use and provides more robust, customized graphics and ability to export data to "securely" via FTP from the cloud to SQL database.
Overall, I prefer AEM as an enterprise site management tool. It allows levels of access control and delegation, while leaving the server management and updates to a specialized team. I do miss the flexibility of being able to search and replace that I have in a WordPress site, and I miss the ability to have one file for redirects like I had in percussion
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.
The key factor is that my devs are not tied up with petty things like adding JS or advertising pixels. Simple work like that can be handled by me while they work on feature development.
Release cycle is much shorter when a dev is needed, say for a direct call rule that involves JS being written. We don't have to go through the normal release cycle and can do it on an ad hoc basis without all the rigmarole of a hot fix.
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.
