Data View: SMSMessageTracking

To view your message send and receive history from MobileConnect SMS sends, query the _SMSMessageTracking data view. Information from this query relates to the owner of a private short code or long code. Query information can also relate to a client by using a shared short code to which the subscriber has opted in.

Identify the name of the SMS message that you want to check on the MobileConnect Overview page.

1. To retrieve the MessageID, click the message name.

2. On the message Overview page, note the URL.

3. Copy the Base64 encoded text.

4. Use an online Base64 decoder to decode the Base64 encoded text. The format of an encoded message is {val}:{val}:{val}. The first value is the MessageID. For example, if the result is 65:78:0, the MessageID is 65.

Example
Example

Sample URL: https://mc.s10.exacttarget.com/cloud/#app/MobileConnect/Mobile/%23!/message/view/NjU6Nzg6MA

Sample Base64 encoded text: NjU6Nzg6MA

Considerations

  • Dates and times are stored in Central Standard Time. Daylight Savings Time isn’t observed.
  • Code and keyword values are currently represented as a static GUID.
  • There are some cases where MobileConnect has no subscriber ID. For example, if a net new number texts STOP, a contact isn’t created, but a record is logged.
  • For shared codes, the delivery statuses shown in this data view only confirms delivery to the aggregator via the status code of 2000. The shared codes delivery receipts are returned to the Marketing Cloud Engagement account that owns the code.
  • Use the _SMSSubscriptionLog data view for Unsub, OptIn, and OptOut data.
  • If you don’t name your activity in Journey Builder, your content name serves as your activity name.
  • This data view retains data indefinitely. To improve query performance and limit the results, use WHERE conditions when retrieving a large amount of data.
  • The JBDefinitionID field corresponds to the VersionID in the Journey Data View.

Columns

Name Description Data Type Data Extension Data Type Nullable
MobileMessageTrackingID Unique ID for tracking information related to the sent message bigint Decimal (19, 0)  
EID Enterprise ID number for the sender bigint Decimal (19, 0) X
MID Member ID bigint Decimal (19, 0) X
Mobile Mobile number for the subscriber varchar(15) Phone  
MessageID Mobile message ID int Number  
MessageTypeID Identifies the type of message for the tracking record. Returns 0 when undefined. int Number  
KeywordID Unique identifier for the keyword unique identifier Text X
CodeID Unique identifier for the SMS code unique identifier Text X
ConversationID Not used (legacy) bigint Decimal(19,0) X
ConversationStateID Unique identifier that correlates mobile originated (MO) and mobile terminated (MT) messages as a single conversation unique identifier Text X
CampaignID The SMS campaign tied to the record int Number X
Sent If the message was sent (1 = true, 0 = false) tinyint Boolean  
Delivered If the message was delivered (1 = true, 0 = false)   Boolean X
Undelivered Whether the message was delivered successfully or not (1 = true, 0 = false) bit Boolean X
Outbound If the message was outgoing (1 = true, 0 = false) bit Boolean X
Inbound If the message was incoming (1 = true, 0 = false) bit Boolean X
CreateDateTime The date and time the tracking record was created smalldatetime Date and time  
ModifiedDateTime The date and time (in Central Standard Time) the tracking record was modified smalldatetime Date and time  
ActionDateTime

The actual date and time a delivery or non-delivery event was received by Marketing Cloud Engagement.

Timestamps for delivery receipts aren’t indicative of when a message was received on a handset. The SMS industry doesn’t support read receipts, and the data returned in this view are based on when a delivery receipt is returned to our system.

smalldatetime Date and Time  
MessageText The text of the message nvarchar(160) Text X
IsTest If the message was a test message bit Boolean  
MobileMessageRecurrenceID The ID of the recurrence schedule for the message. Can be used for troubleshooting send issues. bigint Decimal (19, 0) X
ResponseToMobileMessageTrackingID The tracking ID of the response to the message bigint Decimal (19, 0) X
IsValid If the message is valid bit Boolean X
InvalidationCode Invalidation code for the message smallint Number X
SendID The send ID number for the SMS send bigint Decimal (19, 0) X
SendSplitID If the message was split, the ID of the split bigint Decimal (19, 0) X
SendSegmentID The ID of the segment tied to the message bigint Decimal (19, 0) X
SendJobID The job ID for the SMS send bigint Decimal (19, 0) X
SendGroupID The group ID for the SMS send bigint Decimal (19, 0) X
SendPersonID The sendperson ID for the SMS send bigint Decimal (19, 0) X
SubscriberID The subscriber ID for the affected subscriber. This number represents the unique ID for each subscriber record bigint Decimal (19, 0) X
SubscriberKey The subscriber key for the affected subscriber nvarchar(254) Text X
SMSStandardStatusCodeId SFMC delivery status code int Number X
Description Detailed description of the status code nvarchar Text X
Name The name of your message nvarchar Text X
ShortCode

The short code or long code used to send your message

The ShortCode column isn’t populated for inbound and MT sends. View the associated code in the CodeID column instead.

nvarchar Text X
SharedKeyword The keyword used in your message nvarchar Text X
Ordinal Represents the parts in a multi-part message. Represented in ascending order starting at 0. tinyint Number X
FromName From Name that an individual message was deployed with. Maximum length: 11 characters nvarchar Text X
JBActivityID Unique identifier for the journey activity the message was deployed from unique identifier Text X
JBDefinitionID Unique identifier for the journey a message was deployed from unique identifier Text X
SMSJobID Unique identifier for each SMS job triggered in MobileConnect unique identifier unique identifier X
SMSBatchID Identifies a batch associated with an SMS send bigint Decimal (19, 0) X
SendDateTime The date and time the message was sent to the aggregator. This value is accurate to the second and is displayed in Central Standard Time (CST). datetime2(3) Date and time Yes
DeliveredDateTime

The date and time when Marketing Cloud Engagement received the delivery event. This value is accurate to the second and is displayed in Central Standard Time (CST).

The field gets populated only for successfully delivered messages. It's empty for all other statuses, including carrier-level acknowledgments, failures, or undelivered messages.

datetime2(3) Date and time Yes