Skip to content

Commit 4fc56d8

Browse files
authored
Update journeys-logic.md
More edits, yay
1 parent 22a014d commit 4fc56d8

File tree

1 file changed

+11
-3
lines changed

1 file changed

+11
-3
lines changed

src/personas/journeys/journeys-logic.md

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ By the end of this guide, you'll understand how and why users progress through y
1515

1616
## Entry Conditions and Step Behavior
1717

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.
1919

2020
After users meet the Journey's entry condition, their progress through the Journey depends on satisfying the criteria of subsequent Journey steps.
2121

@@ -52,7 +52,7 @@ To evaluate whether a user has ever joined the previous step, Journeys appends t
5252

5353
### Condition Steps
5454

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.
5656

5757
### Wait Times
5858

@@ -80,7 +80,15 @@ Consider the following example of Journey conditions for a cart abandonment camp
8080
3. Step Condition: User is member of `Example Audience A`
8181
4. Send to Destination
8282

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:
84+
85+
86+
| Semantic Logic | Written Logic Condition |
87+
|----------------------------------------------------|-------------------------------------------------------|
88+
| 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+
8492

8593
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:
8694

0 commit comments

Comments
 (0)