Skip to main content
TrustRadius
Adobe Experience Manager

Adobe Experience Manager

Overview

What is Adobe Experience Manager?

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…

Read more
Recent Reviews
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Popular Features

View all 16 features
  • Role-based user permissions (38)
    8.4
    84%
  • Mobile optimization / responsive design (35)
    7.8
    78%
  • Page templates (37)
    7.6
    76%
  • Bulk management (36)
    7.2
    72%

Reviewer Pros & Cons

View all pros & cons

Video Reviews

12 videos

Adobe Experience Manager User Review | Near Perfect Maintaining Sites
10:40
Adobe Experience Manager Review | Quick Implementation that Saves Time
05:23
Enables People to Create - Adobe Experience Manager User Review
04:59
Return to navigation

Features

Security

This component helps a company minimize the security risks by controlling access to the software and its data, and encouraging best practices among users.

8.4
Avg 8.0

Platform & Infrastructure

Features related to platform-wide settings and structure, such as permissions, languages, integrations, customizations, etc.

8
Avg 8.1

Web Content Creation

Features that support the creation of website content.

7.5
Avg 7.6

Web Content Management

Features for managing website content

7.3
Avg 7.1
Return to navigation

Product Details

What is Adobe Experience Manager?

Adobe Experience Manager, part of Adobe Experience Cloud, combines digital asset management with the power of a content management system.

Adobe Experience Manager Sites is an AI-powered content management system built on a scalable, agile, and secure cloud-native foundation for creating and managing digital experiences across web, mobile, and emerging channels. Users can create content and manage updates with re-usable Content and Experience Fragments and deliver content using template-driven page authoring or a headless approach with GraphQL. Interactive WYSIWYG authoring of React- and Angular-based single-page applications (SPAs) is available using the JavaScript SDK. Experience Manager as a Cloud Service eliminates the need for version upgrades and scales within seconds to handle high traffic with guaranteed uptime SLAs of up to 99.99%.

Adobe Experience Manager Assets is a cloud-native digital asset management (DAM) system that enables the management of thousands of assets to create, manage, deliver, and optimize personalized experiences at scale. Users can create and share asset collections and connect to the DAM from within Creative Cloud apps using Adobe Asset Link. Assets uses AI and machine learning to automatically tag, crop, and manipulate images and video. It also offers rich media delivery, technology that automates the creation of unlimited variations of rich media from a single piece of content for various devices and bandwidths.

Additional Adobe Experience Manager applications that integrate with Experience Manager Sites and Experience Manager include Experience Manager Forms for responsive forms creation and Experience Manager Screens for digital signage.

Adobe Experience Manager Videos

Adobe Experience Manager Competitors

Adobe Experience Manager Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

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.

Salesforce CMS, Acquia Digital Experience Platform, and Contentful are common alternatives for Adobe Experience Manager.

Reviewers rate Role-based user permissions highest, with a score of 8.4.

The most common users of Adobe Experience Manager are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(286)

Attribute Ratings

Reviews

(1-25 of 83)
Companies can't remove reviews or game the system. Here's why
Anshum Malhotra | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
  • Authoring
  • Asset Management
  • Adaptive Forms
  • Analytics
  • Security
  • Integration with AI to develop website with ease and with suggestions
  • Speed - when I open dialog and when changes are made - should be instantly updated
  • CRXDE - new fast IDE should be there
Score 9 out of 10
Vetted Review
Verified User
Incentivized
  • It does allow us to stand up a website relatively quickly.
  • It allows us to componentize different parts. When we are trying to get to production, we can segment out the development from the authorship. If we want to have development go all the way through in a dark release, we can do that separately and then have that ready for the authors, and then the authors can pick up the components and create the pages and release those at any time. So they're able to do a lot more independently without needing a lot of development support. Depending on what they're trying to put in production, it reduces their dependency on engineering, so it makes it so it's a lot easier for them to get things out into production quickly. Also, it allows the authors to be able to push their content into production anytime and then they can author it and they feel like they have a lot more power that they didn't have before. We're also creating templates and websites that they can actually get more messages out there quickly to the consumers so that we can like, let's say we wanted to create a marketing site with flexible phone numbers. They could get that out quickly, get the message, get the campaign with little to no engineering support. There might be some but it's less than it was with the other heavy lifting we've had with other content management systems.
  • One of the problems that we particularly have and would love to see a lot of improvements with is the we use cloud manager for deployments. Specifically with the managed services, we have a lot of issues with the fact that it is one pipe and one pipeline. So if we do a deployment, we have one thing at a time and you have to wait for one batch and one deployment to go through. So typically if you push one thing through the stage, you have to wait and then it goes to prime, and then if you have another batch that you need to send up, you usually typically have about an hour or four hours wait while everybody's doing validation and then it has to go to production. So we need to find a way to either have multi pipes or multi-stage ability to be able to get more things staged or ready to go or be able to have a better deployment mechanism to get things into production because that wait time and that it's just the cycle is just hard.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
  • 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.
  • So for us we have to make changes and have our developers tweak things. So our instance of Adobe Experience Manager is not out of the box, so it ends up that we have multiple versions out there, and so it doesn't streamline as effectively for us. If I was giving advice to somebody, I'd say stick to the pure vanilla AEM as much as possible, and don't let yourself get pulled into these extraneous requests to do something different, because then that ends up breaking. What is the benefit of using Adobe products is that they all fit together seamlessly and then change in one place can happen across the board. So it was partially our implementation and not having a strong enough "no" to stakeholders who wanted to individualize or make changes.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
  • When it comes to the website, we can also build around the side, but the kind of UX, the rich UX, animated UX, or the UX that goes through a transition. All those kind of stuff is very powerful. The number one for the sustainability product due to a lot of KPAs. Because today for sustainability there are a lot of KPAs available in the world. And when we are demonstrating and presenting in the website, it needs to be very intuitive and very good-looking. And it should be appealing as well as very connected. So that's what experience is about. We are able to get that in an EMS.
  • If you look at AEM, I think it's a very mature product. I mean, every product can be improved on a normal basis. New technology will come, you will add new technology, for example, you add all the AI and all this kind of stuff. That's all. But otherwise, if any particular thing which I say, oh, if that is, that it would have been best, I don't think so. AEM is pretty much a very comprehensive product. I would say that.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
  • 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.
  • It's still, at the end of the day, a very traditional platform in by that we mean it's a bulk air platform. There are too many components, which means a lot more operating costs in terms of manageability and things like that. We have tried to streamline that as much as we can, but the multiple components still exist. If anything, Adobe could kind of think about that a little bit to maybe decouple some of those and make them a more slimmer platform. I think that would help. I think that a lot of customers are still in the traditional environment and as we ourselves are looking to move to the cloud, I think some of that will get taken care of, but I think that's one area where it would help if Adobe can put some thoughts into that.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
  • Authoring experience and digital asset management are great, which is very important for the content management system. It has a lot of integrations. Adobe is always evolving this product, so that is really appreciated. It has various connectors, which can be customized based on your requirements.
  • I would say there are some products called the customer experience product called Adobe Experience Cloud. And when Adobe Experience Cloud has asset cloud, asset Cloud does not have a great integration with the AEM, so they have to improve that one. Obviously.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
  • The integration between Adobe Target and Adobe Experience Manager was seamless. We have a seamless integration from the AEM to Target and that will help provide personalization to the users. Better personalization can be done from the AEM to Adobe Target.
  • So far I don't have any pain points actually. As of now, we are only using the main site. We are planning to bring other sub domains into AEM. So as of now, there is no pain points as such.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
  • I've been involved with this product right from the days as a developer myself. I worked with other content management systems before started working on Adobe Experience Manager. I think the key advantage of using AEM is really how well it integrates with the ecosystem of the marketing stack. I don't think there's any other product out there in the industry that can beat that. It truly becomes that core pillar around that marketing stack in the industry. It's easy to deploy sites, the total cost of ownership that I think definitely was resolved by going to cloud. You can definitely say that. You can really do a lot of cool things there. There's absolutely nothing you can't do on AEM, I can say that.
  • It's a well-engineered product, so it's supported and powered by open-source stack like Apache Sling, OS G, and all that stuff. That definitely gives it the edge on the performance side.
  • 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.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
  • It enables people to create their own branding, their own messaging across the site, multilingual, multinational, while maintaining their brand ensuring that it's compliant with not only their brand, but also their legal necessities. And spin it up very quickly
  • It's hard to say off the top of my head. Like I come across issues almost on a daily basis. But they're small things. There are things that would make my life easier as a developer, right? If certain configurations maybe were a little more intuitive or automated. But I also think that it's improving a tremendous amount and we just went live with am as a cloud service customer on like, just this past week and it was one of the smoothest goli I've ever had. So I think it's, it's come a very long way.
September 11, 2023

Adobe Experience Manager

Score 8 out of 10
Vetted Review
Verified User
Incentivized
  • I love the ability to publish my own work and schedule it. That saves us a lot of time when something's going to be implemented on the weekend or in the wee hours of the morning. Then we can schedule it and it easily allows peer review so my colleagues can go in and see my work, make sure it's correct and we can sign off on it.
  • In our organization, we've done quite a bit of customization on certain components of the product. For example, it's a bit limited from a column control for content perspective. So we've had our developers come in and make changes to the components and deploy them so we can use them to deliver the business requirements.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
  • N/A
  • Our current challenge right now is moving to the React tech stack. So all of our developers have been working on that and there's been a decent amount of friction with it. But that's just any sort of new tech stack happening that's going to happen. So it was to be expected.
  • Another con is just simply having that non-agile development requirement to be like, "Hey, we wanna see this happen. Okay, now we've got to wait six weeks for that to get deployed to production." But again, that's the sort of thing that just is a normal part of doing business with development.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
  • As a developer. I can say a few things. Like the first good thing which we like when moving to AEM when as an author, like when they enter the content, they can see the live copy there itself, which it was not happening with the previous CMS system. And it's really cool. Like in terms of what to say, the package upgrade, like service pack, upgrade it's keeping the application alive. I mean the downtime which we face as part of the EM is very less impacted.
  • The CMS we are using earlier, I feel more comfortable the AM now, but pointing out counts I'm really not getting anything into mind right now.
Score 7 out of 10
Vetted Review
Verified User
Incentivized
  • I think some of the strengths really are that kind of ease of use of drag and drop. Once you have a developer come in and really customize the application to like what a client specifications are after that point you really can lay back on the development work and really rely almost entirely on the, what Adobe calls the authors to actually build and maintain these websites. And they really have thought of a lot of those edge cases where things can break. So everything is kind of, I don't wanna say idiot proof because authors are smart but it's made in a way that you can't really make things too wrong and that in with whatever you're building, it's always up to the brand standards. It's up to the accessibility standards. So whatever they're building is ADA compliant and things like that. So everything that you're doing is still maintaining a proper website, which under the hood websites are incredibly complicated involved so many different technologies. So to be able to simplify all of that to a user is incredibly powerful.
  • From my personal experience as a developer, I think Adobe has a lot of work to do with their documentation. certain things they're very strong and they're very like they detail things out great. Other things that haven't been updated since like 2018 don't work anymore and it requires a lot of trial and error to actually figure out what needs to happen. A lot of the time you rely on other AEM developers inside in the inside the community forums that basically have to say, these instructions don't work, has anyone actually gotten this to work? And other people that have done the work and figured out how it actually works have kind of filled in those gaps. So it's great that those exist but it would be great if those holes never existed in the first place and Adobe's documentation really just was robust enough and didn't have typos and really got refined more frequently.
  • So from my experience, that's definitely where I think Adobe could really improve the work experience because it shortens development time, it makes my work a lot easier, which means I can deliver things way faster and things move a lot quicker because I hate having to say I'm doing it the way Adobe says I should do it, but it doesn't work still so I need to figure out what's wrong. that's not a fun thing to have to talk to a client about because then they get confused and are confused why Adobe isn't working the way it should be. it just creates kind of some tighter timelines and things.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
  • The whole headless piece of it wherein we can create content and you can channel it to any sort of channel because now it has this whole piece where we can create content once and use it multiple times. I think that's the piece which I really like about it.
  • There were a couple of pieces which initially the version management and the digital asset management piece was not available. Which was like the key feature. Like I created a document and I wanna create versions of this. I think that was not there, but I think as of today, I think it's still there in the product. But there are a couple, couple of features which I would like to see, but I'll have to kind of think back and get back to you because I don't have them right listed.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
  • I'd say the overall digital way to represent the data is good. It's good that you don't have to have the technical skills and you can just come in and use the drag and drop features. I like how the data's just there so you can play with it.
  • So for us it was a little bit of a struggle to get data into AEP. But that's out of Adobe's realm.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
  • Definitely with like asset management, it's really nice being able to upload things and have it in different renditions across the entire board. also I think it's very beneficial that we can all communicate on one platform and it's useful for the design team, web design team, content managers, and everyone to be on one area and go through the entire process together.
  • I think a lot of the things are gonna be addressed now, like with the launch. I think it's like a firefly that's coming up that seems very beneficial, especially for the design team where it's like we're trying to create all these different assets and bring it into one area for people to use in multiple different areas. I think, and pretty much that I don't really have anything too negative to say about it because it's a very like uniform and unique experience overall and it's very easy for us to use.
September 07, 2023

Adobe Experience Manager

Score 9 out of 10
Vetted Review
Verified User
Incentivized
  • I guess I'm just so used to doing it. I do enjoy the content fragment aspect of it and that we have a repository for the content, and then we are able to help us get that to a page, which then goes live. It's nice to be able to have a repository that users can access and we don't necessarily have to give them access to the webpage itself. We can say, "you stay in this box here and only edit this," which helps us to better maintain the integrity and look at design of our websites.
  • Well I guess within the content fragment aspect, we do find that it can be a pain to have to activate the fragment, then activate the page, then activate the detailed page, then activate a would-be parent page above it - just to do all these different activations to get the content live on the website. It would be nice if we could publish it in one spot and it's activated through all the changes that are pulling that same data. So yeah, that would make the process a lot easier in regards for users. So we don't have to train them to say, activate it here and then you have to activate all these other steps to make sure that your content goes live. They could just publish it in one place. That would be very helpful.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
  • The ease of use and the user interface and the ability to have different user groups. For example, last year we implemented an internal audit for company approval. By using the built-in AEM workflow, we were able to achieve and make sure all the content authored by the content production team is sent through and reviewed by our content editor team. Every trace of the changes is captured in the workflow archives. So that's a very great addition to our implementation last year.
  • I wish Adobe could have some documentation or maybe training sessions, webinars, and maybe more people, to talk about how to improve the platform. So for example, we're building the new templates for web pages. And sometimes when we work with our in-house IT team, and then we have to do a very good segregation between content and code. And for one instance we deploy the code, we accidentally override the templates that we authored before. So there's not much documentation that can be found on the Adobe Experience League.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
  • All the workflows that we built, it was very easy to do. That helps it a lot.
  • It's easier for us users to work on it, go into it, and start using it. It just makes this process a lot simpler. And even for other people who have to approve, it makes it much simpler for them. So simplicity, accessibility.
  • I think it goes back to what I said on the classic UI. There's stuff like the segmentation or the tools because I know there are other areas you can click on. On the front, when you land on the page, the front of the page would be easier to see. Sometimes I have to use segmentation. I have to go to classic UI, put it on there, and then after that, so it takes a little bit longer to process and even apply it. So it's really back and forth. But other than that, that's the only thing I can just ask for room improvement.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
  • Having one centralized repository area for our design team to go. It's also great for those who are a little less tech-savvy and all the inputs and outputs. So when a request comes in, we're collecting everything we need to begin the work, but we can also use it to update. As the job changes or as the scope changes, we can be more dynamic and agile. So the pro is that we can, again, have one standardized place to keep everything, so it doesn't really matter who's looking for it, they can find it.
  • I can't really think of anything. I actually was a bit overwhelmed when I first started using it because I think a lot of people feel the pain of another system. But again, they all talk to and work so well together that it's kind of hard to find anything to crash on.
Kwazi Henderson | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
  • Cross-collaboration within the system allows my team to store and share assets across multiple sites/templates with ease.
  • Dynamic display of content
  • Easy to use user-interface
  • The ability to create multiple paths and organize folder structure
  • Integrations allowed with other marketing applications
  • In current implementation it would be nice to have the ability to create simple isos-graphic animations out of the box.
  • Timeline feature for AEM Sites versioning tends to move at a snails pace
April 04, 2023

My AEM Experience

Score 8 out of 10
Vetted Review
Verified User
Incentivized
  • Easy to use once you understand the concept
  • AEM Assets help provide good clear workflow
  • Make website maintenance/update easier
March 24, 2023

Satisfied Customer

Score 9 out of 10
Vetted Review
Verified User
Incentivized
  • Reusability
  • Flexibility in creating pages using fewer templates
  • Modularity
  • Headless Schemas which are OOTB are limited
  • Providing more flexibility in orchestrating CI/CD pipeline
  • OOTB integration with API for email functionality compared to default SMTP
Return to navigation