Item: Adobe Experience Manager
Rating: 10
Author: Verified User

Use Cases and Deployment Scope

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.

Pros and Cons

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.

Return on Investment

We're still refining it in the sense that we need to understand more about what other optimizations we can do with it. Once we are done with the optimization, we will be in discussions with the technical support team from the AEM side and understand areas of improvement and definitely the ROI matters for any product implementation or purchase. So I believe we'll get a good return on investment from the Adobe world.

Usability

There are some areas on the admin side, administration overall view especially for the tags I believe, I can't pinpoint at this time. Maybe a year back I felt the problem but it got solved. But I can't pinpoint at this time.

Favorite Features

We are using all of them. We are using DAM for the image, like asset management which will help us generate these images for the whole form factors and sites. We are trying to bring other sub domains into other sites that we own which are still running on the other CMS platform. We would like to slowly migrate to AEM. And so far the experience was good.

Alternatives Considered

We are part of OpenText and because of so many acquisitions and all, there is no much development in that. Considering that AEM is the leading CMS platform, it helps us with other problems like asset management or creation or target integrations. It helps us be faster and it's good for the overall ecosystem.

Key Insights

Do you think Adobe Experience Manager delivers good value for the price?

Not sure

Are you happy with Adobe Experience Manager's feature set?

Yes

Did Adobe Experience Manager live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Adobe Experience Manager go as expected?

Yes

Would you buy Adobe Experience Manager again?

Yes

Likelihood to Recommend

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.

Adobe Experience Manager Review

Overall Satisfaction with Adobe Experience Manager