Orchestrate journeys across email, SMS, push, in-app, and web. AJO design, decisioning, and content authoring. Connected to RT-CDP audiences and CJA insights to close the analyze-activate-measure loop.
[ GET THE 2026 BENCHMARK → ]Adobe Journey Optimizer is the orchestration layer of the Adobe stack. It listens for events, decides what should happen next, and delivers the message across the channel that fits. It pulls audiences from Real-Time CDP. It gets its insights from Customer Journey Analytics. It is the place the analyze-activate-measure loop closes.
That is the design. The reality of most AJO deployments is narrower. Most enterprises ship AJO as a better email tool. The other channels stay dormant.
From our benchmark of AJO deployments:
The largest unrealized value sits in the 91% of journeys that are not yet orchestrated across channels. The fix is rarely technical. It is a prioritization problem and a content production problem. We help with both.
We design AJO journeys around the customer event, not around the channel. The first question is always: what just happened, what does it mean, and what is the right next interaction across any channel? Once that is answered, the channel choice falls out of the journey logic.
We use the Journey Canvas to model the orchestration. We define the qualifying audience, the trigger event, the decision logic, the channel branches, and the hold-out controls. We integrate with Real-Time CDP for the audience layer and with the consent service for the channel-level permissions.
Decisioning configurations are present in 31% of AJO deployments and tuned in 9%. The gap is the difference between deploying decisioning and using it.
We configure decisioning when the use case justifies it: cross-sell offers, retention offers, dynamic content selection, journey-step branching. We define the offers, the constraints, the eligibility rules, and the ranking strategy. We instrument the decisioning so that the team can see which offers are being chosen and why.
The biggest practical bottleneck in AJO is content production. The platform is fast. The content team is not. We help by templating the recurring journey patterns: the welcome series, the onboarding series, the cart abandonment, the re-engagement, the renewal series. Each template ships with the message structure, the personalization slots, and the variant guidelines. The content team fills in the body. The team ships in days, not months.
AJO without CJA is a black box. AJO with CJA is a system that learns. We instrument every journey with the metrics that matter: qualification rates, message delivery, message engagement, downstream conversion, and the counterfactual against the holdout. We build the workspace dashboards in CJA so the marketing team sees journey performance the same way the product team sees feature performance.
An AJO foundation engagement runs 8 to 12 weeks. A cross-channel orchestration playbook with the first three high-value triggers ships in 8 weeks. A migration from a legacy MTA to AJO runs 12 to 16 weeks.