Journey Orchestration

Journey is a multi-step workflow that reacts to time and user behavior. Use it to guide users through onboarding, post-purchase follow-ups, cart abandonment, or reactivation flows with timed actions and branching logic. Define entry rules, audiences, and conversion events, then monitor engagement and conversions to optimize each step.

circle-info

This page is the overview. Use the cards below for the actual setup steps.

When to use a journey

Use a journey when timing and branching matter.

Common patterns:

  • Onboarding sequences

  • Cart abandonment and browse abandonment

  • Post-purchase follow-ups

  • Reactivation when users go inactive

Key concepts (fast)

  • Entry rule: When a user can enter (time-based or action-based).

  • Eligibility: How often a user can re-enter (once, lock duration, capping).

  • Audience: Who can enter (segments, tags, profile filters).

  • Conversion event: What “success” means for the journey.

  • Correlation (optional): A key that ties events to one journey instance.

Quickstart: build a working journey

1

1) Decide the goal and the success signal

Pick a conversion event if you will measure lift.

You can’t change it after launch.

2

2) Choose an entry rule

Use time-based for schedules.

Use action-based for event-triggered flows.

3

3) Define the audience

Start with a narrow segment.

Expand once you trust the logic.

4

4) Build the flow

Add steps using core components.

Use branches for “did/did not” and attribute-based splits.

5

5) Launch and monitor

Launch once the entry rule and conversion event are final.

Use analytics to validate volume, drop-offs, and conversions.

Components reference

Examples and how-to videos

Last updated

Was this helpful?