Skip to main content

I am trying to build a Data Extension with the Journey History Data from the last 90 days (Contact Key, Journey, Activity, Status, Date Time). 

 

By default, SFMC Journey Builder gives us the last 30 days data on the Journey History Tab, but I also could not find anyway to export it.

 

Does anyone know how to do this?                                                                                                                    

I found some interesting articles showing that this can be accomplished with an API: 

  1. https://sfmarketing.cloud/2019/11/27/get-journey-history-by-filtering-the-definition-id-via-api/ 
  2. https://www.forcetalks.com/blog/saving-journey-history-in-salesforce-marketing-cloud/
  3. https://gortonington.com/journey-history-for-last-30-days-via-api/  

 

As I am still not familiar with AMPScript, SSJS and APIs, I was not able to use any code to build the APIs mentioned in the articles and therefore the final DE.

 

Just to clarify, the granularity that I´m looking for is the one contained in the Journey History Tab, which can NOT be achieved by joining _Journey and _JourneyActivity DataViews.    

 

Can someone shed a light on this?   

This is basically the same question that @valerie nguyen asked on Nov 5, 2020.   

 

Kind Regards, 

Conrado     

 

#Ask An Expert

#AskAMarketingCloudExpert  

#Marketing Cloud  

#Journey Builder  

#Salesforce Marketing Cloud  

#Automation    

4 Antworten
  1. 24. Sept. 2021, 19:53

    You may have to continuously be extracting the data so you can always have the last 90 days available. 

    For exporting the data, the links you provided have code that you could use to extract the data with the API using SSJS. 

     

    So you may have to use Automation Studio to automatically collect the data on a daily basis.

    Create an automation with 2 activities. One activity for an SSJS Script to save the data from the last saved date (using the API) and add it to a DE, and the second activity in SQL to determine the timestamp for the next run.

0/9000