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

Learn from top reviewers

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

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.1

Platform & Infrastructure

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

8
Avg 8.2

Web Content Creation

Features that support the creation of website content.

7.5
Avg 7.5

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
Security

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 From Top Reviewers

(1-5 of 84)

AEM provides flexibility and control

Rating: 10 out of 10
May 30, 2024
Vetted Review
Verified User
Adobe Experience Manager
9 years of experience
We use Adobe Experience Manager, both for our content management system for our website and also for emails using Campaign. AEM Is a vital tool in managing our web content. It provides the ability to create templates and structured components to build a unified design, branding, and consistent placement of navigation throughout sites and across the university, but also allows the flexibility to personalize and customize pages. Recently, we were able to use an HTML component to drop in just enough JavaScript to automate a sorting of cards for a feature on our site while still keeping the template and branding of the system in place. We use Campaign to send email to our faculty and workshop participants. The analytics we can see in Campaign’s reports help us determine message delivery and gives us insights on how to improve our messaging.
  • Customized templates
  • Flexible components
  • Access management
  • Asset management
  • Scheduled publishing
Cons
  • A find and replace feature that could be set to search the full stack or a specific hostname.
  • The ability to use snippets of content across pages (like inheritance) but not in just one directory/folder.
  • In the column view of site structure it would be nice to be able to search/sort by date.
Adobe Experience Manager allows web content managers to share the work of site maintenance while being able to set access/publishing. Editors don’t need to have advanced HTML experience to make edits or even build new pages. Having workflows to allow authors/editors to request publish gives content managers the ability to review content before it is made public. Being able to set on and off times for pages helps control when content is released and retired. AEM is not ideal for highly specialized and customized designs with lots of interaction/automation.

AEM, value that trickles

Rating: 7 out of 10
May 30, 2024
Vetted Review
Verified User
Adobe Experience Manager
3 years of experience
AEM is leveraged by our org for managing the customer experience on our digital channels. The solution serves up both static and dynamic content for web, mobile and email channels. It also manages our assets including brochures, collaterals and specifications. We also use the solution to craft forms on our sites and capture responses.
  • Centralize and manage content
  • Centralize and manage digital assets
  • Centralize and manage training assets
Cons
  • More governance around content management
  • More seamless integration with AEP/AJO
  • UI/UX enhancements around navigation
Well suited for serving static site, channel and app content. Managing and organizing content, assets and training materials is very streamlined. AI/ML capabilities are evolving well. Less suited for dynamic personalization scenarios and approval related workflows. Integration with AEP/AJO is not very robust and involves too many clicks to get what you need

Adobe Experience Manager Review

Rating: 9 out of 10
September 12, 2023
SS
Vetted Review
Verified User
Adobe Experience Manager
23 years of experience
We use it to support our websites, as right now what we're using it for is our public websites. It hosts all of our public sites, if you're looking out at like anthem.com, elancehealth.com, and carelon.com, it's our public presence, so it allows our authors to be able to author content quickly and get it out to production. It allows us to get quick speed to market for any of the changes we need it to get out there. Also, there is another part of the company that also uses it for EAP, messaging, and campaigns. We also use different parts for other branches of it like Adobe Target and Adobe Analytics. So we use it to get more information about how the product's actually being used, and how the sites are being used to make sure that we get the best information out there for the customer.
  • 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.
Cons
  • 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.
It's well suited for companies that have a need to get things out to production quickly. They have a stronger marketing department or one that can be trained. Understanding that you need to get things a lot more streamlined, you need to reduce your overhead a little bit, with the engineering you get stuck in a cycle. So if you need to break the development cycle a little bit and just reduce your time to market, if they're getting stuck on being able to get innovations and items into production and give a lot more power to your marketing, it's a great product for that. And then it actually makes your site more dynamic. So if they need more dynamic content, more dynamic sites, great product for it. And also if you have smaller sites that you're trying to do, this is more flexible for you. I think it wouldn't be good for someone who is maybe a small company that doesn't have all the technical skills to do it, but it may not be, maybe a mid-size the larger company. It all depends on how they want to do it. I think it could be the right size for anyone. I'd say it'd have to depend on the use case.

Adobe Experience Manager Review

Rating: 10 out of 10
September 11, 2023
ht
Vetted Review
Verified User
Adobe Experience Manager
12 years of experience
In my current organization it plays a key role. Most of our customer-facing web applications are deployed on Adobe Experience Manager. So it's our go-to platform for all our external-facing websites. The healthcare industry includes several key web-facing features like finding a doctor and our patients and other audiences come to our sites and book their appointments for care. And we also have to host kidhealth.org. So that is the number one kid health-related, pediatric-related health content site in the US. That's hosted on Adobe Experience Manager and that's a big success story with Adobe as well. We are moving to the cloud, and that's an ongoing project now. So we are completely going to cloud very live soon.
  • 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.
Cons
  • 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.
I think it's definitely well-suited for any large-scale website deployments. If you're really deploying multi-region sites spread across the world, it all comes out of the box, you don't need to worry about latency or anything of that sort. I think it definitely works well for any of the large-scale deployments.

Where it may not suit is if you really have more transactional sites I think things of your AEM are more like a stateless in nature, so it may not suit well for those use cases, right? You can't build a banking application on AEM, right? But you can always build the customer experience pages on AEM, even for banking. When it comes to having to log into the bank portal, it has to take you away from the whole banking application to move away from there. So, that's where I think it may not be suitable.

Adobe Experience Manager Review

Rating: 10 out of 10
September 11, 2023
LC
Vetted Review
Verified User
Adobe Experience Manager
12 years of experience
I don't really use it in my organization, I use it in other people's organizations, so I'm on the development side, architectural side, so I configure, develop, build. I don't actually use it to author the site itself but I empower other people to do that for themselves.
  • 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
Cons
  • 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.
It's well suited when you're building a fast changing, or frequently changing dynamic website that is looking to engage your customers on a regular basis. If you have a static site or a smaller site or a site that can be maintained relatively easily by one or two people, it might be a little bit overkill for you. probably not the best option.
Return to navigation