1

We've tried to send a message to a specific device, which we can specify via the device's system token on journey's decision split.

But the result was that it's sent to all devices the contact owns.

Was there any case that you've set the push messages to be sent only to a specific device?

Improve this question
6
  • What's the use case? Do you anticipate that a lot of your users will have multiple devices? Also, when creating a list manually there's a de-duplicate checkbox. See if that's available for you.
    – Bill Mote
    Feb 14 at 12:27
  • @BillMote, will that de-duplicate checkbox only select one device? If so which one?
    – Stijn Hoste
    Feb 14 at 13:05
  • I knew you would ignore my questions. What's the use case? Do you anticipate that a lot of your users will have multiple devices?
    – Bill Mote
    Feb 14 at 13:15
  • Hello @BillMote. First of all, Yes, we anticipate that most of the users will have multiple devices regardless of device types (iOS/Android). Also, What we are trying to do is to send only to the device that has the most recent 'last login date' field, which we've set as a custom attribute. As far as I've tested, I guess push messages are basically sent based on the contact information rather than device information, no matter what we set as a pre-condition...
    – Lilyn
    Feb 14 at 23:19
  • 2
    Journey Builder MobilePush activities send on the Contact level. Even if you do a lookup based on the device token, it will still always use ContactKey to make the send. The only way to make a single device send would be to use the messageContact route and supply device tokens there. developer.salesforce.com/docs/marketing/marketing-cloud/guide/…
    – jzehner
    Feb 15 at 17:31

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .