Similar to this thread except we have used Salesforce Contact Id: Mobile Push SDK Functionality

We are implementing MobilePush some time after the initial implementation of Sales Cloud and Marketing Cloud and used the Salesforce Contact Id as the Contact Key. Everything has been working fine inc. journeys and email history flowing back in Sales Cloud using Marketing Cloud Connect.

Now we have the issue presented that our app doesn't have a reference to the Salesforce Contact Id so device registration will create duplicate contacts in Marketing Cloud for known customers in Sales Cloud.

What do others do in this situation? We can still be functional this way but ideally removing the duplicates and updating the MobilePush data views to use the Salesforce Contact Id would be best.

2 Answers 2


As of 20190411 each cloud that registers a contact will have a copy of the contact.


One way to do this may be for each cloud to store a customer-specific attribute (your customer's username?) in the contact record. In MobilePush SDK, that can be accomplished by setAttribute:().

Then, it may be possible to process the data on the server in a way which can make the association between the two records via that "secondary key".

Or, at the very least, if you have a system which references Salesforce contacts (in Sales or Marketing Clouds) you could leverage the secondary key to tie identities together.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .