Adobe Experience Manager manages most of our websites, and content management is conducted exclusively through the AEM platform. Whenever we need to publish a new page, blog, or podcast, we access Adobe Experience Manager to make the necessary changes in the components, retrieve assets from the DAM, and publish the required pages.

Adobe Experience Manager serves as our primary platform for day-to-day operations because we have been using it for an extended period. We build websites, develop components, and create custom and core components for new web pages. We continuously update these components to ensure compliance with AEM guidelines and to verify that our website is accessible and passes all required tests.

Adobe Experience Manager is user-friendly for our team because we have robust content authoring in the components, allowing authors to build pages from reusable components and use already-available templates to manage content without development assistance, as those components are prebuilt. We also have Digital Asset Management where we can retrieve assets after uploading the necessary details, and it maintains a central library of all images, videos, and documents. It is straightforward to access all data at once, and there is a strong content workflow model with approvals, so without proper permissions, users cannot perform any actions. Content reuse and consistency are key factors, and it provides enterprise governance and security for each user role, with granular permissions and SSO support, ensuring compliance-friendly controls.

Adobe Experience Manager offers several best features, including user-friendliness and a more secure platform than any other content management systems I have worked with. It has proven to be an excellent tool not just for developers and technical roles, but also for non-technical roles such as project managers and account managers, making it a solid platform for management.

Adobe Experience Manager has positively impacted our organization by serving as an excellent tool for building websites. We have migrated most of our sites from different content management platforms such as WordPress, Squarespace, and Craft to Adobe Experience Manager because we appreciate the content modeling and the ability to reuse templates for pages. It has been a wonderful tool for us.

Adobe Experience Manager could be improved by making it more reliable for all developers to access, rather than restricting access to a certified pool of resources or developers.

We also have another project running on Adobe Experience Manager where the Adobe support team indicated that integrating Live Search into our current e-commerce platform presented challenges. Adobe Live Search does not support the customizations we have on the live site and only supports the basic version. Therefore, I recommend that Adobe improve customizations and support customer-focused values for Live Search integrations, which would greatly benefit our team.

I assigned a rating of eight because there are certain limitations we must consider, and there are restrictions in Adobe Experience Manager that we cannot resolve. The primary concern is cost; the cost for AEM developers is significantly higher than that for standard developers, and AEM certified developers are substantially more expensive than regular developers.

I have been using Adobe Experience Manager since 2023.

We are a partner and have dedicated Adobe Experience Manager support for the products we currently use.

Adobe Experience Manager is an excellent platform for large enterprise development websites. We currently support a multinational company using this platform.

When we use reusable components for building new pages or landing sites, it has definitely reduced the time required to redo any tasks. Since we are reusing existing page components and available themes, it is simpler for us than performing the work manually.

For others seeking a robust and secure platform with comprehensive details who are running most of their campaigns and digital ads on Adobe, Adobe Experience Manager is an excellent platform to consolidate cross-channel data and bring everything together in one place. However, if they already have a digital meta intelligence or similar setup for their cross-channel platforms, they may not find Adobe Experience Manager suitable, as it is a robust platform where everything can be visible together simultaneously.

I provided a rating of eight for Adobe Experience Manager based on the considerations and restrictions discussed throughout this review.

Adobe Experience Manager is used for developing components, content management, and developing experience fragments and content fragments. Assets are used for the DAM for storing files and documents. All of this is used in day-to-day development.

When there is a similar requirement while changing the content of any component, a single component can be developed and reused, achieving the same requirement in a few minutes. With plain development, the whole page would need to be authored twice a day or have the whole content repeatedly. Adobe Experience Manager allows for developing a component, having reusability, and achieving this in a shorter time.

The main use of Adobe Experience Manager is for reusability and content management. This is the main theme of Adobe Experience Manager.

For targeting within Adobe Experience Manager, if particular users specific to the product base or any type of targeting is needed, Adobe Target can be integrated. Day-to-day targeting allows for reaching exact unique users, sending those product details, and achieving targeting accordingly.

Adobe Experience Manager has automated many things positively in the organization. Previously, the whole application was developed from scratch with all template creations and rendering script creations. When Adobe Experience Manager was introduced, only one component and one template were developed and reused in many pages and many use cases. Over the past two to three years, the organization has grown rapidly with Adobe Experience Manager as a best and supportive tool.

The drastic changes with Adobe Experience Manager are reflected in the numbers. Previously, the whole project was developed in five to six months. When Adobe Experience Manager was implemented, the whole project was developed in weeks, specifically four working weeks or twenty days. The development time has been reduced from five to six months to twenty days, showing a drastic change.

Adobe offers many tools for marketing and targeting. Commerce and other tools have been explored. As a well-developed tool, Adobe Experience Manager has provided extensive experience.

Moving forward, if Adobe implements AI tools wherein a vendor or a stakeholder comes in and gives instructions, they could develop a page or a whole site accordingly in a few minutes or a few days, which would be more helpful with AI.

Adobe Experience Manager has been used for the past four years.

Adobe Experience Manager is a stable tool. There are no bugs or issues within Adobe Experience Manager. It is very smooth, and upgrading to Adobe 6.5 LTS is also a very good and smooth experience compared to different tools.

Adobe Experience Manager can handle numerous projects because more projects can be developed, enhanced, and numerous components can be reused in many projects and published. It is more durable and scalable with this capability.

The Adobe Experience Manager support team is very friendly and responds very quickly. Previous tickets raised with Adobe customer support received quick responses, with all supported documents and links provided to resolve the issues. The customer service rating is five out of five.

Adobe Experience Manager is an upgrade from CQ5, which was previously used. According to training sessions, CQ5 was the previous solution before it was upgraded to Adobe Experience Manager.

The pricing and setup cost for Adobe Experience Manager is a bit higher compared to different content management tools. When compared to CQ5, Adobe Experience Manager costs a little more. However, it should be considered because there are additional features with more add-ons instead of the basic Adobe Experience Manager.

Moving forward, every organization needs to have Adobe Experience Manager license wherein the work can be done in a shorter period of time and achieve a lot of things with this tool. It is advised to have up-to-date information on Adobe because there are many updates available that can achieve more while developing and enhancing sites. Keeping up-to-date with Adobe's official sites is necessary. This review has a rating of five out of five.

Adobe Experience Manager is my main headless CMS that helps with creating, managing, and publishing websites and landing pages in my organization.

A specific example of how I use Adobe Experience Manager for websites and landing pages is that it enables our marketers to update content without coding.

Adobe Experience Manager has positively impacted my organization by allowing us to reduce time to market and enhance personalization, which leads to higher conversion.

Through faster content creation and publishing, this improved our campaign launches. Personalized experiences boost engagement and revenue in my organization.

The best features Adobe Experience Manager offers are website and content management, digital asset management, and personalization and experience delivery.

The personalization and experience delivery features have helped my organization by enabling us to deliver personalized content across channels such as web, mobile, and applications.

Adobe Experience Manager increases operational efficiency through centralized assets and reduces time spent searching, editing, and managing files.

I also value the integration with Adobe Target and Adobe Analytics, which makes analysis of our markets very easy so that we can make data-driven decisions.

Adobe Experience Manager could be improved in that the cost is higher than expected.

Besides the cost, the complex setup is another area that could be improved with Adobe Experience Manager.

I have been using Adobe Experience Manager for three years.

Adobe Experience Manager is very stable.

Adobe Experience Manager's scalability is excellent, as it reduces infrastructure and maintenance costs.

The customer support is great, and everything has been good so far.

I previously used Mailchimp as a different solution.

I switched from Mailchimp to Adobe Experience Manager because Adobe is a great platform.

The licensing plus implementation and maintenance cost is very expensive, making it not suitable for small organizations, and the setup is very complex.

I have seen a return on investment through reduction in time to market, automation through AI, and the availability of very scalable solutions.

Before choosing Adobe Experience Manager, we did not evaluate other options.

Adobe Experience Manager is one of the best enterprise-level content management and digital experience platforms available. My advice to others looking into using Adobe Experience Manager is that this platform will enable all marketers to improve their marketing strategies globally. I rate Adobe Experience Manager a nine out of ten.

My main use case for Adobe Experience Manager is to share papers with colleagues and to edit PDF files.

I use Adobe Experience Manager to share or edit documents with my colleagues because we work with lawyers and have to create documents, modify these documents, and assemble papers.

I use Adobe Experience Manager because it is the official app of our working environment, so I need to use it.

The best features Adobe Experience Manager offers are the capability to modify a document in all of its aspects.

When I say I can modify a document in all its aspects, I mean that signing a document with Adobe is very simple, and certifying the document is also straightforward since we work for the public administration.

Adobe Experience Manager has made document management smoother because many people use Adobe, making it simpler for me to modify and resend PDF documents.

Since I started using Adobe Experience Manager, I have noticed fewer errors.

I think Adobe Experience Manager can be improved by making it simpler to use.

I do not have anything specific in mind regarding needed improvements.

I chose seven because if the app were simpler, I could give a nine or a ten.

Adobe Experience Manager is not so simple to use, so others should have some experience with similar programs.

I have been working in my current field for almost six years.

Adobe Experience Manager is stable in my experience.

I have never needed to reach out for help with customer support.

I have not used a different solution before Adobe Experience Manager.

Adobe Experience Manager is deployed in my organization simply based on my boss telling us to use it.

I do not know if my company has a business relationship with this vendor other than being a customer.

I have not seen a return on investment because I am a simple employee and do not have a return.

I do not have much experience with pricing, setup cost, and licensing.

Before choosing Adobe Experience Manager, I did not evaluate other options.

I do not have much experience with pricing, setup cost, and licensing.

I have been working in my current field for almost six years.

I find this interview too long and it should be shorter to make it more brief.

I gave Adobe Experience Manager a rating of seven out of ten.

Adobe Experience Manager is being used for website development and app PWA developments. It is also used in multiple other use cases related to creating internal web solutions and SaaS-based platforms.

DAM, Digital Asset Management, is used in hosting the entire asset collection including images, videos, and everything else. We also have a customized DAM where we upload all internal DBs related to inventories and other items. A few catalog systems are integrated, and the SKUs are typically dumped through the DAM.

Adobe Experience Manager itself is a content management system. Once you develop components, it becomes easy to change any content-related items frequently. It's very efficient in terms of getting changes done. You don't need deployment, and code changes are not required all the time.

The best feature is the experience fragment. If you want to replicate content across multiple websites with 1,000 or 20,000 pages, this feature helps accomplish it in a fraction of seconds. Additionally, there are schedulers and custom-made publishers which are handled through the system, and it's easy to integrate with multiple cloud-based platforms such as Akamai.

Regarding the component-based framework and content delivery across different platforms, we make a standard framework. Our design team members create a component library. We maintain the library as a storybook and keep it accessible to prevent creating multiple versions of the same component. We focus on reusability to save costs. If a component costs around 6 to 8 lakhs, we reduce it to approximately five, which can be replicated across multiple pages for cost savings.

Akamai has been implemented so we cannot hit the server directly. The website and pages are cached through Akamai. It hits the cache server first and serves through the cache server. When changes occur, the cache gets flushed, then replicates, and the customer receives the final copy of the page.

Adobe Experience Manager needs more optimization. The frequency of components where we have vitals of a page or an app needs to be optimized because these are heavy Java codes along with some AEM developments. The code language should be optimized or they should have some string functions or web plugins to create a lighter version rather than implementing large amounts of code lines. They should start implementing industry best practices which are not currently offered.

We perform our internal development for customization at our own pace. We have multiple frameworks that help us in various ways. We are advancing in terms of AI integration. We have already started our own POCs before Adobe implements these features.

I have been working in my current field for 12 years.

The response has been very quick. The resolution time depends on the type of ticket raised. For P1 tickets, the resolution time is approximately four hours. For P2 or P3 tickets, it takes around 8 to 10 hours TAT. The response time is quick, and they provide resolutions. If they don't have an immediate solution, they coordinate with other team members.

I have experience with Drupal and Magento, where the catalog system was used by Amazon, though they don't use it anymore. Magento is used by Flipkart and eBay. I also have experience with other custom-based solutions.

Drupal is a completely different company. While they also provide a content management system, Adobe Experience Manager is more premium, flexible, feature-oriented, and offers different templatization options where custom solutions can be built easily. Drupal has restrictions and requires a longer development process. Drupal developers are not easily available in the market. With Adobe Experience Manager, you can transition from a Java developer to an AEM developer, making resource allocation easier.

The setup process is quite flexible, with complete support from Adobe. Setting up is straightforward, and while cost effectiveness might be lacking, finding developers and implementing custom solutions is easy. You can build whatever you want across Adobe Experience Manager due to its flexibility.

The price is significantly high. It's a solution for enterprise organizations, not for small-medium organizations. Companies that are scalable and can maintain it for a longer period should consider it. These technology decisions require careful consideration because the cost can be significant. The enterprise solution is the best practice for an integrated market for Adobe Experience Manager to integrate and penetrate.

It is not cost-effective and can be expensive to implement.

I have been working with Adobe Experience Manager and other technologies including SaaS-based developments, apps, and web within the last 12 months.

Adobe Experience Manager is primarily customized development, which we handle internally, occasionally seeking Adobe's assistance for specific products or solutions used for IAM development purposes.

We run sanity suits daily across multiple platforms seeking segmentation, using custom tools and harvesting for testing purposes.

We implement content strategy through our internal portal. We have a matrix portal providing complete updates and a dashboard for tracking. We monitor the number of URLs being published, workflow progress, dispatcher status, and issue resolution frameworks. A monitoring framework has been implemented to oversee these aspects.

I rate Adobe Experience Manager a nine out of ten.

I am on the Digital Asset Management team and we coordinate projects through Workfront, tracking assets through Workfront and with Adobe Experience Manager.

My use cases involve migration within Digital Asset Management teams. At a healthcare company, the Digital Asset Management team retail, within marketing and an insurance company that was acquired by the company, their digital asset management team within the insurance company coordinated with us as they were also using Adobe Experience Manager. There was a migration of assets from their system to our DAM system. We had about a thousand customers, most of those internal creatives, but some of those are external vendors and photo studios. Vendors would submit assets in the inbox within Adobe Experience Manager, and then I would approve and publish, work on folder structure, naming conventions, metadata, and metadata fields and forms.

The search capability in Adobe Experience Manager is superior, as search capabilities are determined by the metadata. Adobe Experience Manager is the tool for metadata, and it also has metadata automation using AI.

There are some issues with AI in assigning metadata, for example, for stock photos. After some of the AI metadata is assigned, we have to go through and double check to make sure that the AI metadata is correct because sometimes it was not accurate.

The benefits I see from using Adobe Experience Manager are that it's an alternative for a digital asset management system. Adobe Experience Manager tends to be the standard, one of the major options for a DAM tool, and in that way, it's beneficial because it's a mainstream product in the industry.

Improvements could be made, though it's difficult to pinpoint because Adobe Experience Manager has been part of my world for the past several years. Many people complain about the price as it's one of the most expensive tools.

I think it might be worth the money for large companies, and I think large companies are going in that direction, but for smaller companies, it would probably not be worth the money.

I have been using Workfront for about a year.

Regarding stability, there are sometimes bugs, and currently at a beauty products corporation, it seems to be better in general.

The scalability of Adobe Experience Manager is pretty good because we have so many engineers that are knowledgeable about and have experience in altering the Adobe Experience Manager system.

My company has a partnership with Adobe. There are Adobe engineers, sales representatives, and engineers assigned to Sephora North America.

It's been years since I used a different solution. When I worked with a manufacturer, I used Extensis.

My company has a partnership with Adobe with engineers and sales representatives assigned to a beauty products corporation.

I would recommend it to large companies with a big budget, and I would recommend it to digital asset managers with experience in Adobe Experience Manager because it would be good for their career.

On a scale of one to ten, I would rate Adobe Experience Manager an eight.

I've worked with all major content management systems. Currently, I work with the leaders such as Adobe Experience Manager, Sitecore, and Acquia.

Working with big companies, I help them either consider setting up a new content management system or address issues they might have with their existing systems. My role involves evaluating the decision for a new CMS and ensuring successful implementation.

The integration of customer behavior and website setup is impressive. It's similar to a heat map used on the fly.

While there are many aspects that could be improved, discussing them would require more time. The licensing model is opaque, and technical support could be improved, especially for smaller companies.

For the last 25 years as Adobe Experience Manager has evolved through various iterations.

Adobe Experience Manager provides assurance that the system will work within five to ten years, ensuring stability for big companies.

Adobe's technical support is so-so. They are attentive to big companies but tend to be negligent towards mid-sized companies. You rarely have a direct contact with Adobe and often work through suppliers.

Setting up Adobe Experience Manager is easy unless you want to customize anything. The setup process can become problematic if you try to change or customize extensively.

The key is the implementation team, which often involves technical suppliers.

The pricing is opaque and not a key factor when considering the dimensions of the solution. For large enterprises, the cost is often comparable with other major CMSs.

ContentSquare, Sitecore, Storyblok, and Typos3 are alternatives that I am aware of.

For any investment, it's important to understand what you want to do and what your targets are. The system should fit into your IT environment and also align with your business strategy. This makes your implementation smoother and more successful.

I'd rate the solution eight out of ten.

I am a full stack developer, focusing more on the front end. I work with frameworks like React and JavaScript. I would like to give a review about Adobe Experience Manager, which I have used for managing content for large-scale applications.

Since using Adobe Experience Manager, we have been able to manage content without dumping everything into the code. It allows business people to modify values directly without waiting for deployment times. Additionally, the use of Adobe Experience Manager has helped manage traffic more efficiently through effective scaling and balancing loads.

The most valuable features of Adobe Experience Manager include its capability to manage content and create reusable fragments. It is user-friendly for business people who may not have extensive technical knowledge. The Asset Manager is particularly useful as it allows multiple developers to reuse images without bloating local code size.

Adobe Experience Manager could improve by allowing the reuse of components like a progress bar across multiple pages to make the development process more efficient. Currently, changes have to be made on all the pages manually, which is time-consuming.

I have been using Adobe Experience Manager for about one year. Although I am relatively new to it, I find it highly beneficial for content management.

Adobe Experience Manager is fairly stable yet could benefit from enhancements, especially in component reuse.

Adobe Experience Manager is highly scalable but has some difficulties. Despite these, it reduces the number of servers needed by efficiently managing web content.

I have not personally interacted with customer service or raised any tickets. Our Adobe Experience Manager team handles such situations.

Before using Adobe Experience Manager, I worked with libraries to manage content but did not use another content management system specifically.

Setting up Adobe Experience Manager is complex and requires a good understanding of Java and content management systems. The setup is especially challenging for those unfamiliar with it.

Deployment requires three people: the developer who made the changes, an Adobe Experience Manager assistant, and a business person to monitor the deployment. Maintenance requires at least ten Adobe Experience Manager experts for large applications.

Adobe Experience Manager has provided significant returns on investment, especially in applications with large numbers of users. Its ability to change content without deployments is beneficial.

Adobe Experience Manager is quite expensive and requires careful management of cashing and usage. It is described as high-cost but value-adding.

The platform team chose Adobe Experience Manager due to its trusted reputation and additional advantages over simpler systems like WordPress.

For web applications with frequently changing content where business people need to make modifications without technical knowledge, Adobe Experience Manager offers significant advantages.

I'd rate the solution nine out of ten.