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

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
Score 9 out of 10
Vetted Review
Verified User
We use it to manage the web page content of almost 4 different enterprises. We use it to create, edit, arrange, organize and redistribute content to all the world. It means we create content yin local and foreign language. Knowledge content, news content and events content. We also manage assets like banners, logos, photographs, pdf files and more.
  • site map display
  • Arrange content using tags
  • Editing web pages
  • Asset administration during creation of pages
  • Load times for components on creation
  • More column control
  • Open to HTML edition
If you have content for multiples languages it works really well, cause you create the model page with the original content. Then you just "recreate" the page as many times as you like and just replace the content for the new language. the style keeps the same and for end user is like the content was created for them. I think Adobe Experience Manager is not suitable if you only create landing pages (like for ads) cause its so powerful that it will be a waste in my opinion.
Anshum Malhotra | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
I am working as a frontend developer(ReactJS) on a Client Project with Adobe as a vendor worker through my own organization. Also, I have knowledge of Adobe Experience Manager. Business problems the product addresses and its scope: - Authoring(WYSIWYG) - Workflows make it easier to perform several tasks - Asset Management - Security - Used Java, JavaScript - most functionalities can be achieved easily - Single Page Application(SPA) with AEM - Integration with Magento and Analytics - Commerce Website
  • 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
Well suited for commerce (Magento), authoring, forms, and assets
Less Appropriate for small/medium websites and fast development
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Using it to create SPA(Single Page Application) with AEM in a Live Project. Client wants fast rendering and Authoring features. AEM fulfilling the demand.
  • Authoring
  • WYSWYG(What you see is what you get) Editor
  • Asset management
  • Speed of development
  • Vault - Repo inbuilt - IDE
  • Integration with others
Best Suitable:
- Where there are Asset Management required
- Forms - website that have many forms to manage
- That require regular updates/changes

Less Appropriate:
- Small Websites/Businesses
Score 9 out of 10
Vetted Review
Verified User
Incentivized
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.
  • 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.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We use it to manage websites for 70-plus hotel properties. Our stakeholders submit tickets, we use it in conjunction with Workfront, and then our team implements changes on the website. We use the DAM for images. We use content fragments to control different sections of the website. So it's basically a website manager for a big enterprise website of more than 70 properties.
  • 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.
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.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use Adobe Experience Manager for our websites. All of our websites are built on AEM because the website gives you another mind-blowing look and feel. Experience of the UX is very important and we use AEM for our sustainability platform where we capture all the sustainable data across the globe and then we create a sustainability footprint calculator as well as part of the platform and show it to our customers. So to tell the customers that's how our products are so sustainable. So it's a sustainability platform that you built completely.
  • 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.
N/A
Score 8 out of 10
Vetted Review
Verified User
Incentivized
It is one of our customer-facing channels. We essentially use that as our acquisition channel for our customers to come in and go through an application process and apply for a product that we provide. That's essentially our main platform of engagement for acquiring new customers.
  • 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.
I think Adobe Experience Manager is great when you look at when putting content out, like not just for marketing, but also for things you know that are not very transactional in nature. For example, your acquisitions or KYC or running some marketing campaigns, something more content-rich as opposed to something that is more dynamic and more transactional which tends to pose a challenge. It's a rather bulkier platform for us to use as day-to-day transaction reporting. So I think that's how I would look at it.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
It helps the customers get a great customer experience and digital experience, and the website built by Adobe Experience Manager is great. It helps content authors quickly build the content, publish it immediately, which will be available on the site within half an hour maximum. Additionally, it has seamless integration with the different products that help to have one enterprise cloud solution, and there we can have customer journey tracking as well as personalization and even content management. Great content management. So that's a reason it's a great product.
  • 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.
Basically, it has a great asset management system. And then it has a great cloud solution. So availability wise, 24/7, and also easily scalable. Internally it has a lot of continuous improvement tools like CACD and it also has the cloud manager product. Using that one we can easily deploy and integrate our new components easily. And it's a very useful tool for marketing acquisitions.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We have close to thousands of web pages. When we create content templates for each of those pages, the majority of those pages fall into 14 to 16 components. The business will give the content writings to the authors, and then they'll publish those pages using those components. For business problems, we need a management system to host our Juniper website. So AEM is like a CMS platform where we can launch and publish Juniper content for the customers. Where the customers can see all the things we do, the product information, customer case studies, and a lot more information we put up.
  • 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.
Publishing the content on the production servers is seamless. Just build over pages with the predefined components in the template and publish it. It's seamless and can be done very fast. When you consider the other platforms' workflows and all, it will be a little bit tough. I believe the workflow AEM is good because we can publish the content in a few minutes.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
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.
  • 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.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
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
  • 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.
September 11, 2023

Adobe Experience Manager

Score 8 out of 10
Vetted Review
Verified User
Incentivized
Our group is responsible for content enablement and content management. We access the product, make changes to our different websites, and add, update, and delete content. It's site maintenance for our various sites, but it also allows us to implement changes quickly as opposed to waiting for releases and encoding code updates. It allows us to do things in real time.
  • 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.
It's definitely appropriate for changes. So if you want to implement changes quickly. But where it's less appropriate would be where there's specific functions like where we want to capture different pieces of information from a user, so that type of thing that requires the custom code development like I spoke of earlier.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
So for Canadian Tire Financial Services, we use Adobe Experience Manager for all of our online offerings, so our banking portal, our credit card applications, and our landing pages for social and paid search. A generic non-authenticated, non-banking portal website with all our card comparison options and stuff like that. So basically any content that's online for us is on AEM.
  • 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.
I think it does everything that we need to do. Pretty frictionless by and large. I think I've already kind of covered this, but I think that a lot of other content management systems that I've used in the past do struggle with having to basically do a French and English page at the same time. There are obviously development options you can have for a lot of those other ones. I find it pretty tough to use and they do rely on you building a second site. Whereas with the internationalization translator, you can be like, okay, "well this is what that's called in both English and French, and it's going to be the same." It also makes it straightforward for making changes and then you can track those changes as well.

What else do I really like? Being able to customize all of your components, you do have those development options. Yes, they do take a long time, but you know, you're not just stuck with what's out of the box. I don't want to name names, but there are other content management systems out there that really don't give you options to plug in whatever you want. You're just stuck with whatever tools they give you and making those work, which is always tough. I feel like we've managed to make it work because there are so many customization options. If we wanna see something happen, it's just a matter of finding someone who can develop that. Like we haven't really run into it. That's an absolutely a hundred percent not possible thing to do so far. There are things that we obviously can't manage within AEM, like security stuff, like firewall and stuff like that, obviously. Maybe that theoretically is something that I don't even know if you'd wanna do that.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Like as part of marketing team, we are responsible for, you know maintaining and hosting the website for our company. Like and also we made a lot of other applications. So these earlier we were using another CMS solution, so last three years back we moved to AEM solution. Like considering like this product have lot of benefits and compared to the previous one, which you're using, among those that I would like to point out you like especially in the experience manager we can integrate easily with the other solutions like Target and, you know, easy to track that. And and we do, you know as a developer day to day, I face the problems. I think, most of them are rid of the experience Managership, right? And especially when it comes to the reason technologies, like in terms of you know, front end, like React angle. We have a good support from the, you know EAM side like single pay powers, Adobe. So that makes sense.
  • 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.
Like to use the software and then maybe some scenarios where it's not quite good, like not appropriate to host more pages like if you have a huge content, especially when it comes to the managing the assets like images or the other stuff, we have one stop solution, where we can get everything in one place. That is a good thing. I mean where we can go for Adobe products. The negative side, like I don't have anything in my mind like, which I can right now. I couldn't recall anything.
Score 7 out of 10
Vetted Review
Verified User
Incentivized
The main use case scenario is to create a very user-friendly drag and drop interface to build and maintain websites so that a non-technical, non like software focused user, someone that has like a marketing degree can maintain an operating large scale enterprise website with like minimal involvement. so I'm there to build custom components, custom features any kind of like optimizations that, or any sort of like improvements that I get under the hood to kind of improve services so then someone can come in and say, we need a new page, we have new product. And all they need to know is what that new page should look like and what the product should be. And that's all the experience they'll need and everything else should just work. and they can deploy that out to multiple languages, multiple different countries. it can do translation, it can do all that sort of things for you automatically. so you can maintain and operate this giant scale site with a smaller core team of individuals.
  • 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.
A good example actually of is a big business that has multiple sub-brands, like a really large enterprise company that has a lot of sub-brands that are in similar areas. one of the things you can do is you can actually maintain several different websites that all function very differently under the same kind of umbrella and you can even share functionality between those. So if you have similar functionality and your developers are smart enough to think ahead and see the connections, you can really have a system that you don't need to rebuild every site from scratch. You can start kind of building a core that then you share out between all your brands and then if you ha see a bug you fix it in one and it fixes across all of them and things like that. And I feel like the sites that I've seen that have implemented that like large scale multi-site management I think really can leverage that power.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We do have different websites that we are trying to build. And now with the cloud services, I think there's one piece which I definitely don't understand is how do I integrate all these websites with each other, with the workflows that are there. I think workflows are still not a part of the different sites that need orchestration between them. That's one piece. I do understand that they do have a digital asset management. So basically we have different problems in different verticals and I'd like to have the AEM product not as different programs but as one unified piece. And that is I think that is somewhere where we are kind of struggling. How do we have the pieces which are within each of these segments, how do we kind of tie all of them together and not have three different products with three different analytics and three different pieces.
  • 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.
All the website management, it's really good. I think the digital asset management piece of it, I've seen better digital asset management products, so I think that's one area which I probably would want to that's one area of improvement for sure.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
So our main goal is to understand what customers are doing that would lead them to renew with us. We want to learn more about the content that's crucial for them in making that decision to renew.
  • 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.
It's really well suited right now in our CJA use cases that we are running before we essentially get more. So we're running two use cases right now and then hopefully later this year, we'll get more use cases and just a quicker process for it.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
I primarily use it for design purposes. So it's uploading all the different assets, managing the assets that are on the platform itself and just making sure everything is all consistent throughout all the different touch points that we use that we have with our consumer.
  • 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.
From my own personal experience, when we're working on the website and uploading all the different content to there, it's really nice being able to put it all into one area. It's all grouped into its own like folder. You can tag it spec in specific areas and it's so easy for all the different designers to go in and just look through all the different assets that we have there easily.
September 07, 2023

Adobe Experience Manager

Score 9 out of 10
Vetted Review
Verified User
Incentivized
We currently use it to manage all of our property and brand websites. So our company has 70 plus websites and they're all hosted on Adobe Experience Manager. Being able to have so many different websites to differentiate between just being able to have the website structure that we need in there and being able to have users go in and make the edits that they need. It's fairly easy to navigate. So if you know the platform, then it is easy to find what you are looking for. Being able to structure the content is probably, for me, one of the best things about it.
  • 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.
I'm on the web team, that's kind of perfect for the instance of what we use it for, just for maintaining all the property websites and whatnot. I guess first what I would say for us is sometimes just not necessarily everything out of the box works for us, like component-wise. There are cases where we have issues with some of those components and then we'll have to make adjustments or customize in order to get the functionality that we need in that instance. But that's probably, at least from my department, the only issue where I would say is not the best case and we have to make adjustments for it. But otherwise, in regards to managing our websites and to the scale that we have, I think it's great for what we need it for.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We use Adobe Experience Manager to manage our content production delivery to our members. So that's the key purpose of using Adobe AEM. The key problems and issues right now is we are in the process of transforming our legacy website to the AEM platform. So a lot of the design and content needs to be reviewed and tested. We are also developing new, best-in-class components and templates for mobile responsiveness to increase and improve our user experience. So there are a lot of challenges in terms of the skillset and knowledge of using the product.
  • 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.
It's best suited for content creation for mainly the website, and then it actually helps us build a website very quick, without a lot of intervention from our IT department. So that's great. We use this product and work internally with our design team to build the content really quickly. We can build a microsite and build the whole company website on the fly within a very narrow time-to-market schedule. So it's really great to use AEM.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Everyday use, we get web content requests, go to the simple pages, update it. Another one: he announcements that we have, so different segmentations to apply on the segments to filter out the users who can see those spotlights. Upload the images, assets that we have.
What business problems? With the touch UI, it's easier to see things much cleaner, simpler. I guess more like very little things. I would say on the classic UI you can see what's active and what's not, but on the touch UI, you have to go into it and see which one is active, just like little things.
  • 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.
Webpages go up there, edited, put in the workflow, and then approved. Uploading your media assets, referencing them to put it on the webpage itself.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We use a lot of the Adobe stack from our producers, which are our sales drivers. So producers use Marketo. A lot of the design and communications and marketing teams use things from InDesign, After Effects, and Adobe Workfront. We're using all of these things and there's all kinds of assets upon assets upon assets and documents and deliverables. We use it to tame the beast, wrangle all the work in, and corral everything in one place. That makes things super easy too for our designers working within InDesign. We can use AEM to corral pieces, whatever it might be, whether it's contracts or photos or logos, whatever the case may be, whatever kind of asset they need, we can load them up with it. So they have everything they need to actually focus on designing, which is their job. So it makes life easy. It kind of cuts away the distractions and clutter and puts everything in one place.
  • 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.
We'd been using different pieces of Adobe just ad hoc, wherever it was convenient. But in 2019, we really had a discussion of like, what can we do to centralize our work and make it more efficient and work for everybody, whether they're a designer or an admin person or an operations person. What can we do to make our work visible, transparent, and centralized? So this, I keep using the word gold standard, but having everything in one place yes, there are a lot of outputs, but it feels really good having kind of one input area. So there might be a lot of pieces of Adobe that we're using, but because of AEM, it really only feels like we're using like one or two. Just Adobe across the board, like having that one home where things can live so everyone can find it. It might create seven more deliverables, but we did it in one place that enough can't be said about how easy that is and how wonderful that is for efficiency.
Kwazi Henderson | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Within my organization, we heavily utilize AEM as our sole content manager of choice to support our SaaS solution site. We needed a dynamic way to provide an in-depth customer journey for our salesforce products. Our team was focused on the implementation of digital roadmaps within marketing technologies to support revenue and ROMI goals. Our goal is to make our site a lead generation machine, and thanks to AEM we are able publish and display content to our customers swiftly allowing us to go to market at a faster rate. We support multiple business units and subject areas. In regards to AEM's multi-site capabilities, it has granted my team the ability to setup sites and configurations in half the time in comparison to other content management systems used.
  • 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
Based on past experiences with other content management systems, AEM is the apparent choice for enterprise level site management and publishing. I have worked for companies that market a wide range of products and in often in various multi-lingual regions. Adobe experience manager handles both multi-site and multi-lingual translations in such a fast and brilliant way and with such accuracy.
April 04, 2023

My AEM Experience

Score 8 out of 10
Vetted Review
Verified User
Incentivized
To improve authoring/publishing efficiency of content on website.
  • Easy to use once you understand the concept
  • AEM Assets help provide good clear workflow
  • Make website maintenance/update easier
A website with 1000 of contents that need update daily or weekly would be benefit from AEM Sites.
March 24, 2023

Satisfied Customer

Score 9 out of 10
Vetted Review
Verified User
Incentivized
Use it for powering websites for the company
  • 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
Building dynamic sites that can be build very quickly reusing existing components and templates.
Return to navigation