1

I have the following Use Case:

  • Journey is triggered from an API Event, It has PUSH Notification messages present.
  • This Event does not have the Device ID which is used to send Push Notification to the Users
  • Device IDs are present but in a separate table(Mobile Push)

The Question is:

If API event is an entry source in the Journey for Push Notification Messages, but Device Id is present in a separate table, what is the best way to achieve the successful run of the Journey with each user receiving those Push Notifications

Improve this question

1 Answer 1

Reset to default
3

As long as the contact in your API event is already tied to a device ID in the Mobile Push channel, journey builder can send the Push Notification message to that contact without needing the Device ID value in the API send.

Normally, when people register in the app and the SDK registers that device into Mobile Push, it involves to the App side so no further action needed if it does properly.

In case, these contacts haven't been added to Mobile Push channel yet, you would need to import them first. You can refer to this article to be aware the best practices for importing contacts into Mobile Push.

Also, in this article Import Contacts into MobilePush, they also give step by step how to manual import contacts.

Improve this answer
1
  • Thanks, I'll go ahead and try this out and approve the answer post successfully achieving the goal!
    – aryashah2k
    Commented Oct 4, 2023 at 14:19

You must log in to answer this question.

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