Segmentation & Personalization: Delivery Window Signal and Night Mode
Our golden rule when it comes to mobile engagement is to always send push notifications with the app user’s benefit in mind. Developers can achieve this in two ways: 1) Personalization, and 2) Perfect Moment of Delivery. OpenBack is currently the only mobile engagement platform on the market that can offer guaranteed real-time reliable delivery for push notifications. This is because our patented hybrid platform processes user data via edge computing… so it all happens on-device. This has many benefits to it, including the fact that this allows us to offer 50+ data signals to customize the timing and context of your notifications. Two of these signals that are important to look at in tandem are the Delivery Window and Night Mode features.
What Is Delivery Window?
Delivery Window is one of our most basic signals. It does exactly what its name sounds like: blocks out a window of time for delivery of notifications. The idea is to figure out a timeslot when your user will be most likely to click on the notification. This may be during their lunch break, from 1 to 2pm. Or it may be after they come home from work in the evenings and are scrolling on their phone in front of the TV, from 7pm to 9pm.
Either way, it’s up to you to determine when this convenient time window might be for your user. And, in most cases, the Delivery Window isn’t specific enough to gauge when your user might be amenable to receiving notifications. Because of this, it should always be combined with at least one other signal.
What Is Night Mode?
Night Mode is a similar feature that blocks out the hours your user is sleeping as an absolute do-not-send window. So, for a user who works a 9-to-5 job, that might mean absolutely no push notifications between 10pm and 8am the next morning. (Except to communicate crucial information… for example, to confirm a change in the take-off time for their 7am flight the next morning.)
When other push notification vendors limit time slots, it’s always done on the server-side. So, you might know the timezone of the device, but that’s not always reflective of true real-time on the device. The big difference with OpenBack is that because we leverage all data directly on the device, we’re using true device time.
Once the window of time assigned to “Night Mode” ends, the notification will be delivered. And it’s configured, so you can change the “no-deliver” period at any time.
So if people are traveling between timezones, for example, with conventional push they will have to open the app before the most accurate time registers on the server. With OpenBack, there is never any disconnect between timezones. The time is always updated in real-time, based on local device time. And once it comes out of night mode, the notification will be delivered.
How Are OpenBack’s Delivery Window and Night Mode Related?
Deployed on its own, the Delivery Window (Time) signal is not very effective. In fact, a study of billions of data points from an OpenBack customer showed that alone the Delivery Window signal results in an 18% decrease in interactions with notifications. Combine with other signals to whittle down your time period to the most appropriate Moment of Delivery.
Combined with our Night Mode feature, the Delivery Window signal enables delivery at both global and app level times. Block off night hours in true real-time to place an embargo on notifications delivering, until Night Mode switches off at a more appropriate time of day.
Ultimately, it’s about respect for a customer’s convenience – something every business should have, and which has seen positive responses from OpenBack customers.
For more insights on how to use OpenBack’s signals to deliver push notifications at the right moment, get in touch with one of our experts.