Skip to content

Commit 1fec935

Browse files
authored
Merge pull request #8156 from segmentio/last-journeys-updates
Update Journeys context verbiage
2 parents de40086 + 6c3181a commit 1fec935

File tree

3 files changed

+7
-2
lines changed

3 files changed

+7
-2
lines changed
157 KB
Loading
20.5 KB
Loading

src/engage/journeys/v2/event-triggered-journeys-steps.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -177,10 +177,13 @@ Data split branches can evaluate conditions based on event properties stored in
177177
When you configure a branch with journey context conditions:
178178

179179
1. Select the event object from journey context.
180-
- The triggering event is always available, and any events from Hold until steps on the current path also show up.
180+
- The triggering event is always available. Any events captured in Hold until steps on the current path also appear, along with other data added to journey context by steps in the current path.
181181
2. Choose the specific property from that event.
182182
3. Define the condition and value.
183183

184+
![Data split panel showing branch conditions with journey context selected. The panel displays a branch named "Split on Context" with conditions set to "with journey context" where the property "Category" from "Example Event" equals any of "A, B, C". A second condition shows a dropdown for selecting journey context events including "Trial_Ended" and "Example Event". The left side shows the journey canvas with a Hold Until step, Data split steps, and completed end states.](../images/data_split_journey_context.png)
185+
186+
184187
Segment shows only event context available on the journey path leading to the Data split step. If an event was captured in a Hold until step on a different branch, it won't appear as an option for conditions on the current branch.
185188

186189
You can combine journey context conditions with trait-based and audience-based conditions in the same branch. Segment evaluates all conditions using `AND` logic, so the journey instance must satisfy every condition to follow that branch.
@@ -458,6 +461,8 @@ Path joins work well when:
458461

459462
### Create a path join
460463

464+
You can only create a path join from the last step in a branch. The **Connect path to existing step** option appears only when you click the last **+** icon at the end of a branch path.
465+
461466
To create a path join:
462467

463468
1. Go to the last step in the branch you want to connect.
@@ -466,7 +471,7 @@ To create a path join:
466471
4. Choose a step from another branch to connect to. Segment only shows the available steps you can connect to.
467472
5. The connection appears as a line on the canvas, showing the path join between branches.
468473

469-
![Journey canvas showing the Connect path to existing step option in a dropdown menu. The menu appears when clicking a plus icon at the end of a journey branch, showing flow control options like Delay, Hold until, Data split, and Randomized split, along with the Connect path to existing step option at the top.](../images/path_joins.png)
474+
![Journey canvas showing a Hold Until step with a branch displaying the Connect path to existing step option. The dropdown menu appears when clicking the plus icon at the end of the branch, showing Flow control options (Delay, Hold until, Data split, Randomized split) and Actions (Send to destination). The Connect path to existing step option appears at the top of the menu. The journey shows other branches including a VIP Member branch and an Everyone else branch with destination steps.](../images/path_joins.png)
470475

471476
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.
472477

0 commit comments

Comments
 (0)