Journey Events

📘
To enable journey exit and entry 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 was at before exiting. If the user completed the journey, this is the last node they visited.

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 when exiting through the last node. 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: The number identifies which path was matched, for example matched_path_1 or matched_path_2. If no condition was met, the value is no_path_matched.
• Check reachability: reachable_on or not_reachable.
• Experiment node: The letter identifies which path the user was allocated to, for example path_A or path_B.
• Webhook (Check response disabled): succeeded or failed.
• Webhook (Check response enabled): The number identifies which response scenario matched, for example matched_scenario_1 or matched_scenario_2. If no scenario matched, the value is no_scenarios_matched. If the webhook request failed, the value is failed.

journey_map_split_path_id The ID of the exit path. Only included when the exit node has multiple paths.

Parameter	Description
`journey_map_split_path_type`	The path the user took when exiting through the last node. 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: The number identifies which path was matched, for example `matched_path_1` or `matched_path_2`. If no condition was met, the value is `no_path_matched`. • Check reachability: `reachable_on` or `not_reachable`. • Experiment node: The letter identifies which path the user was allocated to, for example `path_A` or `path_B`. • Webhook (Check response disabled): `succeeded` or `failed`. • Webhook (Check response enabled): The number identifies which response scenario matched, for example `matched_scenario_1` or `matched_scenario_2`. If no scenario matched, the value is `no_scenarios_matched`. If the webhook request failed, the value is `failed`.
`journey_map_split_path_id`	The ID of the exit path. Only included when the exit node has multiple paths.