Skip to content

Commit 457a6f3

Browse files
authored
Clarifying best practices and examples
1 parent 9a9710f commit 457a6f3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/personas/journeys/faq-best-practices.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,12 +11,12 @@ title: Journeys Best Practices and FAQ
1111
When you create a multi-branch split, do not create overlapping conditions that might lead a user to qualify for more than one step at a time.
1212

1313
For example:
14-
- If a multi-branch split has the following conditions, a user who has performed both `webinar attended` and `registration form submitted` will end up in both branches.
14+
- In the case where a multi-branch split is based on the conditions `registration form submitted` and `webinar attended`, a user may satisfy both conditions, and therefore is eligible for both paths.
1515
- To set a priority, branch 2 should then be `who performed registration form submitted and did not perform webinar attended` to ensure mutual exclusivity
1616

1717
### Add time windows whenever possible
1818

19-
Where possible, add a time window when defining conditions to ensure that users exit the step or Journey, rather than remain at the step forever. This prevents Journeys from collecting stale users which can muddle your data for analytics, or cause you to over-target.
19+
Using selective time windows ensures that Journeys carefully target the most high-priority audiences. For example, in a repeat purchase campaign, the initial entry condition may look for all one-time purchasers, then filter out users who have new transactions in the past 7 days.
2020

2121
### Suppress targeting with journey lists
2222

0 commit comments

Comments
 (0)