omni-channel journeys across channel using AJO

Hi ​@silpasurapaneni Designing and managing an omnichannel journey is quite a task! Here are a few things to keep in mind:

What AJO supports today

Adobe Journey Optimizer provides a single canvas for building personalized messages and orchestrating journeys across channels, and recent releases have expanded omnichannel reach further by adding code-based, in-app, and web channels directly onto the journey canvas as inbound touchpoints, alongside the established email, push, and SMS channels. 

• A single event-driven journey canvas that can span email, push, SMS, web (in-browser messaging), in-app/mobile, and custom/code-based actions in one journey
• Real-time entry and decision points triggered by events from any of those channels, since they all write into the same Real-Time Customer Profile
• Parallel re-entry, letting a profile re-enter an event-triggered journey while still active in it, so you can send parallel context-specific messages without duplicating journeys, and multi-action activation to trigger several inbound experiences at once Adobe
• Basic step-level journey reporting (entries, conversions, drop-off per step) scoped to that specific journey

What it does not give you natively is a single "customer 360 journey map" that stitches together activity that happens outside a given journey's own canvas — that's where Customer Journey Analytics comes in (Refer #4).

2. How to model it: one journey vs. connected journeys

Default to one centralized journey per business goal, with channel-specific branches inside it, whenever AJO itself controls the hand-off timing. Your example (web action → email → app step → push) is exactly the pattern AJO's canvas is built for: entry event from web, wait/decision node, email action, another wait/decision node listening for an app event, push action.

Reach for separate journeys connected by shared events instead when:

• Different teams own different channel experiences on different release cadences (e.g., the mobile app team ships independently of marketing ops)
• A step isn't something AJO triggers directly — it's a native app flow or web experience that only reports back to AEP as an event, which AJO then reacts to as an entry/decision point in the next journey
• You want reusable modules (e.g., a shared onboarding sequence triggered by multiple parent journeys)

Rule of thumb: keep decision logic centralized in one journey wherever the hand-off is tightly coupled and time-sensitive; use cross-journey events as the connective tissue where ownership or timing is decoupled.

3. Maintaining continuity across channels: identity

This is the layer everything else depends on. Continuity comes from the AEP Identity Service and Real-Time Customer Profile, not from AJO itself:

• Define a primary identity (CRM ID, loyalty ID, authenticated user ID) and secondary namespaces per channel — ECID for web, push token/device ID for mobile, email address — and get your merge policy right so all of these stitch into one profile
• Every channel's SDK (Web SDK for web, AEP Mobile SDK for the app) needs to consistently send the resolvable identity, and critically, needs to link the anonymous ID to the authenticated ID the moment a user logs in — this is the most common failure point (an anonymous web session never gets tied to the authenticated profile before the email/push steps fire)
• Journey wait-conditions, splits, and next actions in AJO are all evaluated against the profile ID, so as long as every event carries a resolvable identity, the journey doesn't care which channel the event came from

Before launch, walk through the actual cross-device scenario in AEP's Identity Graph to confirm there's no fragmentation — this is worth testing explicitly rather than assuming it works.

4. Visualizing end-to-end progression

AJO's own reports are journey-scoped, not customer-journey-scoped. The recommended pattern for the cross-channel view you're describing is pairing AJO with Customer Journey Analytics (CJA):

• CJA collects and normalizes omnichannel data, including behavioral, transactional, and operational data, into a single actionable profile, and stitches together complex identity structures to provide journey visualizations and consistent measurement for marketing and operations teams in Journey Optimizer Adobe
• CJA's stitching rekeys identities across dataset rows so records — including both authenticated and unauthenticated sessions — resolve to a single person-level ID rather than device or cookie level, using either field-based stitching or, for more complex identity graphs, graph-based stitching, which harnesses the Adobe Experience Platform Identity Service graph to elevate datasets to their preferred identity AdobeAdobe
• You can customize the reporting interface directly inside Journey Optimizer by building a template in CJA and saving it to be used on the Reports page in Journey Optimizer — so the cross-channel view can live inside AJO's own UI rather than a separate tool Adobe
• Once stitched, CJA's Workspace (Flow/Fallout visualizations) is what actually shows the real sequence of touchpoints a person or segment took, across AJO deliveries, web, app, and even offline channels like call center or in-store, rather than inferring it from one journey's own step metrics

Where AJO is heading,

• Continued expansion of inbound channel support (code-based, in-app, web) directly on the canvas, more real-time/parallel journey handling, and heavier investment in Adobe CX, Journey agents & MCP etc. You can look at the recent AJO roadmap session for more details.