Journey Events
To enable journey entry and exit events, contact your customer success manager.
Entry and exit events
These events are automatically generated when a user enters or exits a journey.
| Event | Trigger |
|---|---|
journey_map_entry | Generated when a user enters a journey by meeting the entry trigger condition. |
journey_map_exit | Generated when a user exits a journey, regardless of the exit reason. |
Shared parameters
Both events include the following parameters.
| Parameter | Description |
|---|---|
identifier | The user's ID. |
timestamp | The time the event was generated. |
journey_map_id | The ID of the journey. |
node_id | Entry event: The ID of the first node the user entered. Exit event: The ID of the last node the user visited, whether or not they completed the journey. |
Exit-only parameters
The following parameters are included only in journey_map_exit.
| Parameter | Description |
|---|---|
journey_map_split_path_type | The path the user took out of the last node before exiting. The value depends on the node type: • Entry node, Update user attribute, Audience sync, Time delay: Empty. • Channel node: sent, not_sent, delivered, not_delivered, clicked, not_clicked, viewed, not_viewed. • Check condition: matched_path_<number> (for example, matched_path_1) or no_path_matched. • Check reachability: reachable_on or not_reachable. • Experiment node: path_<letter> (for example, path_A). • Webhook (Check response disabled): succeeded or failed. • Webhook (Check response enabled): matched_scenario_<number> (for example, matched_scenario_1), no_scenarios_matched, or failed. If the user's profile was merged into another profile, the value is DROP, regardless of the node type. |
journey_map_split_path_id | The ID of the exit path. Only included when the exit node has multiple paths. |
Updated 3 days ago
Did this page help you?
