Journey properties attributes journey-properties
In the Simple Expression Editor and the Advanced Expression Editor, the Journey Properties category appears below the Event and Data Source categories. This category contains technical fields related to a journey for a given profile. These fields include information retrieved by the system from live journeys, such as journey IDs or specific errors encountered. You can use this dynamic, system-level data to tailor journey workflows based on real-time conditions.
The category includes the following information:
- Journey Version: Fields such as journey UID, journey version UID, and instance UID provide identifiers and metadata for the current journey version.
- Errors: Error codes related to data fetch or action execution failures enable targeted troubleshooting.
- Current Step: Fields track the current or last step of the journey execution.
- Discarded Profiles: Details about profiles excluded from the journey due to errors or rules.
The complete list of fields is available in this section.
These fields help create expressions that dynamically adapt during journey execution based on real-time data. For example, expressions can respond to errors, track journey performance, or log specific actions based on system feedback.
Examples of use cases
Below are practical examples that demonstrate how to use these fields effectively:
-
Log discarded profiles
To record profiles excluded due to a capping rule when running a campaign, configure a timeout or error path. Add conditions to identify the specific error type (for example, 鈥渄iscard profiles by capping rule鈥) and use a custom action to push these profiles to a third-party logging system. For example, send this data to a database for further analysis. -
Send alerts in case of errors
To ensure prompt responses to errors, set up a notification system. Configure a path that triggers when errors occur, add conditions to specify the error type, and use a custom action to send notifications. For example, send a Slack message with details like 鈥淢essage delivery failed due to timeout.鈥 -
Refine errors in reporting
To avoid grouping all errors together, define a condition for each error type. This granular approach enhances reporting by tracking specific errors such as 鈥淗TTP error codes,鈥 鈥渢imed out,鈥 or 鈥渃apped.鈥 This method helps identify patterns and address issues more effectively.
List of fields journey-properties-fields
Below is a detailed list of fields available in the Journey Properties category. These fields can help create expressions that dynamically adapt to the journey鈥檚 state.