This data is helpful in that it shows aggregated send data for all Triggered Sends — traditional and Journey Builder ones. A new row is added every time a Triggered Send Definition is published, so it’s also a historical record of publishing events — along with the performance of each “version” of the Triggered Send Definition. The sum of each of the activity counts represents what you would see in Tracking for a particular Triggered Send Definition.
One nice benefit is that the results also contain the number of emails queued to be sent at a specific point in time. So if you retrieve this data hourly (with some additional configuration), you could monitor the sending queue over time.
To get started, create a Data Extension with this schema:
External Key: TriggeredSendSummary
Next, create a Script Activity in Automation Studio like this.
This script does a Describe of a couple of SOAP objects to get the retrievable properties, sets a filter (it’s like a where-clause in SQL), iterates through the TriggeredSendSummary Object results, does a few more related retrieves for specific attribute, and finally upserts the results into the specified data extension. If you don’t want to retrieve all records every time, you can update the filter criteria on line 81 and get more specific. I’ve generally not restricted it, because it’s not that much data to retrieve.
Finally, schedule this to run on an interval appropriate for your needs.
Once you have data, you can toolbar-download it as needed, query it, export it with an Extract Activity, or lookup and display it in an email or CloudPage with AMPscript.