This article provides you with information for setting up In-App Push Re-Permission campaigns.
Push Notifications require opt-in on iOS from the customer. The native iOS pop-up will ask users whether they wish to receive Push Notifications. If a customer says no, you cannot contact them via Push Notifications, reducing the potential reach of your marketing campaigns and potentially impacting revenue, loyalty and engagement.
However, In-App messaging requires no permission so can be used to encourage users to opt-in again for Push Notifications. By creating an In-App campaign targeted at those users without a Push Notification opt-in and using the richness of an In-App message to outline the benefits of switching on Push Notifications users can be directed to their settings to turn notifications back on.
iOS requires specific opt-in for Push Notifications, whereas by default customers are opted in to Push Notifications on Android. Whilst we refer to iOS above (because the iOS Native Permission pop-up is typically displayed early in the app lifecycle) this use case will also work for those Android customers who have physically turned their Push Notifications off via their phone settings.
- Increase reach
- Increase engagement
- Increase loyalty
- Emarsys SDK
- In-App messaging
- Deep Link support set-up
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’
It may be worthwhile adding further segmentation criteria to target more effectively. For example, targeting users who have recently downloaded the app and said no to Push Notifications with an In-App asking them to turn back on Push Notifications soon after may be seen as too intrusive. Therefore adding additional criteria or exclusions such as not targeting users who have had the app for less than one week or have had app activity over a period of time will give you most chance of engagement.
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.
Create a Mobile Engage segment where Push Notifications are ‘Disabled’ (as a minimum).
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 the general settings, giving the In-App a name, linking it to the app, selecting Recipient source as ‘Audience’ to target your segment (your Segment will be dynamically updated in this example once per day so as new users disable or enable Push Notifications they will be moved in and out of the segment).
- On the Content Creation page select an In-App template to use as the basis of your message you can select Full Screen, Modal or Multi-Step templates.
Select either a Full Screen or Modal template for this particular use case. Multi-Step templates are typically used in onboarding or other situations where you want to display multiple pages of info to the customer.
- In the Preview pane alter your selected template accordingly to add in the required images, text and button text.
Type your text directly into the message and add images by clicking on the existing image and selecting another from the Media DB
Use the Styles tab to alter elements such as the background colour, button colour and shape
- To decide on what action should occur when the user clicks on the button go to the button editor as shown below
You can then select the action that should occur from the following options;
- Deep Link
- Custom Event
- Open External Event
- Request Push Permission
In this example, we want to direct users to their Settings or Notification Settings so the customer experience is made as seamless as can be in this situation. Therefore select the Deep Link option and fill in the necessary details.
Deep Links are not created in the Emarsys platform or by Emarsys. They are typically created externally (e.g. through 3rd parties such as Appsflyer or Branch) so the Deep Link needs to be created and your developers decide how to handle the link so it directs to the correct area of the users phone. Further information on deep links is shown below. For further info on Deep Links please see Advanced Topic:: Mobile Engage - Deep links for developers (copied)
- The final step is to fill in the details on the Scheduling page shown below..
An In-App message can be triggered by the users starting the App or via a Custom Event.
Custom Events are essentially any action your user may take in your app, such as clicking on a specific product or category, viewing a particular page, clicking on purchase etc
These events have to set-up by your developers. Typically a marketer will decide on what action should be an event, decide on a name and provide to their development team to create these events. We recommend adding as many events during your implementation process as think you may need so the events are there and ready to use for future use cases and your development teams are not constantly being drip fed requests for 1 or 2 events to be created.
You can also decide on how many times a user should see the campaign. It can be once or multiple times up to 8.
In this example we are deciding to display this message a maximum of 3 times with a minimum of 30 days between impressions. This will effectively mean the customer can only be shown this message once per month for 3 months.
- If your setup is complete then click Save and Launch and your In-App campaign will be live.