---
schema_version: "1"
id: 8f3fe4d3902b4195d5477400fbb929e02e239566be8117cc7b10889bd8f5a79e
title: Key Push Data Model Objects for Unified Reporting
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mke_unified_reporting_key_dmo_fields_push.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mke_unified_reporting_key_dmo_fields_push.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 7c0a5df64f928ebb539e7bcf14836c7f7ee0cffb95d0c86299c95eeaba23093f
description: 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.
products:
  - Marketing
  - Marketing Cloud Engagement
release: "264"
---
# 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

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Marketing Cloud Engagement <strong>Pro+</strong>, <strong>Corporate+</strong>, and <strong>Enterprise+</strong> Editions</td></tr></tbody></table>

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.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d22797e108">Field Label</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d22797e111">Description</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Field Label" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e108 "><strong>Campaign ID</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e111 ">The ID of the campaign in <span>Marketing Cloud Next</span> that sent the bulk send. This
              ID isn’t the same as a campaign ID from <span>Marketing Cloud Engagement</span>.</td>

          </tr>
          <tr class="">
            <td data-label="Field Label" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e108 "><strong>Data Source ID</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e111 ">The ID of the <span>Marketing Cloud Engagement</span> enterprise ID (EID) that the data came
              from.</td>

          </tr>
          <tr class="">
            <td data-label="Field Label" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e108 "><strong>Data Source Object ID</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e111 ">The ID of the <span>Engagement</span> data stream that the data came from.</td>

          </tr>
          <tr class="">
            <td data-label="Field Label" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e108 "><strong>Engagement Channel ID</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e111 ">The messaging channel of the message. For push messages, the value of this field is
              <code>PUSH NOTIFICATION</code>.
            </td>

          </tr>
          <tr class="">
            <td data-label="Field Label" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e108 "><strong>ID</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e111 ">
              <p>The job ID of the send.</p>
              <p style="margin-bottom:0;">For journey sends, this value contains the ID of the journey activity that sent the
                message.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field Label" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e108 "><strong>Name</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e111 ">
              <p>The name of the send definition used to send the push message. </p>
              <p style="margin-bottom:0;">For journey sends, this value contains the name of the journey activity that sent the
                message.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field Label" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e108 "><strong>Send Method Type</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e111 ">
              <p>The mechanism used to send the push message. Possible values are:</p>
              <ul>
                <li><code>API Triggered</code></li>

                <li><code>Automation Studio</code></li>

                <li><code>Journey</code></li>

                <li><code>User Initiated</code></li>

              </ul>
            </td>

          </tr>
        </tbody>
      </table>

## 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.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d22797e265">Field Label</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d22797e268">Description</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Field Label" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e265 "><strong>Data Source</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e268 ">A reference ID for the source of records identified by an external record ID.</td>

          </tr>
          <tr class="">
            <td data-label="Field Label" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e265 "><strong>Data Source Object</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e268 ">The ID of the data source that the object came from.</td>

          </tr>
          <tr class="">
            <td data-label="Field Label" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e265 "><strong>Id</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e268 ">The message ID in <span>Engagement</span>. This ID is different from the asset
              ID.</td>

          </tr>
          <tr class="">
            <td data-label="Field Label" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e265 "><strong>Name</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e268 ">
              <p>For Mobile Studio, API Triggered, and Automation Studio sends, this field contains the
                name of the send definition.</p>
              <p style="margin-bottom:0;">For journey and transactional sends, this field contains the name of the asset in Content
                Builder.</p>
            </td>

          </tr>
        </tbody>
      </table>

## 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.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d22797e351">Field</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d22797e354">Description</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e351 "><strong>Bulk Message ID</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e354 ">A job ID for the send. Use this field to join to the BulkMessage DMO.</td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e351 "><strong>Device ID</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e354 ">The unique device ID associated with the app user’s device.</td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e351 "><strong>Device Locale ID</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e354 ">The locale that applies to the app user’s device.</td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e351 "><strong>Device Model Name</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e354 ">The model name of the app user’s device, such as <code>Google Pixel
        7</code>.</td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e351 "><strong>Data Source Object ID</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e354 ">The ID of the data source object that produced the send.</td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e351 "><strong>Engagement Action Reason Text</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e354 ">
              <p>A description of the reason that an error occurred. </p>
              <p style="margin-bottom:0;">Available for
                <code>NOT_SENT</code> and <code>BOUNCE</code> events only.
              </p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e351 "><strong>Engagement Channel Action</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e354 ">
              <p>The type of engagement event that occurred. Possible values are:</p>
              <ul>
                <li><code>APP OPEN</code>—An app session occured. The event is logged when the session
                  is complete and the app is closed or moved to the background.</li>

                <li><code>BOUNCE</code>—The push notification service, such as Firebase Cloud Messaging
                  (FCM) or Apple Push Notification service (APNs), rejected the message.</li>

                <li><code>DELIVERED</code>—The message was successfully delivered to the push
                  notification service.</li>

                <li><code>ENTERED</code>—The device entered a geofence.</li>

                <li><code>EXITED</code>—The device exited a geofence.</li>

                <li><code>OPEN</code>—The user opened the notification.</li>

                <li><code>SEND_STATUS</code>—The message was sent and the resulting status is
                  available.</li>

              </ul>
              <p>If your account used <span>Data 360</span> with the <span>Marketing Cloud Engagement</span> channel bundles before the Winter ’26 release, the possible values for this field
                are:</p>
              <ul>
                <li><code>Geofence Entry</code>—The device entered a geofence.</li>

                <li><code>Geofence Exit</code>—The device exited a geofence.</li>

                <li><code>Open</code>—The user opened the notification.</li>

                <li><code>Send</code>—The message was sent and the resulting status is available.</li>

                <li><code>Undelivered</code>—The push notification service rejected the message.</li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e351 "><strong>Engagement Channel ID</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e354 ">
              <p>The type of engagement channel. For mobile app messaging, the value of this field is
                <code>MOBILE APP MESSAGING</code>.
              </p>
              <p style="margin-bottom:0;">If your account used <span>Data 360</span> with the <span>Marketing Cloud Engagement</span>channel bundles before the Winter ’26 release, the possible value for this field is
                <code>Push</code>.
              </p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e351 "><strong>Engagement Channel Type ID</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e354 ">
              <p>The type of mobile app message that you sent or the type of event that occurred. Possible
                values:</p>
              <ul>
                <li><code>PUSH NOTIFICATION</code>—Indicates that a push notification message was
                  sent.</li>

                <li><code>GEOFENCE</code>—Indicates that a user entered or exited a geofence
                  location.</li>

              </ul>
              <p>If your account used <span>Data 360</span> with the <span>Marketing Cloud Engagement</span> channel bundles before the Winter ’26 release, the possible values for this field
                are:</p>
              <ul>
                <li><code>Notification</code></li>

                <li><code>Geofence Entry</code></li>

                <li><code>Geofence Exit</code></li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e351 "><strong>Engagement Date Time</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e354 ">The date and time when the engagement event occurred.</td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e351 "><strong>Engagement Event Direction ID</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e354 ">
              <p>Indicates where the event originated. Possible values:</p>
              <ul>
                <li><code>Inbound</code>—The message was sent from a customer to your brand.</li>

                <li><code>Outbound</code>—The message was sent from your brand to a customer.</li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e351 "><strong>Geofence Name</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e354 ">The name of the geofence that the device was in during the engagement event.</td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e351 "><strong>ID</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e354 ">The unique ID of the engagement event.</td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e351 "><strong>Individual ID</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e354 ">The ID of the unified individual that the message was sent to.</td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e351 "><strong>Internal Organization ID</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e354 ">The ID of the business unit or other internal organization that owns the business
              account. This ID can also refer to an <span>Engagement</span> member ID (MID).</td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e351 "><strong>Marketing Journey Activity ID</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e354 ">The ID of the journey activity that sent the message. Use this value to join to
              Journey Builder DMOs.</td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e351 "><strong>Message Recipient Send Status</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e354 ">
              <p>The status of an attempt to deliver a message. Possible values:</p>
              <ul>
                <li><code>NOT_SENT</code>—The message wasn’t sent to the push notification
                  service.</li>

                <li><code>SENT</code>—The message was successfully sent to the push notification
                  service.</li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e351 "><strong>Mobile App Version</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e354 ">The version of your mobile app on the user’s device.</td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e351 "><strong>OS Name</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e354 ">The name of the operating system on the app user’s device. Possible values are
              <code>iOS</code> and <code>Android</code>.
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e351 "><strong>OS Version Number</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e354 ">The version number of the operating system on the app user’s device.</td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e351 "><strong>RecipientMessageId</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e354 ">
              <p style="margin-bottom:0;">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.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e351 "><strong>SDK Version Nbr</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e354 ">The version of the Mobile App Messaging or MobilePush SDK running on the app user’s
              device.</td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e351 "><strong>Software Application Name</strong></td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d22797e354 ">The name of the app associated with the event.</td>

          </tr>
        </tbody>
      </table>