---
schema_version: "1"
id: 352867c0745ccbfdd87371b5c03e5064de8b56d701b843c21f6a57c63df4a201
title: Best Practices for Importing Contacts into MobilePush
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_mp_import_contacts_best_practices.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_mp_import_contacts_best_practices.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 2f6a9bb778f503986a6dcd0cebb07dc65528c7421cd812a05f3f095adb0012d2
description: Review these tips to import contacts into MobilePush for successful sending.
products:
  - Marketing
  - Marketing Cloud Engagement
release: "264"
---
# Best Practices for Importing Contacts into MobilePush

Review these tips to import contacts into MobilePush for successful sending.

## Importing Contacts

- Use the SDK to add Contacts into MobilePush on a regular basis, as the SDK ensures that the latest information is populated.
- Use Imports if there are existing mobile apps or if you want to import existing push subscriber data information.
- The Import Activities feature in Automation Studio allows you to Import Contacts from File or Data Extension into MobilePush.
    - Create your Mobile List in Mobile Push > Contacts.
    - Create your Import Definition in Contact Builder > Imports.
    - You can then use this Import definition in Automation Studio.

## Subscriber Key and Sendable Data Extensions

- Import doesn't allow users to set the opt-out status of a device. But you can change the Marketer Status by mapping to the \_Status field (either Active or Inactive).
- All records imported are as opted in. To avoid recording opted-out contacts incorrectly, filter them via a Query before running the Import MobilePush Contacts activity.

## Import Activity Considerations

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_mobile_studio-264-0-0-production-enus/26e7f9fa-f44c-489b-9b21-135d26904a29/images/icon_note.png)

Note We recommend that you use the SDK to opt in subscribers.

- When possible, allow the SDK integration to register devices and update Attributes versus Imports.
- When you update existing Contact records via an Import, check for data mismatches. Data must be aligned with what's current in Contacts.
    - Current Record is SubscriberKey = 1, DeviceID = 1, System Token = 2 / Import Record is SubscriberKey = 1, DeviceID = 1, System Token = 1.
    - This action results in an incorrect system token in the record and isn’t sendable.
- To ensure that contact data is correct, device data used as the basis for imports must be pulled from MobilePush via a query and extract.