Timeline for Job ID for Journey Builder Sends
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 22, 2018 at 21:12 | comment | added | Tom Callahan | This seems like a really bad process for identifying Job IDs | |
| Oct 17, 2016 at 20:52 | comment | added | Eliot Harper | Actually, I almost forgot. While Triggered Send DE's can be used with Triggered Sends, they can't be used with Journey Builder Triggered Sends, so you will need to use a query to select rows in the Job Data View. | |
| Oct 17, 2016 at 11:24 | vote | accept | Pankaj Gupta | ||
| Oct 17, 2016 at 11:22 | comment | added | Eliot Harper | Yes, the Job ID would be in the data view. The advantage of using a Triggered Send DE is that you can see all attributes used in the send and also add your own fields. A Job Data View requires you to write a query and target a DE to get this information. | |
| Oct 17, 2016 at 11:01 | comment | added | Pankaj Gupta | Does that mean the Journey Builder Send has Job ID in Job Data View ? In that case, what would be the use of Triggered Send DE. | |
| Oct 17, 2016 at 10:50 | comment | added | Eliot Harper | It would not be stored in a Data Extension unless you have already created a Triggered Send Data Extension (create a new Data Extension using the Triggered Send template). Alternatively, you can query the job data view to retrieve the job id. | |
| Oct 17, 2016 at 10:42 | comment | added | Pankaj Gupta | Is there a JOB ID for this send stored in any DE? This would be needed in case we need to directly query the DE for email sends. Pls advise. | |
| Oct 17, 2016 at 10:37 | history | answered | Eliot Harper | CC BY-SA 3.0 |