2

After registering a push device in the All Contact List, a random GUID is assigned to the contact created for the device. And when a ContactKey is assigned to that Device ID, it gets assigned to a new contact with a different Contact ID in the contact model.

What happens next is that the Device ID is erased from the first Contact (with the random GUID) and given to the new contact. So if you're already using the GUID contact in a journey to send Push messages, if a ContactKey registration is forced on his device, the user stops recieving push notifications from that said journey.

Is there any workarround to that issue by forcing push notification sends in journey builder to a specific device or a procedure to allow users to continue recieving the notifications ?

8
  • 1
    Is there a reason you would target the random GUID contact key as opposed to the device? – Bill Mote Mar 3 '20 at 17:15
  • 2
    Take into account that new SDK allows you to delay registration until contact key is set, see:salesforce-marketingcloud.github.io/JB4A-SDK-Android/…. I would mark this flag in your case – SebOB Mar 3 '20 at 17:20
  • Yeah, I see this as A) Unnecessarily doubling your incoming Contacts ($$$) and B) Unnecessarily complicating your device to contact relationships. I would instead look at your approach to registering and adding your device/contacts as both BillMote and SebOB stated above. – Gortonington Mar 3 '20 at 17:56
  • In our case, random GUID contacts are anonymous contacts (just regular app users), and the contactKey registration in the SDK is triggered when they log into the app with their account, and it's at that moment that we can retrieve their contactkey and assign the device to the known contact. So in our use case we need to target both types of contactKeys – Zak Ben Mar 4 '20 at 9:18
  • I'm just not sure why you would target the randomly generated GUID. If you're sending to anonymous contacts then you could simply create an audience list based off the value (or lack thereof) of a tag or attribute that you set when the consumer logs in. – Bill Mote Mar 4 '20 at 12:49

Your Answer

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

Browse other questions tagged or ask your own question.