SendLog

SendLog

Standard corporate SendLog layout for triggered and journey email sends. Composite key: JobID, ListID, BatchID, and SubscriberKey (SubKey).

Schema last reviewed 2026-06-17

Open Interactive Workspace All data views

Opens SendLog in the interactive canvas with SQL Sandbox.

Fields (18)

Field Type Flags Relations Description
JobID Number PK, FK _Job.JobID Email send job identifier from _Job.
ListID Number PK — Audience list ID used for the deployment.
BatchID Number PK — Batch sequence for multi-wave or throttled sends.
SubscriberKey Text(254) PK, FK _Subscribers.SubscriberKey Subscriber key (SubKey) — unique recipient identifier.
SubscriberID Number NULL — Numeric subscriber ID when populated by the send pipeline.
EmailAddress Text(254) NULL — Recipient email at send time.
EventDate Date — — Timestamp the message was accepted for delivery.
Domain Text(128) NULL — Sending domain recorded on the event.
TriggererSendDefinitionObjectID Text(36) FK, NULL _Sent.TriggererSendDefinitionObjectID Triggered Send / Journey email activity object ID.
TriggeredSendCustomerKey Text(36) NULL — Customer key of the triggered send definition.
TriggerSendDefinitionName Text(200) NULL — Friendly name of the triggered send definition.
JourneyName Text(200) FK, NULL _Journey.JourneyName Journey Builder journey name when sent from a journey.
JourneyVersionID Text(36) FK, NULL _Journey.VersionID Journey version GUID for attribution.
EmailName Text(200) NULL — Email asset name from the send job.
EmailSubject Text(500) NULL — Subject line snapshot at send time.
SendClassification Text(200) NULL — Send classification applied to the deployment.
BusinessUnitMID Number NULL — Business unit MID that originated the send.
IsTestSend Boolean — — Whether the row originated from a test send.

Example query

SELECT TOP 100
  JobID, SubscriberKey, SubscriberID, EventDate, EmailAddress, ListID
FROM SendLog
WHERE EventDate >= DATEADD(day, -30, GETDATE())
ORDER BY EventDate DESC

Valid in Query Studio and Automation Studio Query Activities. GROUP BY is only needed for aggregates; ORDER BY is optional but recommended with TOP so rows are meaningful. Narrow date ranges on large tracking views to avoid timeouts.