Journey Node Unique ID

🚧

Journey Node Unique ID is an advanced feature. Please reach out to your account manager to have it turned on in your account.

Definition

For content used in Journeys, an additional piece of Simon-populated content is made available per contact: contact_journey_node_unique_id. This field contains a monotonically increasing counter with a unique value for each contact at that node in the triggering Journey. While other Contact Properties rely on the Customer Data Pipe to update, the contact_journey_node_unique_id updates independently whenever a contact advances through the Journey.

Example

Take the following example.

As contacts enter the Journey, they'll get split at the branching node and then routed to the sending nodes below. Whenever a contact enters a new node, they'll be assigned a contact_journey_node_unique_id for that node. For example, the first contact to enter the HIGH SPENDERS sending node will be assigned 1, the second 2, the third 3, etc. for that node. Similarly, the first contact to enter the LOW SPENDERS sending node will be assigned 1, the second 2, the third 3, etc. for that node.

Details

Note that each node's counter is unique from every other, and each contact only has one contact_journey_node_unique_id. It's value for a given contact will represent the value of the node they're currently in. As a result, when a contact leaves the HIGH SPENDERS node, waits in the delay node, and then enters the HIGH SPENDERS FOLLOW UP sending node, their contact_journey_node_unique_id will be updated to the HIGH SPENDERS FOLLOW UP node.

How to use it

You can leverage this functionality in any custom context, Content Block, or Template in Jinja:

{{ simon.contact_journey_node_unique_id }}

As with anything else in Jinja, this value (a string) can be leveraged in an if statement, for loop, concatenated with other values, assigned to a variable, etc.

❗️

The Journey Node Unique ID for a contact is only populated for content used in Journeys.