Building customer journeys in Adobe Journey Optimizer is not complicated in concept — trigger an event, sequence a response, branch based on behavior, and repeat. In practice, the configuration decisions that determine whether a journey actually works require experience and planning.
This guide covers what you need to know before building in AJO, how the journey canvas works, and the decisions that experienced practitioners make differently from first-time users.
Journey Types in AJO: Which to Use When
AJO has two primary journey types. Choosing the right one at the start determines how the journey behaves and what configuration options are available.
Event-triggered journeys start when something happens — a customer abandons a cart, makes a purchase, submits a form, or reaches a threshold in a loyalty program. These journeys are for real-time, behavior-driven automation. They are the most powerful type in AJO and the primary use case the platform is built around.
Audience-based journeys start by reading a segment from Adobe Experience Platform and entering all qualifying profiles into the journey at a scheduled time. These work like a traditional campaign or nurture program — useful for onboarding sequences, re-engagement programs, and scheduled lifecycle communications.
A common mistake: using audience-based journeys for use cases that should be event-triggered, because the configuration is simpler. This loses the real-time response capability that is AJO's main advantage over simpler tools.
Need Adobe marketing automation talent?
We place certified Adobe professionals across the US and Canada.
Entry Events and Audience Configuration
Every journey starts with an entry condition. Getting this right is the most important configuration decision you will make.
For event-triggered journeys, the entry event is a schema-defined event in Adobe Experience Platform — a web behavior event, a CRM event, a purchase event, or a custom event your engineering team has defined. The event must be properly configured in AEP before AJO can use it. If the event schema is missing fields or is not set up for real-time streaming, the journey will not trigger correctly.
Key configuration decisions at entry:
- Re-entry settings: can a profile enter the journey again after completing it? After what time period?
- Namespace: which customer identifier (email, ECID, CRM ID) is the primary key for this journey?
- Profile data requirements: what profile attributes does the journey need at entry — and are they present in AEP for all expected entrants?
- Capping: for high-volume events, do you need to limit entry volume per time period to protect downstream systems?
Building the Journey Canvas: Key Configuration Decisions
The journey canvas is AJO's visual builder. You drag and drop actions, conditions, waits, and splits to design the flow. It is intuitive once you understand the components.
Conditions are where most journey logic lives. AJO conditions can read profile attributes, event data, segment membership, and AI scores. The more precise your condition logic, the more relevant the journey experience becomes — but over-complex condition trees become difficult to maintain and debug.
Wait steps control timing. You can wait a fixed duration, wait until a specific time, or wait for an event (like a purchase that closes out an abandoned cart journey). Event-based waits are more powerful but require the events to be reliably streaming into AEP.
Splits create parallel branches based on conditions. Use percentage splits for A/B testing. Use condition splits to serve different experiences based on profile data or behavior.
Need help with staffing?
We place CRM and Marketing Automation professionals across the US and Canada.
Channel Actions: Email, SMS, Push, and Web
Each channel action in AJO links to a message template. Email templates are built in AJO's email designer — a drag-and-drop builder with HTML editing capabilities. SMS messages are plain text with dynamic personalization. Push notifications require the mobile SDK to be implemented in your app.
Personalization in AJO messages uses Adobe's expression language — a syntax that lets you pull profile attributes, event data, and offer content directly into message templates. Well-structured personalization tokens make campaigns significantly more relevant; poorly structured ones create edge cases where profiles receive blank or broken content.
Web actions (web personalization) require AJO to be connected to your website via the Adobe Experience Platform Web SDK. Web personalization in journeys lets you change website content in real time for customers who are actively browsing — a capability that sets AJO apart from pure email/SMS platforms.
Testing, Monitoring, and Optimizing Live Journeys
AJO has a built-in test mode that lets you simulate journey execution with a test profile before going live. Use it. Skipping test mode is the most common source of journey errors in production.
Once live, the journey reporting dashboard shows entry volume, action execution rates, error rates, and channel-level delivery metrics. Watch for:
- High discard rates at conditions: signals that your entry criteria is too broad or condition logic is misconfigured
- Email bounces and unsubscribes: signals that your send frequency or relevance needs adjustment
- Wait step timeouts: signals that event-based waits are not receiving the expected events
- Journey version conflicts: when you update a live journey, existing profiles may still be on the old version — understand how AJO handles versioning before making mid-flight changes
Treat live journey optimization as ongoing work, not a launch-and-forget task. The journeys that perform best are the ones that have been tested, monitored, and iteratively improved over time.