FAQ: Understanding Data in the MobilePush Detail Extract Report

Q1. Where can I find definitions for each field output in the MobilePush Detail Extract Report?

A. Please refer to the documentation linked below for official definitions. However, to gain a deeper understanding of the data structure, we highly recommend performing a test send and generating the actual report to review the raw output.

Reference: https://help.salesforce.com/s/articleView?id=000395722&type=1

Q2. What are the data types and field lengths for the report columns?

A. Since the report is generated in CSV format, it does not have strict database type definitions; all fields are treated as text. While the standard documentation lists data types and lengths, please consider these as configuration examples for importing the data into a Data Extension.

Note on External Databases: When importing this data into an external database, formats (especially dates) may differ from the source. Strictly following the documented definitions does not guarantee an error-free import. You may need to process or transform the data on the receiving end. We recommend using variable-length data types (such as VARCHAR) with ample buffer size to accommodate potential variations.

Q3. Does changing the report's date range affect the Open data?

A. Yes, open-related information depends on the date range specified when extracting the report.

Consider a scenario where a message is opened several days after it was sent: If the report's date range covers the Send Date but ends before the Open Date, the report will show the message as sent but not opened. If you re-run the report with a wider date range that includes the Open Date, the open event will then be recorded.

Example:

10/1: Notification Sent
10/5: Notification Opened
Report Range 10/1 – 10/7: The open event is retrieved.
Report Range 10/1 – 10/3: The open event is not retrieved.

Q4. What does a blank "Status" field mean?

A. This likely indicates an Inbox Only message download. Please check if the Template column is set to "Inbox".

For "Inbox Only" messages, no push notification is sent, so the Status field remains blank. Additionally, records for Inbox Only messages are only generated when the message is downloaded by the app. If the message is never downloaded, no record appears in the report. Therefore, this report cannot be used to determine the total number of target devices for Inbox Only sends.

Important Exceptions: There are two cases where "Inbox" messages will generate a non-blank Status:

Inbox Only with "Update iOS Badge" Enabled
- Overview: The message type is Inbox Only, but the [Update iOS Badge] option is set to "Yes".
- Behavior: A "Silent Push" is sent to update the app icon badge. This Silent Push generates a record with a status, regardless of whether the Inbox message was downloaded.
Inbox + Alert
- Overview: The message is configured to send a Push Notification (Alert) alongside the Inbox message.
- Behavior: Since a standard push notification is sent, a record is generated with the push result status, regardless of whether the Inbox message was downloaded.

Interpreting "Failed" Status in these cases: If the Status is "Failed" in the scenarios above, it indicates the failure of the accompanying Silent Push or Push Notification (Alert). It does not reflect the availability or download status of the Inbox message content itself.

Q5. Why is Status sometimes blank even for "Inbox + Alert" sends?

A. This occurs if the device has opted out of Push Notifications. In this case, the Push Alert is suppressed (not sent), and the device only downloads the Inbox message. Consequently, the behavior matches the "Inbox Only" scenario, resulting in a blank Status.

Q6. The DateTimeSend field seems different from the Send Job start time.

A. This discrepancy can occur with Inbox messages. Please refer to the article below for details.

Reference: https://help.salesforce.com/s/articleView?id=004269023&type=1

Q7. Does this report provide data on In-App Message impressions/displays?

A. No, this information is not recorded in this report.

Records in this report where the Template is output as "In-App" represent the sending log of a "Silent Push Notification" used to notify the device that an In-App Message has been updated. This does not represent user engagement data such as the message "display" or "button clicks."

Please note that, as of this writing, there is no standard report type available that outputs display or click logs for In-App Messages on an individual device level.

Additionally, please be aware of the following points when interpreting data related to these silent pushes:

When Status is "Failed": This indicates that the request to send the "Silent Push Notification" failed. It is not directly related to whether the In-App Message itself can be successfully displayed on the device.
When the record count does not match the target audience size (higher or lower): Like standard push notifications, silent push notifications are sent only to "opted-in devices." Therefore, the count will often not match the total number of contacts passing through Journey Builder. Devices that are opted-out do not receive the silent push, but they will download the message by communicating with Marketing Cloud Engagement when the app is launched (or brought to the foreground). Consequently, the absence of a record in this report does not prevent the In-App Message from being displayed.
Regarding "Open" records: Since silent push notifications are not visible to the user, the concept of an "Open" does not exist. Therefore, it is not an issue if the Open count is zero in this report (this is the expected behavior).

Q8. Is there a way to check Device IDs for testing without using Contact Builder?

A. Exporting a MobilePush Filtered List is a relatively easy alternative. The CSV file obtained from exporting a Filtered List contains various device attributes. You can create a list filtered by your test user's Contact Key, export it, and then locate the specific Device ID based on attributes like device model or name.

Reference: https://help.salesforce.com/s/articleView?id=mktg.mc_mp_export_contacts_standard.htm&type=5