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.
N/A
Pega Customer Decision Hub
Score 6.9 out of 10
N/A
Pega Customer Decision Hub optimizes customer lifetime value by providing an “always-on brain” to unify data, analytics, and channels into one connected experience. Customer Decision Hub collects data from every interaction as it’s taking place, combines that with the customer’s full interaction history to determine their current context, and then delivers nextbest-action recommendations. Pega aims to enable users to pivot between selling, serving, retaining, and nurturing in real time.
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
PRPC is a BPM and Case management suite from Pega Systems. Pega is a comprehensive suite which offers a unique theme of BPM development in the market. A no-coding approach based on rules with inheritance makes Pega a very powerful product but is very difficult to learn. Even, if we go to Pegasystems for training, we have to work on a project at least for a year to have some confidence. Areas where it requires improvements: 1) One of the first things that client's IT department questions about is proprietary BLOB column in PRPC, for them, it is a disadvantage, but as we all know BLOB is what makes the highly complex data model of any BPM application fit inside to a common schema which eliminates the help of a DBA. 2) Another area of improvement is: when using the wizards to generate rules (such as the connector wizards) you have to be careful about the level of coupling between the work object's data model and the interface's data model. This can also create maintenance issues. 3) The complete Pega suite of products have a long time to develop and deploy and it can be easily done using other low-cost software.
Site speed and performance can be impacted when using GraphQL for headless applications
Adobe Experience Manager is difficult to learn for new users, and is often a burden to train users when authoring is delegated to property teams with high turnover
Updating content is more difficult when using content fragments, as content needs to be updated in multiple areas
Pega Customer Engagement Suite is ready to use out of the box with several features, but custom development is always needed.
Although new features can be quickly implemented, they have to go through a screening Business analysis process, QA screening and SCRUM based development.
Pega eliminates the need for custom code, but there are rare cases where an specific requirement has little to no support from Pega, and implementing custom code can break OOB functionality and make the system unstable.
We had and still have a fantastic experience using Adobe CQ. Lots of flexibility, great integration with other Adobe products we already use and a powerful technology make it a great fit for our corporate environment. Also as the community grows, it makes it easier to network with other developers and users to get new ideas on how to continue to get the best out of the software.
Pretty easy to use and learn. Lots of great features that could make it more complex, but there are great resources to help navigate usage given it’s so widely adopted. I have used this at two different companies now, and it’s proven to be very effective in managing both brands' digital presence.
When it comes to availability, adobe experience manager is the best with little to no downtime at least during business hours. Considering the enterprise scale and critical business solutions built on experience manager, availability was our primary requirement during CMS evaluation and adobe fits best on this parameter. If there's a planned upgrade, adobe would make sure they do it in non-business hours.
Page load time is important to me for search engine optimization reasons. I cannot say I have been particularly impressed by Adobe Experience Manager in this area so far. When using tools like Google's PageSpeed Insights, the reports received on our AEM pages have suggested there is a lot of room for improvement, especially when assessing mobile performance.
Adobe Experience Manager, in all its capacity, is a great alternative to any other CMS you are using. It helps in rapid development and makes life easier for maintaining the website for multi-language sites. Technical know-how is eliminated at content authoring. Better documentation in terms of live examples with videos would be appreciated.
Depending on your individual needs, It is really quite simple to create an authoring experience for a website that looks really good. I have been part of many implementations and many teams and have seen many projects that were super successful and others that were not implemented well. AEM has room for a lot of flexibility in the implementation process compared to other CMS like SharePoint
AEM provides a sustainable quality of work that goes long-lasting, and we don't need to worry about future updates as AEM gives time-to-time security, patch, and platform updates. Not only updates, AEM introduces new features every now and then, which not only encourage its users but also lets us pay a good amount for it as well; apart from customizing the website, AEM also provides us with community forums that facilitate and increase customer engagement. In AEM forums, we can also rank users, give them badges and promote them to put more content on the community.
Instead of being directly involved in the tool purchase, I am involved in analysis or what we can use to maximize the tool. Small organizations may find it expensive. However, if the team or organization focuses more on your ROI or the features you will get, then it will definitely be worth it. Pricing is based on a number of factors, including team size or the use of the tool. The user can select the pricing option that best fits their needs based on the number of form submissions they make or the number of pages they wish to publish on their global/multisite sites.
The professional services team within adobe is one of the best in terms of technical and solutioning knowledge. However, considering the billing charges of adobe professional services team, it is always recommended to involve them during platform initial setup or when a complex solution is to be built with platform customizations.
Adobe Experience Manager has allowed us to create translated versions of our website to serve to other divisions of our company around the world.
Adobe Experience Manager has allowed us to achieve one of our primary objectives of knowing who are users are by tracking their movement across our website and content, via our tagging taxonomy that classifies our content.
Adobe Experience Manager allows us to create reusable and scalable content via the Experience Fragment methodology, which injects dynamic page content within the page template that can be plug and played into other pages.
One negative aspect is that by consolidating so many websites under one roof in Adobe Experience Manager, it takes away the freedom of other smaller sects of our organization from creating their own websites and templates, as they are required in some cases to adhere to the rigidity of the templates set in Adobe.
