Adobe Experience Cloud
An AJO journey is only omnichannel if identity and progress travel with it
Design cross-channel AJO journeys around identity, events and a measurable customer goal.
November 10, 2026
A lifecycle team can put web, email and push actions on one canvas and still lose the customer between channels. An AJO community question asks how to model that progression and see the end-to-end journey, rather than a series of channel reports.
Begin with one customer task
Write the outcome first: for example, complete an application after starting it on the web. Define the events that prove each step, the identity used to join web and mobile activity, and the time window for a legitimate continuation. A send or impression is not the same as task completion.
Adobe's journey configuration guide describes events, data sources and actions. Its unified Action activity covers native channels including email, push, in-app and web. The channel matrix helps verify where each channel can run.
Choose the orchestration boundary
Use one journey when the customer's state and next decision belong to one coherent process. Split into separate journeys when the goals, owners or timing differ, and use explicit events or profile state to pass context. Test the same person moving from anonymous web to authenticated app, including a missing identity link.
Measure entry, step transition, suppression and outcome by a stable profile key. Add a customer-level trace alongside channel delivery metrics; otherwise a campaign dashboard can look healthy while people stall between steps.
Adovo’s view
Omnichannel is a continuity claim, not a channel count. If the team cannot explain why one person received the next action and whether that person progressed, the canvas is only a diagram. Make identity and outcome observable before adding more touchpoints.
