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/journeys-logic.md
+11-3Lines changed: 11 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ By the end of this guide, you'll understand how and why users progress through y
15
15
16
16
## Entry Conditions and Step Behavior
17
17
18
-
Journeys begin with an entry condition that computes like standard [Personas Audiences](docs/personas/audiences/). This entry condition queries your customer data in Segment to find users who meet your specified criteria.
18
+
Journeys begin with an entry condition that computes like standard [Personas Audiences](/docs/personas/audiences/). This entry condition queries your customer data in Segment to find users who meet your specified criteria.
19
19
20
20
After users meet the Journey's entry condition, their progress through the Journey depends on satisfying the criteria of subsequent Journey steps.
21
21
@@ -52,7 +52,7 @@ To evaluate whether a user has ever joined the previous step, Journeys appends t
52
52
53
53
### Condition Steps
54
54
55
-
“Add a condition” steps operate like [Personas audiences](/docs/personas/audiences/). The defined conditions provide criteria for each step’s membership.
55
+
“Add a condition” steps operate like [Personas Audiences](/docs/personas/audiences/). The defined conditions provide criteria for each step’s membership.
56
56
57
57
### Wait Times
58
58
@@ -80,7 +80,15 @@ Consider the following example of Journey conditions for a cart abandonment camp
80
80
3. Step Condition: User is member of `Example Audience A`
81
81
4. Send to Destination
82
82
83
-
If a user makes a purchase during the wait time of 5 days, the system would update membership to `false` for the audience created from the entry condition. However, when evaluating Step Condition 3, the `preceding_step_audience_member` trait would remain on the user’s profile as true. As a result, the user would meet the step’s conditions and continue to progress through the Journey.
83
+
If a user makes a purchase during the wait time of 5 days, the system would automatically update membership to `false` for the audience created from the entry condition, Step 1. However, the user could still satisfy Step Condition 3 based on the three step membership conditions:
| Has the user ever joined the previous step? | True; `preceding_step_audience_member` remains true. |
89
+
| Does the user meet the specified step conditions? | True; assuming user is member of `Example Audience A`. |
90
+
| Has the user met preceding N wait time conditions? | True; once 5 days has passed from initial entry. |
91
+
84
92
85
93
To maintain best practices and enforce your funnel, re-check or modify audience conditions that follow wait steps. For example, adding a `purchases = 0` condition to Step 3 results in Segment not advancing users who made a purchase during the wait time:
0 commit comments