Journey Email Tracking Dataset
Build a reporting dataset that resolves email sends back to Journey and activity context without multiplying raw tracking events.
Evidence tier describes my hands-on relationship with the content. Official sources describe platform contracts/documentation. Production observations should not automatically be treated as official limits.
A reporting-ready Journey/email dataset with explicit grain and safe event aggregation.
Know the reporting grain you need.
Identify whether you need send-level, subscriber-level or event-level rows.
Resolve Journey activity
Use TriggererSendDefinitionObjectID → JourneyActivityObjectID → VersionID.
State the event grain
Do not join raw _Open and _Click event sets without deciding how duplicates should behave.
Pre-aggregate engagement
Reduce event views independently before joining them into the final dataset.
Persist history when needed
Data Views are operational sources, not a universal forever-history store.
Validate against recent sends
Use a bounded recent window and compare counts with Journey/Email tracking UI.
Turn the Recipe into checkable work.
Progress, notes and history stay in this browser.