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/engage/journeys/v2/event-triggered-journeys-steps.md
+27Lines changed: 27 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -442,3 +442,30 @@ There may be cases where events sent to Segment are missing specific properties
442
442
- Similarly, if a mapped trait is missing on the profile, the key is included in the payload with a value of `undefined`.
443
443
444
444
Carefully configuring mappings and handling missing attributes can help you maintain data integrity and avoid errors in downstream systems.
445
+
446
+
## Reconnect branches with path joins
447
+
448
+
Path joins let you connect one branch of a journey to a step in another branch. This eliminates duplicate steps and saves journey step credits when multiple branches need to converge on the same downstream actions.
449
+
450
+
Use path joins when different user segments need different initial treatments but should follow the same steps afterward. For example, high-value customers might receive multiple touchpoints through one branch while standard customers skip directly to a general follow-up step that both groups eventually reach.
451
+
452
+
Path joins work well when:
453
+
454
+
- Different user segments require unique messaging initially but share common downstream steps
455
+
- One branch needs fewer steps than another, and you want both to converge at a specific point
456
+
- Multiple branches lead to the same destination send or action step
457
+
- You want to reduce journey complexity and avoid duplicating identical steps across branches
458
+
459
+
### When to use path joins
460
+
461
+
### Create a path join
462
+
463
+
To create a path join:
464
+
465
+
1. Navigate to the last step in the branch you want to connect.
466
+
2. Click the **+** icon at the end of that branch.
467
+
3. Select **Connect path to existing step**.
468
+
4. Choose a step from another branch to connect to. Segment only shows the available steps you can connect to.
469
+
5. The connection appears as a line on the canvas, showing the path join between branches.
470
+
471
+
You can only connect to child steps (steps that come after the split), not parent steps or steps earlier in the journey. Each branch endpoint supports one path join connection.
0 commit comments