Salesforce Marketing Cloud Journey History
Today, Feature Friday, we're continuing our Journey Builder series with a feature that makes it possible to track the flow of contacts across all activities in a journey — the journey history. In this article, we show what this functionality can do and where its limits lie.
Analyses and research
The journey history is a tabular overview of all activities that have taken place in the journeys of a business unit within the last 30 days. It helps marketers obtain information about the history of individual contacts or journey activities. The journey history contains the following data in each entry:
- Contact Key
- Journey name
- Activity (Email, Wait Step, Decision Split...)
- Status (Complete, Waiting, MetCriteria...)
- timestamp
Using various filters, historical data can be selected in such a way that various questions relevant to marketers can be answered:
- Which journeys has a contact gone through within the last (maximum) 30 days?
- Which contacts were on a specific journey in the last week?
- Which contacts are at which point in a journey?
- Has a specific email activity already been completed for a contact?
Each entry also includes information about the status of the activity. Since this information is not self-explanatory, it is recommended that you read the explanations of the status messages in the documentation Read up.
Visualize individual journey processes
A very helpful feature in connection with Journey History is the Contact Path. With this functionality, you can display the path that a specific contact has traveled there directly in a journey. Based on the data from the journey history, it is possible to check whether a specific contact is in the journey, which path they have traveled there so far and where they have arrived. But that's not all — you can even remove the contact from the journey if necessary.
Journey History: Everything at a glance?
Unfortunately, only data from the last 30 days can be viewed in the journey history, which means restrictions, especially for journeys that run over longer periods of time.
In addition, the current information on “Failed” activities does not provide sufficient information to be able to speak of a real error log with troubleshooting tips.
Anyone who is aware of the two restrictions can certainly use the journey history profitably and gain helpful insights — whether as part of quality assurance or journey optimization. The visual presentation of the journey history for individual contacts based on the contact path and the option to even remove them from journeys is particularly useful.
Here Is it about documenting the journey history.
