Salesforce Docs Portal

Key Push Data Model Objects for Unified Reporting

In the unified reporting system for Marketing Cloud Engagement+, there are three data model objects (DMOs) that contain helpful data for creating reports related to push 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 Push messages:

  • Bulk Message: Contains metadata about your messages, such as the campaign ID and send method. The data applies to push messages that you send from Automation Studio and Journey Builder in Marketing Cloud Engagement. It also contains data for API-triggered messages.
  • Digital Content: Contains metadata about the send.
  • Device Application Engagement: Contains send and engagement data related to push messages.

Bulk Message

The Bulk Message DMO contains metadata related to a push 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 you create push-related reports in the unified reporting system.

Field Label Description
Campaign ID The ID of the campaign in Marketing Cloud Next that sent the bulk send. This ID isn’t the same as a campaign ID from Marketing Cloud Engagement.
Data Source ID The ID of the Marketing Cloud Engagement enterprise ID (EID) that the data came from.
Data Source Object ID The ID of the Engagement data stream that the data came from.
Engagement Channel ID The messaging channel of the message. For push messages, the value of this field is PUSH NOTIFICATION.
ID

The job ID of the 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 push 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 push message. Possible values are:

  • API Triggered
  • Automation Studio
  • Journey
  • User Initiated

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 push 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 Engagement. This ID is different from the asset ID.
Name

For Mobile Studio, API Triggered, and Automation Studio sends, this field contains the name of the send definition.

For journey and transactional sends, this field contains the name of the asset in Content Builder.

Device Application Engagement

The Device Application Engagement data model object (DMO) contains information about the sending, delivery, and engagement of mobile app 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 mobile app messaging.

Field Description
Bulk Message ID A job ID for the send. Use this field to join to the BulkMessage DMO.
Device ID The unique device ID associated with the app user’s device.
Device Locale ID The locale that applies to the app user’s device.
Device Model Name The model name of the app user’s device, such as Google Pixel 7.
Data Source Object ID The ID of the data source object that produced the send.
Engagement Action Reason Text

A description of the reason that an error occurred.

Available for NOT_SENT and BOUNCE events only.

Engagement Channel Action

The type of engagement event that occurred. Possible values are:

  • APP OPEN—An app session occured. The event is logged when the session is complete and the app is closed or moved to the background.
  • BOUNCE—The push notification service, such as Firebase Cloud Messaging (FCM) or Apple Push Notification service (APNs), rejected the message.
  • DELIVERED—The message was successfully delivered to the push notification service.
  • ENTERED—The device entered a geofence.
  • EXITED—The device exited a geofence.
  • OPEN—The user opened the notification.
  • SEND_STATUS—The message was sent and the resulting status is available.

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:

  • Geofence Entry—The device entered a geofence.
  • Geofence Exit—The device exited a geofence.
  • Open—The user opened the notification.
  • Send—The message was sent and the resulting status is available.
  • Undelivered—The push notification service rejected the message.
Engagement Channel ID

The type of engagement channel. For mobile app messaging, the value of this field is MOBILE APP MESSAGING.

If your account used Data 360 with the Marketing Cloud Engagementchannel bundles before the Winter ’26 release, the possible value for this field is Push.

Engagement Channel Type ID

The type of mobile app message that you sent or the type of event that occurred. Possible values:

  • PUSH NOTIFICATION—Indicates that a push notification message was sent.
  • GEOFENCE—Indicates that a user entered or exited a geofence location.

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:

  • Notification
  • Geofence Entry
  • Geofence Exit
Engagement Date Time The date and time when the engagement event occurred.
Engagement Event Direction ID

Indicates where the event originated. Possible values:

  • Inbound—The message was sent from a customer to your brand.
  • Outbound—The message was sent from your brand to a customer.
Geofence Name The name of the geofence that the device was in during the engagement event.
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 an Engagement member ID (MID).
Marketing Journey Activity ID The ID of the journey activity that sent the message. Use this value to join to Journey Builder DMOs.
Message Recipient Send Status

The status of an attempt to deliver a message. Possible values:

  • NOT_SENT—The message wasn’t sent to the push notification service.
  • SENT—The message was successfully sent to the push notification service.
Mobile App Version The version of your mobile app on the user’s device.
OS Name The name of the operating system on the app user’s device. Possible values are iOS and Android.
OS Version Number The version number of the operating system on the app user’s device.
RecipientMessageId

The unique ID for each instance of an outbound message. This ID is included only for messages sent from journeys and by using the Transactional API.
SDK Version Nbr The version of the Mobile App Messaging or MobilePush SDK running on the app user’s device.
Software Application Name The name of the app associated with the event.