You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/personas/journeys/build-journey.md
+8-17Lines changed: 8 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,13 +44,13 @@ Journeys provides five step types, which you can add after the entry condition.
44
44
45
45
**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.
46
46
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.
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.
48
48
49
49
You can add Step Names to describe the users in the True and False branch.
50
50
51
51

52
52
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.
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.
54
54
55
55
Define the number of branches you want to create, then add a **Wait for condition** step to define each branch's condition.
56
56
@@ -61,20 +61,20 @@ Define the number of branches you want to create, then add a **Wait for conditio
61
61
62
62
## Cloning a Journey
63
63
64
-
To clone a Journey:
65
-
1. In Journey List view, click the **…** icon at the end of a row.
66
-
2. Select **Clone Journey**.
64
+
To clone a Journey:
65
+
1. In Journey List view, click the **…** icon at the end of a row.
66
+
2. Select **Clone Journey**.
67
67
68
-
Segment then creates a draft of your Journey.
68
+
Segment then creates a draft of your Journey.
69
69
70
-
You can also clone a Journey from a Journey’s Overview by clicking the **…** icon.
70
+
You can also clone a Journey from a Journey’s Overview by clicking the **…** icon.
71
71
72
72
## Publishing a Journey
73
73
74
74
To publish and activate a Journey, click **Publish Journey** from the Journey Overview. You can also click **Publish Journey** in the bottom-right corner of the Journey Builder.
75
75
76
76
> info ""
77
-
> After publication, Segment limits which Journeys features you can edit. For more information, see the difference between Draft and Published Journeys below.
77
+
> Some Journey features can only be edited before publication. For more information, see the difference between Draft and Published Journeys below.
78
78
79
79
## Journey re-entry
80
80
@@ -106,15 +106,6 @@ To enable Journey re-entry for a new Journey, follow these steps:
106
106
3. Under **Exit settings**, enter an exit time.
107
107
4. Click **Build Journey** to complete Journey setup.
108
108
109
-
To enable Journey re-entry for an existing Journey, follow these steps:
110
-
111
-
1. Select the **Journeys** tab within your Personas space.
112
-
2. Select the Journey for which you want to enable re-entry.
113
-
3. Select the **Settings** tab from the Journey overview.
114
-
4. Under **Entry settings,** select **Re-Entry** and enter a re-entry time.
115
-
5. Under **Exit settings**, enter an exit time.
116
-
6. Click **Update Settings**.
117
-
118
109
## Pausing and resuming a Journey
119
110
120
111
Pausing a published Journey prevents new users from joining your Journey. Users already in the Journey, however, will continue their progress.
0 commit comments