...
To receive push notifications, push tokens are required. If a device doesn’t have a push token, there is no way to send push to it.
Push tokens are a unique anonymous identifier generated by a user’s device and sent to Braze to identify where to send each recipient’s notification.
...
Braze provides a specific segmentation filter,
Push enabled for App,to help identify the users who have enabled push notifications.
| Note |
|---|
To identify the users you can contact, you need to filter for
|
2️⃣ Push Registration by Device
...
| Note |
|---|
If the user does not have both device opted in & app opt in, we should not expect they receive notifications. Please find below more details:
|
...
Name | Description | Devices |
|---|---|---|
Background push notification | Push notifications that are not rendered for the device. Usually used to send packets of information down to the app for background processes and uninstall tracking. A Background-enabled push token is required for background push to be sent. |
|
Regular push notifications | These appear on your user's device with a notification sound and message which slides in or appears in a notification bar or stack. |
|
Silent push notifications | A push notification that does not wake up the device when rendering on the device. Instead, the notification will be stored in the device's notification tray. |
|
HTML Push Notifications | Coded push notifications that don’t follow Braze templates. They allow more customization |
|
Notification IDs & Channel IDs | Notification IDs and Channel IDs allow you to replace or update push notifications already received, but not opened, by the user. |
|
Provisional Push Notifications | Introduced by Apple in iOS 12, provisional authorization automatically occurs on install for iOS apps, allowing brands to send silent notifications without displaying a push prompt to users. When the silent push is sent and viewed in the device's notification tray, users will be given the option to allow or discontinue push notifications.
|
|
Push Stories | Push Stories are immersive messages that take your user through a visual journey in the form of a carousel. These are available for mobile devices only
|
|
Push with Action Buttons | Push with action buttons are messages that allow you to provide options to your users and offer several calls to action.  |
|
Wearable Push | These push notifications allow brands to send messages directly to wearable devices like the Apple Watch. |
|
...
How can we improve push tokens collection?
Prompts
According to the opt-in channels, we can leverage emails and/or in-app messages to educate the guests and prompt them to go to their device setting and activate their notifications. This is a common practice in the industry, see below.
...
If you are sending IAM to IOS users, you can leverage this deep linking path to link directly to the notification center of the phone: app-settings:root=Notifications&path=Burger King
...
Push Primer
User have to opt-in to receive push notifications
To optimize the chances that users will accept to receive push notifications, you can set up a push primer (in-app message explaining why the user should opt-in to notifications).
Push primers are beneficial as they allow us to send the message with:
Optimized design (a/b test copy and visuals)
Best time (avoid overwhelming the guests at the first interaction). It is recommended to do it based on specific user activity (post high engagement moments)
Leverage the button on-click behavior “Request Push Permission” when creating an in-app message for iOS, Android, or Web.
For iOS, push campaigns are relevant as foreground push notifications (such as notifications that wake up the device) are not enabled until a user explicitly opts into iOS' native push prompt.
Guide on how to set up a push primer:https://www.braze.com/docs/user_guide/message_building_by_channel/push/best_practices/push_primer_messages/#step-5-target-users
...