Below are frequently asked questions about Push Notifications:
No. Each Push Notification sent by DailyStory is send individually to each recipient. This is done so each message can be personalized to each recipient.
Yes! Using DailyStory's Personalization tokens and conditions you can add personalized content to your Push Notifications similar to emails and text messages.
Unlike email and text messages, Push Notifications do not provided delivery information.
There may be several reasons why a recipient did not receive your Push Notification:
Yes! If your App is installed on multiple devices, such as an iPhone and and iPad, each of the device ids are registered with DailyStory. When a Push Message is sent, the message is sent to all the devices registered for the Contact.
Enabling DailyStory to send Push Notifications to your App requires registering the device id. This provides DailyStory with a unique identifier (the device id) that identifies the App and the individual. Secondly, Push Notifications are sent by DailyStory using Twilio. Twilio Notify Service integration must be configured. DailyStory can manage and configure this service for you, or you can do it yourself.
Push Notification messages do not provide delivery information. Unlike email and text messages, if you want to know if your recipient receives your Push Notification additional updates to your App are required to tell DailyStory when a message is received.
A device binding is a unique identifier that uniquely identifies your app and the devices the app is installed on. When an App is installed on the device and the end user agrees to receive notifications, a device binding is created. This device binding, or device id, is then sent to DailyStory. When DailyStory sends a Push Notification the device id is used to identify the recipient.
Yes! Create a new Autopilot automation in a campaign and use the When device is registered trigger. This trigger is called whenever a device is registered. It will first check to see if the contact associated with the device is in the campaign (and add them if not) and then run the next step in the automation.
