Skip to content

Build a Journey edits [DOC-383] #2210

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 30, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 8 additions & 20 deletions src/personas/journeys/build-journey.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,6 @@ title: Build a Journey
---
{% include content/plan-grid.md name="journeys" %}

Use this guide to create a new Journey.

## Before you begin

Verify that you've connected at least one source to your Personas space, with events streaming in.
Expand All @@ -19,9 +17,9 @@ For more information, see [Setting up your Sources](/docs/personas/quickstart/#s
1. Add a name to describe the step, for example `New users`.
2. Add inclusion conditions, or import conditions from an existing audience to define users who will enter the Journey.
3. Check **Use historical data** to allow users who have already matched the entry criteria to enter the Journey. Otherwise, only users who meet the entry conditions after publication will enter the Journey.
4. Click **Preview** to see the list of user who meet your criteria. Verify that you've defined the right conditions.
4. Click **Preview** to see the list of users who meet your criteria. Verify that you've defined the right conditions.
5. Click **Save**.
4. Segment displays the entry condition on the Journey Builder canvas. It may take up to 2 minutes for Segment to estimate the number of users in the journey.
4. Segment displays the entry condition on the Journey Builder canvas. It may take up to two minutes for Segment to estimate the number of users in the journey.
5. Click **+** to add the next step and view available step types.

> info ""
Expand All @@ -36,7 +34,7 @@ If you select the **Use historical data** option, Segment queries all historical

## Available step types

Journeys provides 5 step types, which you can add after the entry condition.
Journeys provides five step types, which you can add after the entry condition.

![Step types](images/journey_step-types.png)

Expand All @@ -46,20 +44,20 @@ Journeys provides 5 step types, which you can add after the entry condition.

**Wait for duration** defines the length of time in minutes, hours, days, or weeks that a user must wait before moving to the next step.

**True/false split** divides the previous step's user group into 2 branches, based on Boolean logic against a defined condition. Users who satisfy the condition(s) move to the **True** branch. Otherwise, they move to the **False** branch. To enforce mutual exclusivity, Journeys evaluates true/false conditions when a user reaches the relevant step.
**True/false split** divides the previous step's user group into two branches, based on Boolean logic against a defined condition. Users who satisfy the condition(s) move to the **True** branch. Otherwise, they move to the **False** branch. To enforce mutual exclusivity, Journeys evaluates true/false conditions when a user reaches the relevant step.

You can add Step Names to describe the users in the True and False branch.

![true/false split](images/journey_t-f-split.png)

**Multi-branch split** divides the group of users from the previous step into 2 or more branches based on conditions you define for each branch.
**Multi-branch split** divides the group of users from the previous step into two or more branches based on each branch's defined conditions.

Define the number of branches you want to create. Then, add a **Wait for condition** step to define each branch's condition.
Define the number of branches you want to create, then add a **Wait for condition** step to define each branch's condition.

> info ""
> Journeys doesn't enforce mutual exclusivity in branch conditions. For more information about ensuring branch exclusivity, see [Best Practices](#).

**Send to Destinations** delivers information about the journey to the selected Destination. For more information, see [Send data to Destinations](/docs/personas/journeys/send-data)
**Send to Destinations** delivers information about the Journey to the selected Destination. For more information, see [Send data to Destinations](/docs/personas/journeys/send-data)

## Cloning a Journey

Expand Down Expand Up @@ -90,19 +88,9 @@ When you’ve finished creating your Journey, click **Save as Draft** in the bot

Keep the following considerations in mind when working with a published Journey:

- It may take up to 3 hours for Journeys to compute user counts after publication.
- It may take up to three hours for Journeys to compute user counts after publication.
- You can edit a Journey's name, description, and Destination steps.
- You can't add, edit, or delete other steps in the Journey.
- Once Journeys computes and displays user counts, you’ll see the list of users at each step of the Journey.
- Click a user profile to see the Journey list to which they belong.
- Journeys sends and updates data to Destinations in real-time.

## Edit name, description, and Destinations

### Edit name and description
To edit your Journey name and description, navigate to the **Settings** tab of the Journey Overview.

### Edit destinations
To edit Destinations, click **Edit Destinations** from the Journey Overview. You can add, edit, or delete connected Destinations within existing Send to Destinations steps.