Adobe Experience Manager Reviews

164 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 7.9 out of 101

Do you work for this company?

Overall Rating

Reviewer's Company Size

Last Updated

By Topic

Industry

Department

Experience

Job Type

Role

Reviews (1-25 of 28)

Tolulope Lawal profile photo
Score 8 out of 10
Vetted Review
Verified User
Review Source
My organization uses Adobe Experience Manager (AEM) to manage some of our partner-facing and customer-facing sites. AEM helps us organize and manage the content we show to customers who use our platform, and the content we show to organizations we partner with. On our customer-facing sites, we primarily manage content relating to support and FAQs, and on our partner-facing site, we primarily manage content relating to our product offerings and troubleshooting.
  • Adobe Experience Manager keeps your content separate from your layout which allows for a lot of flexibility in how you display your content.
  • Adobe Experience Manager integrates really well with other Adobe products like Adobe Analytics.
  • Adobe Experience Manager 's drag and drop interface makes it fairly easy to utilize with minimal familiarity.
  • A decent amount of technical knowledge is needed to set up templates for sites.
  • The capabilities of the different kind of users don't align very well with the different roles/job functions at some organizations.
Adobe Experience Manager is great for managing a collection of sites in a manner that ensures all the sites are on-brand (adheres to an organization's image guidelines) and that also ensures that each individual site is not too rigid; the content on each site can still be customized to appeal to the intended audience.
Read Tolulope Lawal's full review
No photo available
Score 7 out of 10
Vetted Review
Verified User
Review Source
We use Adobe Experience Manager primarily in our HQ digital department, but we also have helped implement it to staff and departments in many other countries around the world. We use it to host our main corporate website, as well as our staff intranet site and several other smaller sites. Adobe Experience Manager addresses our organizational need for a powerful, enterprise-level CMS that can handle translations and live copy, experience fragments and dynamic content, integrations with analytics and targeting tools, and many of the cutting-edge Adobe technologies that are included out of the box.
  • Adobe Experience Manager is great for maintaining large websites with lots of content. It has a comprehensive repository and folder structure which makes it easy to organize and break down your website into sections.
  • Although we have not personally used it much yet, Adobe Experience Manager has integrations with the other Adobe Experience Cloud products such as Campaign, Target, and Analytics. The newest version(s) also have integrations with Creative Cloud products like Photoshop, which allows creatives to upload assets directly into the DAM.
  • Adobe Experience Manager has powerful live copy/translation tools that allow you to clone and translate webpages into other languages for alternate language versions of your site.
  • The new Touch UI interface could use a lot of improvement. Many of it is smaller detail items/features, but when using the system extensively it can become cumbersome.
  • There is a bit of a learning curve because of the depth of what Adobe Experience Manager can do. Even basic editing and page creation, while relatively simple at the most basic level, is not as intuitive and easy to use as other systems like WordPress.
  • Development can be complicated. Although I've not personally done much in terms of dev work, my experience and what I've heard from my colleagues indicates that there are some complexities that make it not as easy to develop in as other systems.
  • The source edit option within the rich text editor does not include syntax coloring for the code, or even a different serif/monospaced font. It is the same sans serif font as the regular rich text, which makes it hard to read.
Adobe Experience Manager is well suited for large organizations that need a powerful, comprehensive and robust CMS to manage multiple websites/translations of websites. It is also well suited for those who need a CMS that is well integrated with other systems such as analytics, targeting and email marketing, or those who want some fancy add ons like Adobe smart tags or AI-enhanced capabilities.
It is also an expensive product with a steep learning curve, so it is less appropriate for smaller companies/individuals or those that don't need an overly robust system that is integrated with other digital marketing tools. If you're looking for a more affordable solution that is easy to pick up and play, go with a more basic WordPress or Joomla type option.
Read this authenticated review
No photo available
Score 6 out of 10
Vetted Review
Verified User
Review Source
The nine websites for my company are engineered within Adobe Experience Manager. This is primarily used and managed within our eBusiness department, but is obviously impacted by all our lines of business. Since we operate nine websites that are similar but separate, Adobe Experience Manager is a great solution to maximize efficiency.
  • Adobe Experience Manager allows our company to manage multiple sites simultaneously.
  • Adobe Experience Manager make it easy to share review sites for necessary sign-offs.
  • Adobe Experience Manager is a flexible resource and can always be what you make of it.
  • Searching for and organizing images can be a clunky experience.
  • Standard components frequently do not meet our needs. New components must constantly be in production to run what I usually consider pretty standard functionality.
  • Steep learning curve for people not used to web design or development. Not intuitive at all levels.
Adobe Experience Manager is well suited for businesses with a lot of information or depth, or businesses that must manage multiple websites simultaneously. I picture this being a great tool for insurance companies, financial communities, etc. I do not believe it is well suited to more creative businesses. Despite images of Illustrator of Photoshop that you may conjure when you hear Adobe, Adobe Experience Manager is ill-suited to the kinds of creatives who thrive with those types of programs.
Read this authenticated review
No photo available
Score 7 out of 10
Vetted Review
Verified User
Review Source
We used it to create templates for pitch work. These templates were then used and customized according to the client.
  • You can create robust templates in this CMS and reuse later
  • Managing small or big sites become easier
  • You can use it with Adobe Cloud
  • It has a learning curve, not everything is straightforward even if you are familiar with other CMS's
  • Depending how big your site is, it can become a bit slow
It well suited if you are not a developer but you want to create sites and use their CMS. Having said that, it is a bit complicated for first-time users. It's pretty robust and can perform very well, but it has a learning curve. I would advise taking tutorials.
Read this authenticated review
Vanessa Suarez profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source
One of my clients uses Adobe Experience Manager (AEM) for their site, and as a Web Optimization specialist, I update content on a daily basis for them. AEM allows building and keeping an organized site structure, where you can create new pages in the correct location from the beginning. With AEM, you can have different pre-set page templates but also you can build your own template for specific types of pages i.e Landing pages, product pages, form pages etc... This has to be done by the IT team of your organization, and then, everyone with correct access can use those templates. You can also control the level of accessibility and permission by person, which helps to keep the publishing process clean.
  • It's a drag and drop kind of platform, so building pages is very easy and you don't need coding abilities.
  • The ability to copy existing blocks and section from other pages is excellent! Instead of creating content from scratch, you can actually copy the section you want from an existing page, and paste it in your new page and update the content. This saves a lot of time!
  • The block/brick system is very clean and the results look very good!
  • You can easily embed videos from Youtube only by adding the Youtube ID. Very easy!
  • There is no easy way to change a template if it has been built a certain way. Sometimes it would be nice to have an option to add an extra item on the spot. Instead, you have to ask your IT team to create for you.
  • You can set up a staging site and a site to publish... but sometimes the 2 environments doesn't connect correctly, meaning some changes in the staging sites doesn't show of on the live site.
  • The quick publish button is dangerous and not that helpful: pages can be published with the "quick publish" option even if they are blocked... however, the purpose of a blocked page is to prevent it from publishing until you unblock it. Also, the "quick publish" option will publish your age and every other page connected to it! so be careful!!
If the employees in charge of creating pages are not developers, this is a great platform since everything is easy and drag and drop style. For a developer, this might be more frustrating since small code tweaks are not as accessible.
Read Vanessa Suarez's full review
Meghan Hays profile photo
December 13, 2017

AEM Asset Management

Score 7 out of 10
Vetted Review
Verified User
Review Source
Our marketing team is using it for asset management and also contract vendor management.
  • Easily searchable with the proper meta data
  • Creating links to assets, publishing assets and sharing assets is very easy and fast
  • Uploading files and creating folders is fast and easy
  • Adding meta data to batch files would make it much more efficient
  • You still need to convert any Word or Excel docs to PDFs if this was on auto when you have multiple files, it would also save time
Great for asset management and sharing content. Not ideal for Word docs and Excel format assets.
Read Meghan Hays's full review
Courtney E. Howard profile photo
Score 8 out of 10
Vetted Review
Verified User
Review Source
The editorial department uses Adobe Experience Manager (AEM) daily to post news stories -- articles of varying lengths -- with images, links, etc. Marketing uses AEM, as well, to post marketing information and collateral.
  • Provides instant access from anywhere with a web connection to content.
  • Enables development and use of large image repository that is well organized, promoting easy reuse and accessibility.
  • Accommodates near-real-time edits/changes; changes are reflected almost instantly, as soon as refreshed.
  • Adobe does a decent job of adding features and support, such as for new file formats (added PNG support, when previously only supported GIF and JPG).
  • User interface reminiscent of Microsoft Word, enabling fast customization.
  • Great way to add Cloud capabilities and content management to your workflow.
  • Easy to learn and use; learning curve minor.
  • In all honesty, Adobe Experience Manager is not without its glitches, like anything. Some errors have perplexed our internal IT staff.
  • Likely to require some finessing or customization to work with or port over assets in an existing system.
  • Check that it supports any ancillary, third-party or custom solutions you might already use.
  • Check on hardware requirements, to ensure your infrastructure is sufficient to take full advantage of AEM (web server capacity, speeds, etc.).
It's a great fit for editors and marketing communications staff to quickly update sites from virtually anywhere (with an Internet connection). It's likely useless for sales professionals, and might prove too pricey for start-ups or DIY bloggers compared to other solutions.
Read Courtney E. Howard's full review
No photo available
Score 7 out of 10
Vetted Review
Verified User
Review Source
Adobe Experience Manager is used by the marketing department to build the entire marketing website. It is also used by various others in the development department to build out other web-based products our services run off.
  • AEM is great for customization. Web Dev builds the parts and authors use what they need.
  • Branding can be ensured with the ability to require brand colors, fonts, and styles.
  • It's easy to see who has built, modified, and published pages. It makes tracking changes very convenient.
  • The move to the new interface for authoring is drastically different from the previous interface. Moving has been difficult.
  • Since it is so customizable, a talented web dev team is needed to make all the parts.
  • It is not easy to tell if the page is live or draft in the new interface.
  • Integration with non-Adobe marketing automation tools is very difficult.
Out of the box, AEM is great for building simple websites. For more complex websites such as e-commerce and database integrated websites it requires a lot of customization. Due to this, our team does not use AEM for an e-commerce site we support.
Read this authenticated review
No photo available
Score 7 out of 10
Vetted Review
Verified User
Review Source
Adobe Experience Manager (AEM) is used as part of our digital strategy and refresh of our front facing websites. AEM allows us to leverage the whole Adobe Marketing Suite including analytics and tagging. It also allows for ease of use in terms of interface design.
  • Ease of use for content authors by drag and drop components.
  • Easy to manage users and permissions through grouping.
  • Built in assets management.
  • Cost. AEM is expensive.
  • Touch UI not as intuitive as classic UI.
Well suited to deploy multiple sites with a consistent look and feel with the forms, especially for global companies with multiple authors spread out within different regions. Easy for authors to publish content on a frequent basis. More suited used for large scale deployments due to licensing costs.

Complexity of the system may be a challenge for AEM administrators and developers.
Read this authenticated review
Sujeet Sharma profile photo
Score 7 out of 10
Vetted Review
Verified User
Review Source
I have been associated with various consulting firms and was part of various Adobe experience manager implementations. Here are the details industry wise AEM usage & use case -

Healthcare - My current client is using AEM mainly for content authoring, publishing, multisite management. Integration with analytics, search, test & target. Adobe campaign is being explored, how it can be used with AEM. AEM is replacing current implementation for a few departments that is on Teamsite but fa ew other departments are considering Sitecore as well because they have .Net experts there.

Telecom - Used mainly for authoring and publishing. Didn't use livecopy, workflows except OOTB. Integrated AEM with commerce, search & promote, adobe analytics. Didn't use translation through AEM but it was outsourced to another translation company, they used to translate site on daily basis and host on a different domain.

Banking - Used almost all the features provided by the AEM for example multisite, livecopy, workflows, reports. integration with translation engine, analytics and test & target. It was a content heavy site having big DAM asset collection. Daily jobs used to run to keep all the content and DAM in sync with another system.

  • Easy content authoring by using drag-n-drop components.
  • Strong workflows support. You can quickly implement review-approve workflows. DAM Workflows can create different renditions of uploaded images by default.. For example create thumbnail image, small image, large image, adding text on image.. all these feature are out of the box
  • OOTB Social integration feature. You can quickly integrate with facebook, pinterest and share your content there.
  • Easy to launch multiple site from source site using live copy feature. You can launch child site from parent site with content subset. For example... for different region of same language you want to launch the site with minimal content.
  • Content fragment, Experience fragment making authors life easy..They can create content in advance that can be used on multiple pages.
  • OOTB integration feature provided for Adobe analytics, Adobe target. Obviously, you need separate license for analytics and target
  • OSGi support. Project can be divided into multiple sub-projects and can be deployed/un-deployed without affecting other deployed projects. Using runmodes, you can impose different configurations for different environments.
  • Easy User management and permission control.
  • Adobe provides OOTB caching plug-in for webserver that can be used to clear cache automatically on content change. You can specify the rule what you want to cache or not.
  • Reporting made easy... DAM asset reports, page reports, click reports are available OOTB..
  • Components were introduced to reduce the development & authoring time by reusing them. With some clients, it worked very well because they had page structure and content like that. But if you have UI requirements that can not support component re-usability then your life will be difficult. You will end up creating more and more components in the hope that they will be utilized one day some where on some page... Although you can achieve re-usability by creating smaller customizable component but then again it will increase your development time. In a Nutshell, you will not save development time.
  • Osgi was a great concept. AEM Developer used to write the most of business logic in them but due to adaptation of micro-services, now everybody wants to implement business logic in there instead of AEM internal OSGi. If your architecture had micro services then power of Osgi is useless for you, you will just use 10-20% of it which will bring no big value.
  • License of AEM is super costly, not every organization can afford it. Once you have implemented AEM, it will be hard to get rid of it. Getting rid will mean another investment.
  • Like other products, AEM also releases new versions. Upgrades to new versions never happens smoothly. Means organization needs to spend more money to upgrade the servers.
  • You need a big infrastructure to deploy AEM server setup. Each setup needs at least 3 machines, one for author, one for publisher and one for dispatcher. This means spending more money on maintenance.
  • TouchUI is confusing sometimes for everyone i.e business, authors, developers.
AEM is one of the best CMS available in the market. Adopt it if -
  • You have frequent content change or content creation requirements like new agencies, insurance, mutual fund companies have. For this type of company, its value for money.
  • If you want to maintain multiple sites for different regions.
  • You want to have an easy authoring experience.
  • You are ready to spent a good amount of budget in infrastructure and technical teams.
Note, based on your requirements -
  • You may need separate licenses for -
    • Adobe analytics
    • Adobe Target
    • Adobe Campaign
    • Adobe Cloud DAM
  • Separate infrastructure for -
    • Search Server
Read Sujeet Sharma's full review
Diana Williams profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source
Adobe Experience Manager is being used by the College of Agricultural and Environmental Sciences at the University of Georgia, a separate entity from the central IT system. We currently have over 100 websites on an older editing program that are being migrated to AEM. By the end of the migration, it will be used by about 80% of our college.
  • It is easy for people who are not web designers to achieve an attractive and useful website
  • It is easy to manage users and their permissions
  • It allows users to assemble their digital assets in one place, for use on the web site
  • Upgrading and applying patches can be hit or miss - I recommend backups because of the potential to damage the existing infrastructure
  • Space management is an issue - every change or request takes up space that can be reclaimed, but only through a complicated procedure done through command prompts. There was no documentation for this on their site and we had to use a third party to create the procedure. It has to be run manually.
  • There isn't a good backup system, particularly one that can be scheduled to run reliably.
If you have a number of smaller parts of your organization that you want to maintain the same look & feel as the rest of the organization, it is easy to create a base site and then let them customize. Also, if you have contributors of content who are not involved in the web site maintenance - our professors, for example - they can enter the text on a basic page which is then incorporated through tagging.
Read Diana Williams's full review
Mike Plant profile photo
Score 8 out of 10
Vetted Review
Verified User
Review Source
Adobe Experience Manager (AEM) provides an integrated editing interface. It is a true WYSIWYG experience for the authors with real time visual updates showing the data on dynamic interfaces and really helps our clients see how the page is going to come together without much effort. From a development standpoint separate client libraries from code files allows teams to integrate and work on varying phases of the project without stepping on each others work. Front-end developers can work in unison with back end developers.
  • Media library and asset management is simplified, separating storage and also allowing developers to manage the workflow of the publishing process.
  • No addition of API services are required, using the same requests and data access layer for both front end and back end development simplifies the project lifecycle.
  • Duplicating code is easy, developers can simply copy components and reuse or rework for each use case.
  • Styling the front-end of the author interface can sometimes be challenging. Built in styles and HTML can be overwhelming until you get used to it. Having a less intrusive author output or defining a standard output per site could speed development.
  • Documentation is often outdated, keeping docs up to date and readily available is needed.
  • The local build process is slow and takes a lot of space. Reducing the overhead with local testing would be great!
It is very well suited for large websites and clients with multiple properties where some data is shared. I would not recommend it for smaller websites as the overheard would be too much for small clients and basic websites.
Read Mike Plant's full review
Shishir Srivastava profile photo
Score 8 out of 10
Vetted Review
Verified User
Review Source
I have worked with more than 5 AEM implementations.This includes various industries ranging from publishing, media & entertainment, manufacturing and education. In most of the cases it was a migration from a legacy CMS to AEM. Most of the implementation involves integrating a video system, email system, news system, and feed integration etc. All the sites are non logged in sites and are large websites having more than 1000 pages.
  • Concept of iparsys enabling inheritance
  • MSM support for multi site
  • Digital Asset management
  • Concept of preview
  • Workflow GUI
  • Widget customization is extremely challenging
  • Ability to create Custom Dashboard is missing
  • Portal support is inadequate
Adobe Experience Manager (AEM) is a great tool but you need to be proficient to handle it well. It allows great control over content hierarchy but this is also a source of its biggest issue. Hence it requires expertise to drive the content hierarchy. Unfortunately most of the out of box components cannot be used directly and it requires some sort of development. So development is not as fast paced as expected from a CMS.
It is best suited for large enterprises which have a number of of sites and it requires complex inheritance or language support for Adobe. If you are not planning to buy any other marketing tool from Adobe and do not have a MSM specific requirement it's to better go with another option as cost would be difficult to justify.
Read Shishir Srivastava's full review
Tea Dejanovic profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source
My company guides the implementation of Adobe Experience Manager (AEM) for our clients. We have implemented it in a variety of industries, from healthcare and pharmaceuticals to retail. The business challenge that it helps our client solve is that it alleviates the need for a software developer to be always present at the site for any changes that need to be implemented on the website. Its user friendly interface empowers people with a non-technical background to manage the content themselves.
  • User friendly interface is easy to learn for people that do not have a technical background and it is easy to train employees how to use it.
  • The flexibility of content management. The content hierarchy on the website is easily changeable because it allows the user to move things around at any stage of the content management process, before or after publishing.
  • The structure of the system in templates and components is very logical and easy to explain to the senior management and/or project sponsors.
  • In Touch UI interface the authoring dialogue can not be expanded which prompts the user to scroll when authoring and makes it a cumbersome user experience.
  • Moving the page hierarchy within AEM structure is not intuitive.
  • Re-sizing of the assets often does not work as expected and the user needs to refresh the page before they see the final outcome.
Adobe Experience Manager is a very good match for companies that update their content on a frequent basis and their authors need to have full control over the publishing process. It also works well for large global corporations that have an abundance of distributed authors as it ensures that everyone is following the same guidelines due to the component restrictions that can be imposed.
Read Tea Dejanovic's full review
Nadia Sweeting, MS profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
My company utilizes Adobe Experience Manager (AEM) as a CRM for the company website. All images and content are stored within the DAM within AEM. All changes to individual pages are authored through AEM. Each business unit updates their respective site content or implements new components in an effort to launch new campaigns and site optimization.
  • Ease of image upload
  • Ease of content changes on the spot
  • Workflow systems for production
  • Allow all vested parties to a project to be notified once any changes occur to a page
  • Allow for paid media campaign management
Adobe Experience Manager is well suited for an integrated digital marketing team who works closely with digital agencies and IT.
Read Nadia Sweeting, MS's full review
Curtis Mortensen profile photo
Score 7 out of 10
Vetted Review
Verified User
Review Source
We have an in-house development team that develops custom implementations of Adobe CQ for our clients. It is one of many CMSs our company works with to support our customers.
  • Adobe CQ's biggest strength is allowing marketing departments at our clients to build out their website with minimal tech involvement (once an implementation is in place.) Marketing folks can create pages and arrange pieces on the page to build out a very professional and complex design without requiring a developer to deploy the update.
  • Adobe CQ is built on various open source platforms that make it possible to extend functionality in a lot of complex ways.
  • Adobe CQ also does a good job integrating with many of Adobe's other marketing products, which many clients find useful.
  • I've found that CQ isn't quite as stable as I'd expect an enterprise piece of software to be. There are a few out of the box components that are finnicky/fragile.
  • Supposedly this has been improved in the latest release (6.0), but up until 5.6.1 there were no true coding standards, so business logic could be found scattered all over in scriptlets and servlets. The scriplets would be part JSTL/Expression Language, part scriplet code. This is kind of a nitpick, but as a developer it definitely has an impact.
Adobe CQ is definitely for enterprise applications only. Even were the cost of licensing to be reduced, in many ways, it's overkill for smaller deployments. I've also found it to be inadequate for any eCommerce applications (and I think Adobe would agree with this in their sales literature.) That said, it's fantastic for a large corporation with a big marketing department managing large amounts of content.
Read Curtis Mortensen's full review
Vagner Polund profile photo
Score 8 out of 10
Vetted Review
Verified User
Review Source
Since I work at a agency named Axis41 I have worked extensively with the product. It was formally known as CQ but has since been rebranded as AEM. Initially CQ started as a enterprise level CMS (Content Management System). Since then Adobe has integrated many different solutions into AEM. It excels at managing web content for large scale enterprise websites. It has many web content management facets as well such as: Personalization, Digital Asset Management, Analytics, and many other solutions on the way.
  • Manages web content with an intuitive WYSIWYG authoring experience.
  • Manages Digital Assets used by your website such as images, audio, documents, etc.
  • Creates an simple easy to use experience to generate web content. Centers all web content generation around the author.
  • A lot of the OOB (Out Of the Box) components are still a little buggy and not fully ready to go without some minor tweaks.
  • Since the software was acquired not too long ago by Adobe, a lot of Adobe integrated solutions are not fully baked yet. That is getting better with time.
Adobe is an enterprise level software that is best suited for large amounts of web content. The entire web management experience is engineered around the author. It is a large solution with many capabilities readily available to you out of the box.
Read Vagner Polund's full review
Terry Peters profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source
I am designing the implementation of an experience manager at a client for use as an international business management tool. We have implemented the tool as a multiligual, multinational solution that is used by over 10,000 concurrent users with more to come in the coming months. We have designed a custom front end and use the authoring environment to manage the content. The application is integrated with many backend systems through restful web services to provide real-time data to end users of the web application. The solution has been heralded as a game changer for people in this particular industry.
  • Flexible
  • Powerful
  • Adaptable
  • None
Read Terry Peters's full review
Ali Alkhafaji profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
My organization focuses on implementing and customizing CMS tools like Adobe CQ for our clients and partners.
  • Scalable, testable and extensible architecture
  • A large feature set out of the box
  • Intuitive Interface and modulization
  • Adobe CQ could do a better job at providing more intuitive user and developer documentation
Adobe CQ is highly suitable for content centric web applications based on a Java stack.
Read Ali Alkhafaji's full review
Fernando Galeano profile photo
Score 8 out of 10
Vetted Review
Verified User
Review Source
We are using Adobe CQ in the Merchandising department. It allows those teams to author and launch landing pages for the different sales and seasonal events we run on a regular basis. It helps them be independent of our technical teams for releasing and authoring all the pages they need, at the speed they need. At the same time, our technical team can provide customized templates, components and publishing workflows within certain boundaries that help us keep our design and development standards in check. All this while authors can publish new content any time they need without having to go through the rigorous release and deployment processes.

Our previous CMS solution was dated and it was costly for the organization to keep up with the pace of the Merchandising and Marketing teams. We were forced to plan too far in advance to give development teams time to put together new landing pages and it didn't allow for quick turn arounds like CQ does.
  • Allows non-technical staff to author and publish content by focusing on the content itself and the needs of a given campaign instead of technical implementations.
  • Content workflows allow varying degrees of complexity for content review and quality assurance before providing approvals on any piece before going live.
  • Development teams can build very robust and complex component for handling virtually all posible needs: from integrating back-end web services to UI Widgets for content authoring; from multisite suites to multi-language components, CQ can handle it all thanks to the power of Java and the flexibility of Sling and JCR.
  • Easy to scale for high-traffic sites and thanks to the Publisher/Dispatcher infrastructure, very flexible for caching and load balancing.
  • Steep learning curve for both Authors and Developers when it comes to customized components and workflows.
  • Development community is small and somewhat closed. It keeps growing with the years as CQ becomes more popular, which is a good thing.
  • Expensive, both to purchase, train and certify. This makes it harder to learn unless companies are willing to spend thousands on official training.
CQ is best suited for multi-site projects that require frequent updates or new pages spun up very quickly and with the same quality as the rest of your site. It's also a great fit if you have extensive media libraries: pictures, videos, etc. The Digital Asset Manager is very powerful and if it's coupled with a CDN, it can be itself a great solution for that particular purpose alone.

Key questions to ask would be:

- How comfortable will our authors be with this publishing platform? What are their needs and wants? Can CQ accommodate them?
- How skilled is our development team to take a project like CQ? The best of CQ comes when is customized but it will come with a price. Time and talent will be necessary to tweak it to the right fit.
- Do we have enough time and resources to allow our technical and non-technical stuff to learn? Can we afford all the oficial training levels?
Read Fernando Galeano's full review
Cassie Lyn Dusute profile photo
Score 8 out of 10
Vetted Review
Verified User
Review Source
The company I previously worked for used Adobe CQ as a CMS for the main company website along with multiple microsites. The site as a whole included well over 400 pages. The website was created with a customized version of Bootstrap 2.0, and integrated with CQ modules. Our job was to make sure that the modules worked with the designs, and fix any problems that arose.
  • Customization. Although this is important for any CMS to allow, CQ does a pretty good job at allowing for customization.
  • Easy to use. Adobe CQ requires a little bit of up-front work to get you started, but after you start, it's easy to continue.
  • Versioning. A huge plus when you're constantly changing pages. The versioning available is amazing and super helpful
  • Migration. We had multiple environments that we were constantly moving content back and forth on. Moving the content over through CQ was a bit of a challenge.
  • Integration. In some instances, Adobe CQ's built in modules would fight with custom modules. Usually the problems went away on their own.
  • Forms. Sometimes when adding a form to the page, the TO and CC sections would show up as empty when they had email addresses. Then when you went to change them, you couldn't close the settings window without clicking cancel.
Do you expect to have a lot of pages with similar templates? I would suggest Adobe CQ for this kind of website. You can create templates so that the look and feel throughout the site is consistent.

Are you planning on a smaller site with few pages? Then Adobe CQ may not be for you. The cost of the product alone is a sign that this should be used for businesses with a lot of information to share.
Read Cassie Lyn Dusute's full review
No photo available
Score 5 out of 10
Vetted Review
Verified User
Review Source
Adobe Experience Manager (AEM) is being used mainly by two departments (marketing and support) but is also being slowly adopted by other departments, depending on their use cases. AEM allows us to manage all sites on a single platform, increasing efficiency, reducing QA time and complexities, and requiring less training. We can more quickly deliver targeted digital experiences to our customers and visitors, and all campaigns can be managed and launched from a central location.
  • One central location to manage all sites.
  • All assets can be easily accessed, managed, and published from one central location.
  • Easy for authors to create and publish content.
  • User interface can be buggy at times.
  • The touch interface can be confusing and/or unintuitive.
  • Cost. AEM by itself is good, but needs some additional services (Analytics, Target) to really make it more effective.
AEM is suited for enterprise-level businesses to easily author, publish, and manage websites. There are many powerful features that allow businesses to author, publish, develop, implement workflows, manage assets, launch marketing campaigns, and integrate an e-commerce platform, all in a central location.

AEM is less suited for small to medium sized businesses simply because of the cost and initial setup time. Out of the box, it isn't very useful and will need to be heavily customized to the business's needs. It also requires users who already have AEM experience or they will need to be trained.
Read this authenticated review
No photo available
Score 9 out of 10
Vetted Review
Verified User
Review Source
My company implements Adobe Experience Manager solutions on behalf of others.
  • Give content editors an easy and intuitive interface to manage content. For example the WCM allows users to create and edit pages. The page editor allows the users to navigate the DAM and drag/drop images onto the page. Once done editing, they can submit the page into a workflow for manager review.
  • Give managers the tools to establish an editorial workflow to better control what is published. Managers can create custom workflows, often with out of the box components (there is a workflow editor) to allow them to control the review and publishing of content.
  • Based on Open Source so it is easier for developers to work with. There are at least 2 major OSS libraries out there, ACS Commons and WCM.IO.
  • Out of the box integrations with many other systems, especially the Adobe Marketing Cloud.
  • It is hard to find people with the skill to develop solutions on AEM.
  • The TouchUI pales in comparison to the features found in the Classic UI. Developers have a hard time implementing solutions in the new Touch UI because the framework is lacking, where as in the Classic UI the framework is more robust. For example there are some out of the box classic UI widgets that allow developers to create key/value pair lists in dialogs. In touch ui that does not exists and developers are forced to implement custom solutions.
  • It is based on open source, so a lot of the code base is out there (except the proprietary AEM stuff, i.e. WCM). This means that between versions of AEM, there are major changes (they are good at backward compatibility however). This could be a good thing, but may be a bad thing if your company is more sensitive to big changes that come hard and fast. There are people out there developing on AEM 6.2, as if it were still AEM 5.6. They don't even know how to take advantage of the new features.
It is well suited to put out traditional and informational intra/extranets where content editors create articles/posts; could even allow external users to contribute content, deliver your site to many channels. For example, aside from the traditional desktop site, there are AEM Publications and Mobile Apps.

It's not meant to be used as a CRM, it is supposed to integrate with one. It's not meant to be used as some management system. For example in previous experience, a customer was using it to manage requests (i.e. a JIRA type of thing).
Read this authenticated review
No photo available
Score 6 out of 10
Vetted Review
Verified User
Review Source
[My organization] implements for other clients.
  • Easy for authors to use
  • A lot of functionality available to use
  • Scalable
  • Can be very difficult to develop for
  • Adobe takes a very long time to fix bugs, sometimes not fixing them at all
  • Lack of any consistent documentation
Adobe Experience Manager is a good piece of software once the specific and individual pieces have been developed. It is easy for authors to publish information and construct pages and sites, but only when the tools are already built. For the developer, it can be difficult developing in AEM due to the various bugs and extremely poor official documentation, or documentation in general.
Read this authenticated review
No photo available
Score 8 out of 10
Vetted Review
Verified User
Review Source
Using Adobe Experience Manager, we design and integrate web and mobile properties to help our customers engage and inform the rest of the world along with their individual customers the correct message they want to communicate. We would also help them set up a web content management system through which new content can be produced and released to the public without the need of IT involvement thereby bridging the gap between marketing and technology.
  • Ease of use and highly customizable
  • Lots of feature integration with other marketing and analytics tools
  • A lot of default options, which when used correctly reduce the need for custom development
  • Designer friendly as it integrates well with several other design and creative tools from Adobe
  • Commerce platform integrations are really hard
  • Developer documentation is not up to the mark
  • Certain issues are very hard to detect and there is little log information
  • Rapidly changing features are compromising the stability of the system
Usage of AEM requires certain training on the marketer's side, the general recommendation depends on how frequently the information on web properties get updated. It is highly useful if there is a constant change in the content. Alternatively, it can also be used as a content delivery system which is in turn hooked to a third party system.

If an organization has predominantly static content and relies on IT to carry out the updates, then AEM is a very expensive option and there are better WCMS alternatives.
Read this authenticated review

Feature Scorecard Summary

Role-based user permissions (23)
8.6
API (17)
7.3
Internationalization / multi-language (18)
8.1
WYSIWYG editor (20)
7.5
Code quality / cleanliness (20)
7.1
Admin section (20)
7.6
Page templates (22)
7.0
Library of website themes (15)
5.2
Mobile optimization / responsive design (21)
6.6
Publishing workflow (21)
7.3
Form generator (17)
6.7
Content taxonomy (18)
7.1
SEO support (20)
6.1
Bulk management (22)
6.4
Availability / breadth of extensions (20)
5.2
Community / comment management (18)
5.3

About Adobe Experience Manager

Adobe Experience Manager is a content management system from Adobe designed to help businesses manage their marketing and web presence, and track customer data to optimize the visitor experience and conversion. It allows businesses to create customer profiles for site visitors using both authenticated and anonymous data, dynamic tag management, mobile services and accessibility, and connection with third-party data and applications via the Adobe Marketing Cloud Exchange. It features multi-site management with regionalization and localization and editing, templates to ensure consistency across sites, and pre-built integration with other Adobe tools and services. Marketing campaigns and assets are centrally managed, and out-of-the-box integration with Adobe Analytics, Target, and Adobe Campaign help expand features. E-commerce systems can be integrated and product information can be synchronized, allowing Experience Manager's analytic features to test and improve the online shopping experience. Pricing varies considerably as implementation needs will vary.

Adobe Experience Manager Competitors

Adobe Experience Manager Technical Details

Operating Systems: Unspecified
Mobile Application:No