Best practices to Import Contacts into MobilePush

Import MobilePush Contacts

• The best practice is to use the SDK to add Contacts into MobilePush on a regular basis, as this ensures the latest information is populated.
• You would use Imports if there are existing mobile applications, or need to import existing push subscriber data information. 
• Import Activities 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 should then be able to use this Import definition in Automation Studio.

Requires Subscriber Key and Sendable DE

• The Import doesn't allow Users to set the opt-out status of a device. However, you can change the Marketer Status by mapping to the "_Status" field (either Active or Inactive). This is an override. 
• All records imported will be treated as opted-in.
• To avoid recording opt-ins incorrectly, pre-filter any opt-outs via a Query before running the Import MobilePush Contacts activity. 

Considerations for using Import Activity

Note: We recommend that you use the SDK to opt in subscribers because 2 of the required 4 fields (DeviceID and SystemToken) are difficult to get correctly (the others are Contact Key and Platform). 

• Where possible, allow the SDK integration to register devices and update Attributes vs. Imports
• When updating existing Contact records via an Import beware of data mismatches. 
• Data needs to 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 would result in the record having an incorrect system Token and will be not be sendable and causes many issues. 
• Device data used as the basis for imports should be pulled from MobilePush via a query + extract to ensure information is correct. 

• Manage Standard Lists
• iOS Device and Contact Registration
• Android Device and Contact Registration