Adobe Journey Optimizer is a customer engagement solution, enabling brands to orchestrate and deliver personalized customer engagement across all channels — including email, web, app, mobile, and more — in the moments that matter to customers.
N/A
Pega Customer Decision Hub
Score 7.2 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.
AJO is best suited for advanced Martech teams who are already bought into the Adobe ecosystem through the use of RTCDP, AA, AAM, etc. Organizations that are starting their Martech journey are good candidates, as well as those who are reevaluating all of their marketing channel vendors near the same time. Success in AJO is highly dependent on the number of marketing channels added. Close coordination with database teams is essential for success. Many of the offline data requirements benefit from modeling of the data. Having dedicated resources developing AJO (RTCDP)-specific views will reduce the amount of QA required to bring the solutions to market
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.
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.
At times, Adobe Journey Optimizer offers too many options, making things less user-friendly than I would personally prefer. As mentioned earlier, there is a tendency to encounter decision paralysis with the increase in available options. While having options is excellent, in typical Adobe fashion, too many can be overwhelming for users
They both have their pros and cons, I feel it depends on the users that the products are targetting, SFMC is has more specialized customizations, Adobe does offer similar but require a higher technical knowledge which is not something that is provided bt the other product
Multichannel onboarding journey improving the engagement of freshmen in the business, resulting in a decrease in the dropout rate.
Separate business of anticipation of receivables from suppliers that used to be manual and now I have connected this entire operation via the S3 connector, less manual work and significant gains in conversions and payments