I'm working on a data extraction. I implemented it with a file transfer to my FTP, it's for "Sent" journey feedbacks. My customer would like to have the "journey name" in the generated file. I have just the "TriggeredSendExternalKey" for the moment, the customer really wants the journey name instead.

Thank you in advance, Ilyass

2 Answers 2


Are you using a query to populate the DE that you are then extracting? If so, you can match the TriggererSendDefinitionObjectID on the _Sent data view to the JourneyActivityObjectID on the _JourneyActivity data view. Then you can match VersionID on the _JourneyActivity to VersionID on the _Journey data view, in order to retrieve the JourneyName from the _Journey data view.

Here is an example query that can be tailored to your needs:

from _Sent s
inner join _JourneyActivity ja on ja.JourneyActivityObjectID = s.TriggererSendDefinitionObjectID 
inner join _Journey j on j.VersionID = ja.VersionID 
where s.TriggererSendDefinitionObjectID = 'YOUR_TriggererSendDefinitionObjectID'
  • 1
    I don't use DEs, because the type of extraction that I use is "Tracking extract". So the extraction is done automaticaly without SQL query. Commented Jul 21, 2021 at 15:37

It is still advised to use SQL for such use-case, as @jake314159 suggested already. Here you can find a step-by-step explanation of his suggestion and a bit more on top.

Additionally, there is a similar question has been asked some time ago and there you find a way how to manually map TriggeredSendExternalKey and identify what was the journey used for sending.

There is no special option to add the Journey Name field to the Tracking Extract's file. Maybe the only thing to try is to set some field that you would receive in the file that would include Journey's name, e.g. EmailName field from SendJob would have a naming pattern like - [Journey_Name]_Email_#1. but then you would need to make sure that you are not re-using emails across different journeys.

  • The Tracking Data Extract was a nice feature until new features such as journey builder were added without updating the data extract output to include journey info. If the Sent extract included a TriggererSendDefinitionObjectId that would be a good start to fixing what is missing. If that field name's spelling could be be corrected to say TriggeredSendDefinitionObjectId that would be amazing. Commented Oct 31, 2023 at 16:51

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .