You are here:
Key SMS Data Model Objects for Unified Reporting
In the unified reporting system for Marketing Cloud Next for Engagement, there are three data model objects (DMOs) that contain helpful data for creating reports related to SMS messaging. These DMOs contain information about your send definitions, engagement data, and message content.
Required Editions
| Available in: Marketing Cloud Engagement Pro+, Corporate+, and Enterprise+ Editions |
These DMOs contain information that’s useful for creating reports that focus on SMS sends:
- Bulk Message: Contains metadata about your messages, such as the campaign ID and send method. The data applies to SMS messages that you send from MobileStudio, Automation Studio, and Journey Builder in Marketing Cloud Engagement. It also contains information about API-triggered SMS messages.
- Digital Content: Contains metadata about the SMS send.
- Message Engagement: Contains send and engagement data related to SMS messages.
Bulk Message
The Bulk Message DMO contains metadata related to an SMS send, based on the send definition in Marketing Cloud Engagement.
This table lists the fields in the Bulk Message DMO that you’re likely to use when creating SMS-related reports in the unified reporting system.
| Field Label | Description |
|---|---|
| Campaign ID | The ID of the campaign in Marketing Cloud Next that sent the message. This ID isn’t the same as a campaign ID from Marketing Cloud Engagement. |
| Data Source ID | The Marketing Cloud Engagement enterprise ID (EID) that the data came from. |
| Data Source Object ID | The ID of the Marketing Cloud Engagement data stream that the data came from. |
| Engagement Channel ID | The messaging channel that was used to send the message. For SMS messages, the value
of this field is SMS. |
| ID | The job ID for the SMS send. For journey sends, this value contains the ID of the journey activity that sent the message. |
| Name | The name of the send definition used to send the SMS message. For journey sends, this value contains the name of the journey activity that sent the message. |
| Send Method Type | The mechanism used to send the SMS message. Possible values are:
|
Digital Content
The Digital Content DMO contains information about the content that’s associated with your message sends.
This table lists the fields in the Digital Content DMO that you’re likely to use when you use the unified reporting system to create reports related to SMS messaging.
| Field Label | Description |
|---|---|
| Data Source | A reference ID for the source of records identified by an external record ID. |
| Data Source Object | The ID of the data source that the object came from. |
| Id | The message ID in Marketing Cloud Engagement. This ID is different from the asset ID. |
| Name | The name of the asset in Content Builder. |
Message Engagement
The Message Engagement Data Model Object (DMO) contains information about the sending, delivery, and engagement of SMS messages sent from your account.
This table lists the fields in the Message Engagement DMO that you’re likely to use when you use the unified reporting system to create reports related to SMS messaging. For a complete list of fields, API names, and data types for this DMO, see Data 360 DMO and Mapping Guide: Message Engagement DMO.
| Field | Description |
|---|---|
| Bulk Message ID | A job ID for the SMS send. Use this field to join to BulkMessageDMO. |
| Contact Point ID | A reference ID that’s associated with the recipient’s phone number. |
| Conversation ID | A unique identifier that correlates mobile originated (MO) and mobile terminated (MT) messages as a single conversation. |
| Country ID | An ID associated with the recipient’s country. |
| Data Source ID | The ID of the data source that’s associated with the SMS send. |
| Data Source Object ID | The ID of the data source object that produced the SMS send. |
| Device Type | Indicates whether the recipient viewed the message on a mobile device or on a computer. |
| Engagement Action Reason Text | A description of the reason that an SMS error occurred. |
| Engagement Channel Action | The type of engagement event that occurred. Possible values are:
If your account used Data 360 with the Marketing Cloud Engagement channel bundles before the Winter ’26 release, the possible values for this field are:
|
| Engagement Channel Type ID | A reference ID to the type of engagement channel. For the SMS channel, the value of this
field is |
| Engagement Date Time | The date and time when the engagement event occurred. |
| Engagement Event Direction ID | Indicates where the event originated. Possible values:
|
| ID | The unique ID of the engagement event. |
| Individual ID | The ID of the unified individual that the message was sent to. |
| Internal Organization ID | The ID of the business unit or other internal organization that owns the business account. This ID can also refer to a Marketing Cloud Engagement member ID (MID). |
| Is Test Send | Indicates whether the SMS send was tagged as a test send. Possible values are
If your account used Data 360 with the Marketing Cloud Engagement channel bundles before the Winter ’26 release, this field has a value of
|
| Keyword Text | The keyword associated with the SMS message. |
| Link URL | The shortened link URL that was sent in the message. |
| Marketing Journey Activity ID | The ID of the journey activity that sent the message. Use this value to join to Journey Builder DMOs. |
| Marketing Batch Number | The batch ID for the SMS send. |
| Message Recipient Send Status | Indicates whether the message has been sent. Possible value: If your account used Data 360 with the Marketing Cloud Engagement channel bundles before the Winter ’26 release, the possible value is
|
| Message Segment Number | The number of message parts in a multipart SMS message. The first message part is
0. |
| Message Text | The text in the message body. |
| Messaging Error Code | A status code that indicates the reason for a message not being delivered. This field
is only provided for messages where the value of the Engagement Channel Action ID
field is NOT_SENT or UNDELIVERED. |
| Mobile Messaging Tracking ID | A unique ID that can be used to troubleshoot delivery issues for individual messages. |
| Original URL | The URL included in the message, before rendering AMPScript values. |
| Resolved URL | The actual URL of the link in the message. |
| Sender Code | The short code or long code that was used to send the message. This field isn’t populated for inbound (Mobile Originated or MO) messages. |
| Sender Display Name | The sender name that was used to send the message. |
| Send Time Phone Number | The recipient’s phone number. |
| SMS Communication Class | The type of SMS message that was sent. Possible values:
|
| SMS Standard Status | A code that indicates the status of the SMS message. See Salesforce Developers: SMS Status Codes. |
| SMS Tracking ID | A unique ID for tracking the delivery status of a message. |
| User Agent Text | The user agent of a device that generated a CLICK event. |
