sfmc // MobileConnectPRODUCTION

SMS Tracking by Journey Version

Map Journey-sent SMS tracking records to the Journey version via JBDefinitionID.

sqlsmsmobileconnectjourney

Trust & provenancePRODUCTION

Evidence tierPRODUCTIONOfficial sources1Other sources0Last verified2026-10-05

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.

EvidencePRODUCTION

Difficultyintermediate

Verified2026-10-05

Use when

Troubleshooting an SMS Journey activity.

Building a Journey-level SMS delivery report.

SELECT
    s.MobileMessageTrackingID,
    s.Mobile,
    s.SubscriberKey,
    s.Name AS SMSActivityName,
    s.SMSStandardStatusCodeId,
    s.Description,
    s.SendDateTime,
    s.DeliveredDateTime,
    j.JourneyName,
    j.VersionNumber
FROM _SMSMessageTracking s
INNER JOIN _Journey j
    ON s.JBDefinitionID = j.VersionID
WHERE s.SendDateTime >= DATEADD(day,-7,GETDATE())

Why it works

Salesforce documents _SMSMessageTracking.JBDefinitionID as corresponding to _Journey.VersionID.

Operational notes

For shared codes, status 2000 can confirm delivery only to the aggregator.

SMSMessageTracking is documented as retaining data indefinitely; always constrain large queries.

Sources / verification

Salesforce — SMSMessageTracking ↗

SMS Tracking by Journey Version

Keep following the context.