Adobe Journey Optimizer Fundamentals and Use Cases
Adobe Journey Optimizer (AJO) is built on the Adobe Experience Platform (AEP) and is designed for real-time, cross-channel orchestration triggered by customer behavior, alongside scheduled campaign sends. The core mental model is a separation of concerns: profiles and events describe who the customer is and what they just did; journeys define the orchestration logic that reacts to those inputs; channels (email, SMS, push, in-app, direct mail, web) deliver the message; campaigns handle one-off or scheduled batch sends; and decisioning selects the best offer or content.
A recurring trap is confusing Journey Optimizer with Adobe Campaign or Marketo Engage. In AJO questions, the giveaway is real-time event-triggered orchestration on AEP profiles. Another trap is confusing journeys (multi-step, stateful, event- or audience-driven) with campaigns (single send, often scheduled or API-triggered). A third common trap is assuming AJO requires a separate data store; it depends on AEP datasets, schemas, and the Real-Time Customer Profile.
Worked example
A retailer wants: "When a customer abandons a cart, wait 1 hour, send an email, and if they still haven't purchased after 2 days, send an SMS." The correct pattern is a journey with an event trigger (cart abandonment), a wait activity, an email activity, a second wait, a condition on purchase, and an SMS activity. The wrong answers usually describe a campaign with a segment, which cannot react to a real-time event per profile.
Rule of thumb
If the requirement includes "when the customer does X" or "wait, then check", it is a journey. If it is "send this to this audience at this time", it is a campaign.