Minimum Delay between Push Notifications

Overview

 

WARNING

Minimum Delay settings are not applied on push notifications sent using MoEngage Transaction Push API.

Marketers on MoEngage create multiple campaigns in a day, spaced by 5-10 mins. As much as marketers try to create a campaign that has non-overlapping segments, they cannot ensure that there are zero overlaps. Because of this, end-users receive more than 1 notification within 5-10 mins which deteriorates their app experience.

To improve this notification delivery experience, marketers can ensure that two or more notifications are not delivered in quick succession to any device using this setting.

Marketers can configure a delay between two notifications delivered to a device of the end-user from any of these campaign types such as One Time Push, Event-Triggered Push, Location Triggered Push, Device Triggered Push (Online/Offline Mode),  and Push sent using Flows.

Examples

If the marketers want end users to not receive two notifications within 30 minutes, they would need to set the Minimum Delay between two notifications as 30 minutes.

Example 1

If a user's device is eligible to receive notification N1 (sent using One Time or Periodic Push campaign C1) at time 1:00 pm UTC and N2 (sent using One Time or Periodic Push campaign C2)  at 1:15 pm UTC. If the Min Delay setting is OFF, the user device will receive a campaign as per their Frequency Capping status. If the Minimum Delay setting is ON (and set as 30 mins), the user device will not receive N2.

Example 2

If a user's device is eligible to receive notification N1 (sent using One Time or Periodic Push campaign C1) at time 1:00 pm UTC and N2 (sent using Event-Triggered campaign C2) at 1:15 pm UTC. If the Min Delay setting is OFF, the user device will receive a campaign as per their Frequency Capping status. If the Minimum Delay setting is ON (and set as 30 mins), the user device will not receive N2.

FAQs

Q. But there might be specific campaigns that must be sent urgently even if they are spaced closely?

Ans. MoEngage provides a capability to skip this setting on the campaign level i.e. marketers should be able to create a campaign that may not abide by these settings of Minimum Delay. You can find it in Advanced Setting (for One Time, Periodic, Event-Triggered, and Location-Triggered push) OR campaign Delivery Control (for Device Triggered push)

Q. Given that FC is evaluated on the user level and then minimum delay settings are applied on devices, will there be cases where users will not receive the notifications because of minimum delay but their FC will still be incremented?

Ans. Yes. Say your FC is 2 notifications in 1 day. Your user is eligible for campaign C1 and received it. FC bucket is incremented to 1. Now, within 15 mins, the user becomes eligible for campaign C2, which is not sent because of the Minimum Delay setting. FC bucket will be incremented to 2. Not if you try to send another campaign on the same day, it will not be delivered to the user since the FC bucket is already 2.

Q. Does it impact the campaign sending time? If there are 10 campaigns scheduled at 8 am - any difference in execution time with and without this feature enabled?

Ans. MoEngage works on a large scalable infrastructure. So even if these operations will take time to the tune of milliseconds, the campaign send time will not increase substantially.

Q If there are multiple campaigns scheduled at the same time and all of them get picked up at once, will the minimum delay setting continue to work? For example, if my device gets picked up in 2 different campaigns at close intervals like 10:00:05 & 10:00:08, will my device receive two notifications?

Ans. Even if they get picked at the same time, only one would go through as our data store, as well as operations performed, are atomic in nature. So the device will receive only 1 notification.

Was this article helpful?
2 out of 3 found this helpful