The MobilePush Detail Extract Report allows you to garner deeper insight into how your Push messages are performing amongst your subscriber base, allowing you to better understand your customers and reach them where and when it matters most. Below are the columns included on the report along with data type, character length and a brief description of each dimension and measurement.
| Field Name | Description | Data Extension Data Type | Data Extension Character Length |
|---|---|---|---|
| AppName | Name of the mobile app message was sent to; configured in MobilePush Administration | Text | 32 |
| MessageName | Name of the sent message. This field is populated by the name of the Push Activity in Journey Builder. | Text | 100 |
| MessageID | ID number of the sent message | Number | |
| Campaigns | Name of the campaign associated with the sent message | Text | 64 |
| DeviceId | ID of the device that received the message. The Device ID is a unique identifier assigned to a specific mobile device owned by a contact. | Text | 125 |
| DateTimeSend | Date and time that the message was sent | Date | |
| MessageContent | Content of the message. This field shows AMPscript if used. | Text | 4000 |
| MessageOpened | Whether the message was opened on the device corresponding to the Device ID | Text | 13 |
| OpenDate | When the message was opened | Date | |
| TimeInApp | How long the user spent in the app after opening the message. Measured from the time the subscriber opens the app to the time the app goes into the background. | Number | |
| Platform | Operating system of the device | Text | 50 |
| PlatformVersion | Version of the operating system | Text | 50 |
| Status | Status of the send job at the device level. This field tells you whether the job succeeded or failed for the device. Expected values are Success, Failed, and Blank only if there’s no returned data on the send. | Text | 13 |
| ServiceResponse | Lists any errors with the send. | Text | 256 |
| GeofenceName | Names of all geofence locations associated with the message | Text | 4000 |
| Template | Template of the sent message: Outbound, Location Entry, Location Exit, or Beacon, In-app, Inbox | Text | 50 |
| Format | Format of the sent message: Application Alert or Application Alert & Landing Page | Number | |
| PageName | Subject field of the cloud page that is associated with the message | Text | 4000 |
| PushJobId | ID of the job to use when troubleshooting with support | Text | 40 |
| SystemToken | Unique key that is used by Google or Apple to identify the device for sending | Text | 2000 |
| InboxMessageDownloaded | Date and time the message was downloaded | Date | |
| InboxMessageOpened | Date and time inbox message was opened | Date | |
| IosMediaUrl | Text | 4000 | |
| AndroidMediaUrl | Text | 4000 | |
| MediaAlt | Text | 4000 | |
| ContactKey | ID of the contact that owns the device that received the message but not the ID of the device; one contact could have multiple devices. The ContactKey matches the Contacts and Devices ID. The ContactKey indicates the subscriber associated with the device when the message is sent. | Text | 127 |
| RequestId | Marketing Cloud’s unique identifier for every request | Text | 40 |
Note: The exported data itself may be text/csv, but the Data type and the length information provided in the table above can be useful as a reference when you use it as a secondary report source via Data Extention or other tools.
000395722

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.