Creating Journeys
Journeys are multi-step orchestrated experiences that guide users through complex workflows over time. Unlike individual flows (which run within a single session), journeys span multiple sessions and can include delays, conditions, and branching logic.
Journeys vs. Flows
| Flows | Journeys | |
|---|---|---|
| Scope | Single session, one or more pages | Multiple sessions, multiple features |
| Duration | Seconds to minutes | Hours to weeks |
| Steps | Tooltips, modals, beacons, banners, slideouts, videos, forms, inputs, clicks, navigates, waits, scrolls | Content items (including flows), surveys, waits, wait-for-event, conditions, splits, goal checks |
| Use case | Feature walkthrough, multi-step tutorial, in-app form | Onboarding program, training path, adoption campaign |
Creating a Journey
- Navigate to Content > Journeys in the dashboard.
- Click Create New Journey.
- Enter a name and description.
- Open the journey builder to add and connect steps (see Journey Builder).
- Configure enrollment rules (see Enrollment below).
- Click Publish when ready to launch.
Journey Statuses
Every journey has a lifecycle status that controls whether it accepts new enrollments:
| Status | Description |
|---|---|
| Draft | Journey is being designed. No users are enrolled. |
| Published | Journey is live. New users matching the enrollment criteria are enrolled automatically. |
| Paused | Journey is temporarily suspended. Already-enrolled users stop progressing but retain their position in the journey. New enrollments are blocked until the journey is resumed. |
| Archived | Journey is hidden from the active list. Historical enrollment data remains accessible. |
Enrollment
Enrollment controls how users enter a journey and tracks their individual progress through it.
How users are enrolled
- Auto-enroll — Automatically enroll users who match a configured target audience. Users are enrolled as soon as the journey is published and they satisfy the audience rules. New users who meet the criteria after publishing are enrolled on their next qualifying session.
- Manual enrollment — Enroll a specific user programmatically using
DAP('startJourney', journeyId)in the SDK.
Per-user progress
Each enrolled user moves through the journey independently at their own pace. A user's progress through a journey can be in one of these states:
| State | Description |
|---|---|
| Active | The user is currently progressing through the journey. |
| Completed | The user reached an exit node and finished the journey. |
| Stopped | The user was manually removed from the journey before completing it. |
| Archived | The user's enrollment record has been archived. Journey content is no longer shown. |
You can view and filter enrollment records for any journey from the Enrollments tab on the journey detail page.
Re-enrollment
By default, each user can only be enrolled in a given journey once. If you want users to be able to go through the journey again after completing or exiting it — for example, for refresher training — enable Allow re-enrollment in the journey settings.
Anonymous Enrollment
Journeys can be shown to users who have not yet been identified, such as visitors on a marketing site or users in the early steps of sign-up.
To enable this, turn on Allow anonymous users in the journey settings. Once enabled:
- The SDK will enroll and advance anonymous visitors through the journey without requiring a sign-in.
- If the visitor later identifies themselves (for example, by logging in), their anonymous journey progress is automatically carried over to their user account.
This is most useful for top-of-funnel onboarding where you want to start guiding users before you have a stable identity for them.