Journey properties attributes journey-properties
In the simple expression editor, and in the advanced expression editor, below the Event and Data source categories, you can access the Journey Properties category. This category contains technical fields related to the journey for a given profile. This is the information retrieved by the system from live journeys, such as the journey ID, or the specific errors encountered.
It contains information, for example, about:
-
journey version: journey uid, journey version uid, instance uid, etc.
-
errors: data fetch, action execution, etc.
-
current step, last current step, etc.
-
discarded profiles
The list of fields is available in this section.
You can use these fields to build expressions. During the journey execution, the values are retrieved directly from the journey.
Below are a few examples of use cases:
-
Log discarded profiles: you can send all profiles excluded from a message by a capping rule to a third-party system for logging purposes. For this, you set up a path in case of timeout and error and add a condition to filter on a specific error type, for example: “discard people by capping rule”. You can then push the discarded profiles to a third-party system via a custom action.
-
Send alerts in case of errors: you can send a notification to a third-party system every time an error occurs on a message. For this, you set up a path in case of error, add a condition and a custom action. You can send a notification on a Slack channel, for example, with the description of the error encountered.
-
Refine errors in reporting : instead of having just one path for messages in error, you can define a condition per error type. This will allow you to refine the reporting and view all error types data.
List of fields journey-properties-fields
Error type of the latest activity (node) in error. Possible types:
- Events: Events, Reactions, SQ (example: Audience Qualification)
- Flow control: End, Condition, Wait
- Actions: ACS actions, Jump, Custom Action
Error code of the latest activity (node) in error. Possible errors:
- HTTP error codes
- capped
- timedOut
- error (example: default in case of an unexpected error. Should not/extremely rarely happen)