MobilePush SDK – Contact Key with using Data Cloud(CDP)

MobilePush Demographics holds information sent to the Marketing Cloud by your application. You can also import contacts into MobilePush and you will see the data for the contacts in the table. It is also the table where you will add any custom attributes you wish to pass to the Marketing Cloud.

The SubscriberID on the table is an auto-populated field which populates when a contact record is created; it is not the same thing as ContactKey/SubscriberKey. The ContactKey (SubscriberKey) is a root table value and is not part of MobilePush Demographics since MobilePush Demographics relates back to the root table on ContactID.

When a new contact record is created by your application sending a registration call to the Marketing Cloud it is create on the root table and on MobilePush Demographics.

Here is information for setting the SubscriberKey for iOS: http://salesforce-marketingcloud.github.io/JB4A-SDK-iOS/features/subscriber-key.html

Here is information for setting the SubscriberKey for Android: http://salesforce-marketingcloud.github.io/JB4A-SDK-Android/features/subscriber-key.html

First you need to deactivate the auto-registration, by calling setDelayRegistrationUntilContactKeyIsSet(true) during the app init phase. This will ensure a random ContactKey is not pushed to MC. If you don't you will have dups.

Of course you won't be able to send notifications until an actual key is sent to MC. In your use case you want to call setContactKey from the app with the 18-digits Lead or Contact ID.

You may ask the user in your app onboarding to input an identifying information (a custom userId of yours or an email) which will enable you to send the 18-digitsID back to the app, to finally call setContactKey.