Skip to content

Commit 5916228

Browse files
committed
exit rules fixes
1 parent 1814a21 commit 5916228

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

src/engage/journeys/v2/exit-rules.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Exit rules don't wait for a profile to reach a specific step; they apply globall
1717

1818
## Configuring exit rules
1919

20-
You'll set up exit rules in the journey’s settings panel. By default, journeys don’t have any exit conditions, but you can choose to add up to five exit events.
20+
You'll set up exit rules in the journey’s settings panel. By default, journeys don’t have any exit conditions, but you can choose to add up ten five exit events.
2121

2222
## Basic setup
2323

@@ -31,8 +31,6 @@ For each exit rule, choose the event that should trigger the exit. You can also
3131

3232
You can optionally require that the exit event matches the same identifier used in the entry event. This helps tie the two together, like if a journey starts with a `Cart_Modified` event and should exit only when `Order_Purchased.cart_id` matches the same cart.
3333

34-
Each exit rule must be mutually exclusive.
35-
3634
> success "Exit rules Analytics"
3735
> You can track how exit rules are performing from the journey overview, which shows total exits per rule, and from individual step details, which show where users exited.
3836
@@ -73,6 +71,6 @@ Follow these tips to make sure your exit rules behave as expected:
7371

7472
As you work with exit rules, keep the following in mind:
7573

76-
- You can configure up to 5 exit events per journey.
74+
- You can configure up to 10 exit events per journey.
7775
- Journeys support only one destination send for exit events.
7876
- If an exit rule is triggered, it overrides all other steps. The user exits immediately, even if they’re mid-delay or hold.

0 commit comments

Comments
 (0)