MobilePush | FAQ: Verifying and Extracting Contact Data Synced via the Mobile App (SDK)

You may need to verify user attributes within contact data synchronized to Marketing Cloud Engagement via the MobilePush SDK. Common scenarios include verifying detailed Opt-In/Opt-Out status or retrieving a list of DeviceIDs.

The standard methods for verification and retrieval are as follows.

1. Methods for Verifying and Retrieving SDK Attributes

Verifying a Single Record Navigate to [Contact Builder] > [All Contacts] and click on a specific Contact Key. You can view detailed information on the [Attributes] tab of the individual contact view.

Bulk Retrieval Export a Filtered List. Create a [Filtered List] within [MobilePush] and manually export the list to retrieve a CSV file containing a list of attribute values. Note: This CSV does not include the SystemToken.

2. Frequently Asked Questions (FAQ)

Q. Can I automate the export of a Filtered List?

A. No, this is not possible. The standard feature only supports manual export. This method cannot be used for requirements such as "periodically and automatically retrieving MobilePush Demographic information."

Q. Can I access Filtered List data using SQL?

A. Yes, access is possible for the list of Subscriber Keys (Contact Keys). When a Filtered List is created, a Data Extension with the same name is created in the background. You can retrieve data by executing a query like the following against that Data Extension.

Example:

SELECT Subscriberkey FROM [Name of Filtered List]

Reference: How to store all "Contact Keys" within All Contacts into a Data Extension

Q. Can I retrieve data from system tables such as MobilePush Demographics using SQL?

A. No, this is not possible. MobilePush Demographics, MobilePush Subscriptions, and MobilePush Tags are system-defined data and are not exposed as supported Data Views. Therefore, they cannot be referenced directly from an SQL Query Activity.

Note: While inquiries are often made regarding the _PushAddress data view for automation purposes, this data view is not supported at this time. Please refer to community resources for information regarding its usage.

Q. Why does the exported record count of a Filtered List not match the contact count displayed on the screen?

A. They usually do not match because the counting criteria differ. The contact count on the screen displays the "number of Contacts (people) matching the list criteria," whereas the exported CSV outputs information per "Device (terminal) held by the matching Contacts."

Discrepancies occur in the following scenarios:

• Higher count in CSV: If one Contact holds multiple devices, or re-install your app, the record count increases by the number of devices.

• Lower count in CSV: If many contacts matching the filter conditions do not own a mobile device (are not MobilePush contacts). The screen count includes non-MobilePush contacts (e.g., email-only subscribers or contacts without channel addresses). However, the export only includes device information for "Contacts with MobilePush devices." This typically occurs when broad filter conditions (e.g., "Contact Key is not null") are specified.

Example: For a Contact count of 100 (including 5 MobilePush contacts owning a total of 8 devices):

• Screen display: 100 (Contact count)

• Exported CSV: 8 records (Based on device information)

Thus, the discrepancy is caused by the difference between the "Contact (person)" unit displayed on the screen and the "Device" unit records in the CSV.

Q. Is there a way to bulk export SystemTokens?

A. No, existing features do not support bulk export. Please consider methods such as using a separate database for token management. Alternatively, for devices with send history, the Token information used is recorded in the standard MobilePush Detail Extract Report, so using that report is another option.