Skip to content

Commit 178b414

Browse files
authored
Merge pull request #2210 from segmentio/DOC_383_Journeys_updates
Build a Journey edits [DOC-383]
2 parents df38daa + fad919e commit 178b414

File tree

1 file changed

+8
-20
lines changed

1 file changed

+8
-20
lines changed

src/personas/journeys/build-journey.md

+8-20
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,6 @@ title: Build a Journey
33
---
44
{% include content/plan-grid.md name="journeys" %}
55

6-
Use this guide to create a new Journey.
7-
86
## Before you begin
97

108
Verify that you've connected at least one source to your Personas space, with events streaming in.
@@ -19,9 +17,9 @@ For more information, see [Setting up your Sources](/docs/personas/quickstart/#s
1917
1. Add a name to describe the step, for example `New users`.
2018
2. Add inclusion conditions, or import conditions from an existing audience to define users who will enter the Journey.
2119
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.
22-
4. Click **Preview** to see the list of user who meet your criteria. Verify that you've defined the right conditions.
20+
4. Click **Preview** to see the list of users who meet your criteria. Verify that you've defined the right conditions.
2321
5. Click **Save**.
24-
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.
22+
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.
2523
5. Click **+** to add the next step and view available step types.
2624

2725
> info ""
@@ -36,7 +34,7 @@ If you select the **Use historical data** option, Segment queries all historical
3634
3735
## Available step types
3836

39-
Journeys provides 5 step types, which you can add after the entry condition.
37+
Journeys provides five step types, which you can add after the entry condition.
4038

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

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

4745
**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.
4846

49-
**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.
47+
**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.
5048

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

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

55-
**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.
53+
**Multi-branch split** divides the group of users from the previous step into two or more branches based on each branch's defined conditions.
5654

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

5957
> info ""
6058
> Journeys doesn't enforce mutual exclusivity in branch conditions. For more information about ensuring branch exclusivity, see [Best Practices](#).
6159
62-
**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)
60+
**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)
6361

6462
## Cloning a Journey
6563

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

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

93-
- It may take up to 3 hours for Journeys to compute user counts after publication.
91+
- It may take up to three hours for Journeys to compute user counts after publication.
9492
- You can edit a Journey's name, description, and Destination steps.
9593
- You can't add, edit, or delete other steps in the Journey.
9694
- Once Journeys computes and displays user counts, you’ll see the list of users at each step of the Journey.
9795
- Click a user profile to see the Journey list to which they belong.
9896
- Journeys sends and updates data to Destinations in real-time.
99-
100-
## Edit name, description, and Destinations
101-
102-
### Edit name and description
103-
To edit your Journey name and description, navigate to the **Settings** tab of the Journey Overview.
104-
105-
### Edit destinations
106-
To edit Destinations, click **Edit Destinations** from the Journey Overview. You can add, edit, or delete connected Destinations within existing Send to Destinations steps.
107-
108-

0 commit comments

Comments
 (0)