The Four-Key Engagement Grain in SFMC Tracking Views

Why four keys, not one

SFMC tracking views share a common event grain. JobID alone is insufficient — a single job can deploy across multiple lists and batches. Omitting ListID or BatchID produces duplicate rows or dropped matches.

SubscriberID identifies the recipient within that deployment context. Together, the four keys uniquely identify a send event and its downstream opens, clicks, and bounces.

All four keys in every tracking join

• JobID — the send job identifier from _Job
• ListID — the list or publication list used in deployment
• BatchID — the batch within the job run
• SubscriberID — the subscriber record receiving the send

Template join block

Reuse this ON clause pattern for _Click and _Bounce when joining back to _Sent. DataViews.pro Pathfinder generates these joins automatically when you select related tracking views.

FROM _Sent s
INNER JOIN _Open o
  ON s.JobID = o.JobID
  AND s.ListID = o.ListID
  AND s.BatchID = o.BatchID
  AND s.SubscriberID = o.SubscriberID