Adobe Journey Optimizer: Journeys vs Orchestrated Campaigns

At first glance, Journeys and Orchestrated Campaigns in AJO can look very similar. Both can work with audiences, contain multiple steps, include waits and conditions, and orchestrate communication across channels. Initially it also looks like Orchestrated Campaigns are for batch workflows whereas Journeys are for trigger/event-based workflows. However, a Journey can also behave like a batch-oriented workflow when Read Audience is used as the entry criteria.

So, the question is: if Read Audience can be used as the entry point in Journey and process an entire audience, why do we need Orchestrated Campaigns?

The difference is not simply trigger/event vs batch. The answer is that Journeys are profile-centric and Orchestrated Campaigns are campaign-centric.

Journeys: Think about the customer’s progression

A Journey is designed around the experience of an individual profile.

For example, consider a cart abandonment scenario:

Cart Event
    ↓
Wait 2 hours
    ↓
Did the customer purchase?
   /             \
 YES             NO
  ↓               ↓
Exit            Email
                  ↓
               Wait 1 day
                  ↓
                 SMS

The important part here is that each profile can progress differently.

Customer A may purchase and exit.

Customer B may not purchase and receive the reminder.

Customer C may take a completely different path based on another condition or event.

Journeys are particularly useful when customer behaviour or events should influence what happens next.

They can also start with Read Audience.

For example:

Read Audience
      ↓
Email
      ↓
Wait
      ↓
Condition / customer behavior
      ↓
Different paths

So, Read Audience Journey is not just a simple batch campaign. The initial audience may be loaded in batch, but the subsequent orchestration can still be profile-centric.

Orchestrated Campaigns: Think about campaign execution

Orchestrated campaigns are naturally suited for batch campaign execution and audience processing.

For example:

Build Audience
      ↓
Enrich
      ↓
Split
   /     \
Group A  Group B
   ↓       ↓
 Email     SMS
      \   /
       ↓
   Follow-up

This becomes especially useful when the campaign requires more complex audience construction, enrichment or splits.

A campaign might target customers based on a combination of:

• Customer attributes
• Purchase history
• Product information
• Loyalty information
• Store or account relationships

A simple way to decide

Choose a Journey when:

• The customer’s behaviour should determine the next step.
• You need event-driven orchestration.
• Different profiles should progress differently.
• You need to maintain an ongoing customer experience.
• You’re building use cases such as cart abandonment, onboarding, post-purchase journeys, etc.

Choose an Orchestrated Campaign when:

• The primary requirement is a campaign against a defined population.
• You need complex audience construction or refinement.
• You need enrichment, reconciliation or splits.
• The campaign execution is more important than maintaining an individual customer journey state.

Both capabilities overlap, and there will be use cases where either could accomplish the requirement. The better choice depends on whether the problem being solved is customer progression or campaign execution.