Push Notifications

The main use cases for Push Notifications are to engage active users, or to re-engage potentially churning users. Omniata provides an easy way to send notifications to your users. Please note that key for running Push Notifications campaigns is a completed and tested Push functionality integration with Omniata. You can find details on this from the guides under Integration.

The push notification campaigns are build in a similar way than any other campaign with an option to A/B test the performance of different types of messages (generic vs. localized) and also engagement of users that receive the push and other that return to the app organically without a notification.

The setup for Push Notification campaigns is very similar to the other campaigns discussed in the previous chapters. The main difference is scheduling. With Omniata, you can schedule push notification to be delivered at the hour when the user installed the app, or to a specific hour defined by users timezone.

In the following exercise we will focus on building a push notification campaign with custom scheduling. We will use pre-defined content, segments and delivery channels to build the campaign.

Exercise - Create a Push Notification Campaign

  1. Navigate to Engagement > Campaigns. Select 'New Campaign', choose ‘Push Campaign’ as the campaign type, and name the campaign as ‘Push Re-engagement’. After that select Next to continue to the next page.

  2. On this we will set up the content to be delivered. Start by clicking 'Add experience'. Select the ‘Push iOS - Example’ as the delivery channel.

  3. Add content to the experience. As we want to compare the impact of push notifications, we need to set control group that does not receive push notifications. To do this we add an empty JSON content that will not be send to the user, but does assign the user to belong to the campaign as a control. For this use the content ‘Push - Control’.

  4. Let’s now add more experiences and content. In the end you should have four experiences with each having an unique content.

  5. Choose the share of users that get assigned to each experience. The default of 25% each is also a good set up as this ensures that all experiences get enough users to make statistical comparisons.

  6. The next step is to add target segment. Assigning a segment is mandatory as this activates the delivery channel. If you wish to send push notification to all users, create a segment that will match the whole user base. In this case we want to target users that have been inactive for the last 7 days, and we don’t want to limit the number of users assigned to campaign.

  7. Next up is scheduling. Select a timeframe of your liking, but typically recommended duration is one month or more, depending on the size of your user base. For testing purposes with very large user base, even a shorter timeframe might work.

  8. You have two options to define the scheduled delivery time. If you do not check the box for ’Refine Content Targeting and Schedule’, the content will be delivered to the segment specified at the hour of app install. If you choose to customize the targeting and scheduling, you have option to define target segment for each content and specific delivery hour per user timezone. Please note that if you assign different segments to content, you can’t get run a proper A/B test as different user segments might not be statistically comparable.

  9. Once you have reviewed the summary page, you can activate the campaign. And no worries, the Training Project does not have real users so no push notifications will send to anyone.

Congratulations, you have created your first push notifications campaign!

NEXT - Content

This article was last updated on September 3, 2015 22:24. If you didn't find your answer here, search for another article or contact our support to get in touch.