Adobe Journey Optimizer vs. Pusher

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

Incentivized

As I told you earlier, if you just want to send regular push notifications to the app users, then Pusher shall not be your first choice. However, if you wish to make the app a little more interactive by making live changes in the app using Pusher and sending your user's real-time notifications, then you should definitely try it.

• pre built use case playbooks provide a basis for various trips
• provides customized messaging
• custom actions let different systems and databases be easily integrated

Incentivized

• Pusher allows live changes in the UI using push requests. We can also integrate it with the PHP source code.
• They offer 99.99% uptime, so we can trust on their services.
• Pusher works well along with the Flutter codebase, so we do not have to modify it much to work on cross-platforms.

Incentivized

• It doesn´t keep the last search you sis in the journeys and you have to enter the search parameter every time
• there is a window of time during the day that the audiences give out errors and you can´t see the estimates
• I should be able to select STO in campaigns, not only in journeys
• I should be able to select the email parameters when using campaigns

Incentivized

• Not a good support system.
• Poor documentation.
• Date transmission encryption issues.

Incentivized

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

Incentivized

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

Incentivized

• 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

Incentivized

• We had over ten thousand customer orders go through over the course of a year with no problems with this API
• There was very minimal support for this API which allowed us to focus on other priorities.

Incentivized