Create Unique Journey Results using Transaction Keys
Transaction keys allow your journeys to produce unique results for all entry and multi-criteria decision filters. The transaction key value is combined with the contact key to create a unique identifier that is automatically applied to the entry filter and multi-criteria decision filters used throughout a journey.
- Add a transaction key to the custom event’s config.json under
metaData
. - Map the transaction key value to a contact attribute using the
from
andto
properties. - Enter the from event property, which comes from the event schema and is case sensitive. Only provide the property that you want to match, not the fully qualified string. For example, if
FirstName
is a valid event property, useFirstName
for the from property, notEvent.EventID.FirstName
. - Enter valid data extension values from the same MID in order to enable the Next button when defining the entry filter criteria in Journey Builder.