You are here:
Audiences
Use the contact information made available by Contacts in MobilePush to segment and target audiences for your push notifications.
The Contacts feature allows you to view and interact with information about an app user. You can use the contact information made available by Contacts to MobilePush to segment and target audiences for your push notifications.
To send only to contacts who meet certain criteria, create a filtered list or create a data extension in Contact Builder.
Note Shared data extensions aren’t available in MobilePush.
The Contacts feature uses a system table to store information along with an automatically incremented identity column for the primary key. You can also include custom information required to send messages by adding attributes for your contacts. You can’t query or export the information in a system table. The system table contains the following attributes:
| Attribute | Description |
|---|---|
| Application | The ID of the app that the user is associated with. |
| Badge | The number of messages shown in the iOS app badge. |
| Channel | The channels that you can use to send messages to the contact. |
| City | The contact's city of residence. |
| Contact ID | A system-generated unique identifier for the contact. |
| Contact Key | A unique identifier for the contact that is used to link data about the contact across channels. Also known as Subscriber Key. |
| Created Date | The date the contact data was entered into Marketing Cloud Engagement. |
| Device | The mobile device used by the contact. |
| Device ID | A universally unique identifier (UUID) that the SDK generates when the app is installed on a device. This ID is sometimes called the Installation ID. A device ID isn’t considered a persistent unique identifier for the physical device. |
| Device Type | The type of mobile device used by the contact, such as a phone or tablet. |
| First Name | The contact's first or given name. |
| Hardware ID | An identifier for the type of mobile device used by the contact, such as
iPhone7,1. |
| Is Honor DST | Indicates whether the contact lives in a location that follows Daylight Saving Time. |
| Last Name | The contact's last or family name. |
| Location Enabled | Indicates that the contact opted to receive location-based push messages. |
| Modified Date | The last date and time that a person or application modified data for the contact. |
| Platform | The operating system for the contact's device, such as iOS or Android. |
| Platform Version | The version of the operating system used on the contact's mobile device. |
| SDK Version | The version of the MobilePush SDK that your app uses. |
| Source | Indicates how the contact information entered the system, such as Mobile Opt-in or Import |
| State | The contact's state, province, or other subnational unit. |
| Status | Indicates whether the contact currently subscribes to push messages |
| System Token | A unique identifier generated by Apple or Google for the contact's mobile device |
| UTC Offset | The number of hours that the contact's time zone differs from UTC time. |
| Zip Code | The contact's ZIP or postal code. |
| Device Language | The language setting used on the contact's mobile device. |
| GCM Sender ID | A unique identifier for Google Cloud Messaging push message sender for the app |
| Application Version | The version of the app installed on the contact's mobile device. |
| Last Application Open | The most recent time and date the app was opened on the mobile device. |
| Last Message Open | The most recent time and date that a push message was opened on the mobile device. |
| Last Send | The time and date of the most recent push message sent to the contact. |
| Send Count | The total number of push messages sent to the contact. |
| Message Open Count | The total number of push messages opened by the contact. |
- Create a MobilePush Audience
In MobilePush, an audience is a group of contacts that you can send a notification or message to. - Contacts and Devices
The contact key, also known as a subscriber key, is a unique identifier for a contact in MobilePush. Use this value to associate cross-channel addresses and subscriptions for a single contact. You can use the same key for a contact across multiple channels, such as email, SMS, and push messaging. - Who Receives Your Push Notification
Learn how MobilePush determines which devices to send to. - Manage Filtered Lists
In MobilePush, manage is the first step to editing filters, duplicating a filtered list, etc. - Manage Standard Lists
In MobilePush, add contacts, delete lists, and export contacts. - Previous Version of Contacts
Complete instructions for using the previous version of Contacts in MobilePush. - Upgrade Contacts in MobilePush
Upgrading Contacts in MobilePush provides access to functionality that makes it easier to manage contacts across channels.
Did this article solve your issue?
Let us know so we can improve!
