This article provides you with information for setting up Push pre-permission campaign.
When installing an app, for Android, push notifications are enabled by default but this is not the case for iOS devices. To influence contacts to enable push notifications on iOS, or to get Android users to re-enable push notifications, In-App messages can be a powerful tool as it does not require a push token. With only approximately 43% of people accepting Push Notifications on iOS this is a critical first step in the journey. The guide below is to suggest a campaign to get contacts to enable push notifications.
- Increase reach
- Drive loyalty
- Emarsys SDK
- In-App messaging
- Custom events
High level use case flow
Create the necessary mobile segment:
- Segment should be linked to the correct app.
- Add a condition for Push Notifications is ‘Disabled’.
- Add a condition for App Installation Date was in the past 24 hours.
Create the In-App message:
- Link to the correct app.
- Link to the correct segment.
- Choose the template and design the In-App.
- Decide on how the In-App should be triggered (App open or Custom Event).
- Decide on how often a customer can see the In-App.
- Decide on launch date and time.
Push/In-App campaign creation
- From the Mobile Engage In-App tab, click Create In-app Message to begin creating the In-App message
- Fill in general settings, giving the In-App message a name, linking it to the app, selecting Recipient source as Audience and the choosing the relevant segment created previously.
- Choose the relevant In-App template and customise the message text. The template chosen should have 2 action buttons, one to close and the other will be for accepting push messages.
Keep the message concise and with a friendly tone. If you are going to send offers via Push, it's a valuable motivator for the contact to accept push notifications. An example would be "Stay up to date? - We'd love to keep you up to date with important news and offers"
- Click on the Styles icon on the left navigation panel to configure the style of the In-App message to match your brand, including the background and button colours.
When choosing the button colours, please note that the colours can have an impact on the likelihood of the contact clicking the buttons. For example, red or grey buttons are less appealing to be clicked than green.
- Click on the left action button and select the Button Editor icon.
- Select Button Type of "Closed" and click Confirm.
- Repeat steps 5 and 6 for the right action button but this time for the Button type select Request Push Permission. When doing so, also confirm the reporting display name to be used in the reporting.
In this section, define when the contact is to receive the In-App message. As the segmentation will stop the message going to contacts who have already accepted Push notifications, it is only required to define the schedule for those who haven't accepted Push notifications.
For the campaign trigger, it is suggested to do this off a custom event rather than app start, as triggering this type of campaign off app start is not recommended practice. Please note that the custom event name needs to be exactly as stated in the app.
On the section "How often should the recipients see this campaign" - A suggested setting is to show the In-App message no more than 4 times with a 7-day minimum gap between impressions.