What is your primary use case for Adobe Experience Manager?

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.

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.

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.

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.

We are working on digital experience platforms such as Adobe Experience Manager or Sitefinity. It's for powering their customer-facing website, not the transaction portal, but the brochureware portal. Currently, we have around three customers who are using Adobe Experience Manager.

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

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.

We use the solution for e-commerce. For the e-commerce part, we have three types of channels: mobile, web, and tools, both B2B and B2C.

I have been using it for CDP, real-time data, CJA, and CJAO (Customer Journey Optimization). My current organization is a product-based company. We have multiple products with a wide user base, both B2B and B2C. We have to track their data, including digital and offline data. We have sales and marketing teams who use different sources. We need to club the data through our CDP and give it to the marketing team to utilize for marketing efforts. We have a separate team that requires cold calling details, small communications, and push notifications. All these things are required for CJA to optimize our campaigns. Before, we were using Eloqua, Salesforce, Adobe, AWS, and many other data sources. It was difficult for stakeholders to make decisions because they had to consult multiple dashboards (marketing, campaign, etc.). They had to create slides and then make decisions. Now, with Adobe Experience Manager (AEM), we have all the data sources in one place and can visualize them together. We can make quick decisions, and we started using this in 2024.

It's a powerful content management system – there's really no competitor in the market right now. The main use case is digital marketing. For example, if you have offers you want to publish immediately, and you want extended functionality like Adobe Target and Adobe Analytics on top of those offers, Adobe Experience Manager (AEM) is perfect. You can publish something in minutes. Adobe has other tools like Analytics, Target, Scene7, and now Centra (which is based on artificial intelligence). Integrating these products with your CMS gives you powerful digital marketing and customer journey analytics.

Adobe Experience Manager is used for user experience, product design, and user journeys.

Adobe Experience Manager is a CMS or content management system. It's primary use for web development involves hosting a website. That is, anything that we develop, such as a new feature, a new website, or upgrades, is hosted in Adobe Experience Manager.

We use Adobe Experience Manager primarily for content management.

In general, we work a lot with software requests by our customers, mainly enterprise companies. Typically, our clients are in supplies and they require a complex web portal. They are demanding in terms of quality and usually prefer to work with Adobe and not with Drupal or other platforms because here in Italy, Adobe has a lot of commercial support. We manage a software factory with over 150 employees. We are customers of Adobe and I'm a chief technology architect.

It is helpful for hybrid applications, generic templates, third-party data synchronization, and user-specific data restriction and analytics.