I have this very awkward situation with my mobile application developing team.

I have consulted dev team to implement the delay registration method for the app but happened to some miscommunications the team forgot to include that part of the code and now we are having duplication contacts in our Marketing Cloud instance because the subscriber keys we're using on our MC instance do not link to the device and we don't have any downstream data to our backend system.

To be honest, I did some research through every solutions and come up with 2 outcomes.

  1. We need to have out backend team get data from CRM first to backend for app developing team to lookup and update subscriber key for the app again.
  2. (New idea) We keep everything at it is and using API to update subscriber key accordingly device token we send over to MC earlier.

The 2nd idea seems not so realistic to me since I didn't see any documents or posts prefer to the solutions.


You would be better off setting the parameter as desired and just setting the ContactKey from your application. You will end up with some orphaned contacts as this will disassociate the existing contact from the device, but that is a much easier clean up.

|improve this answer|||||
  • This would be the best practice which is opt1 because we have limited resource on that implementing application so opt2 is the fastest way for us. – Tuyến Nov 8 '19 at 14:37

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.