Minimum Delay between Push Notifications is currently enabled only for limited customers. Please reach out to email@example.com to try it out.
Minimum Delay settings are not applied on push notifications sent via MoEngage's Transaction Push API.
Marketers on MoEngage create multiple campaigns in a day, spaced by 5-10 mins. As much as marketers try to create the campaign which have non-overlapping segments, they cannot ensure that there is zero overlap. Because of this, end users receive more than 1 notification with-in a span of 5-10 mins which deteriorates their app experience.
To improve this notification delivery experience, using this setting, marketers can ensure that two or more notifications are not delivered in quick succession to any device.
Marketers can configure a delay between two notifications delivered to an end user's device from any of these campaign types viz. General Push, Smart Trigger Push, Geo Fence Push, Real Time Trigger Push (Online/Offline Mode), Push sent via Flows.
Assume marketers want that end users should not receive two notifications with-in 30 minutes, they would need to set Minimum Delay between two notifications as 30 minutes.
Example 1: If a user's device is eligible to receive notification N1 (sent via General Push campaign C1) at time 1:00 pm UTC and N2 (sent via General Push campaign C2) at 1:15 pm UTC. If the Min Delay setting is OFF, user's device will receive a campaign as per their Frequency Capping status. If Min Delay setting is ON (and set as 30 mins), user's device won't receive N2.
Example 2: If a user's device is eligible to receive notification N1 (sent via General Push campaign C1) at time 1:00 pm UTC and N2 (sent via Smart Trigger campaign C2) at 1:15 pm UTC. If the Min Delay setting is OFF, user's device will receive a campaign as per their Frequency Capping status. If Min Delay setting is ON (and set as 30 mins), user's device won't receive N2.
Q. But there might be certain campaigns which have to be sent urgently even if they are spaced closely?
Ans. MoEngage provides a capability to skip this setting on campaign level i.e. marketers should be able to create the campaign that may not abide by these settings of Minimum Delay. You can find it in Advanced Setting (for General, Smart Trigger and Geo Fence push) OR campaign Delivery Control (for Real Time Trigger push)
Q. Given that FC is evaluated on 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 with-in 15 mins, user become eligible for campaign C2 which is not sent because of Minimum Delay setting. FC bucket will be incremented to 2. Not if you try to send another campaign in the same day, it will not be delivered to 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 large scalable infrastructure. So even if these operations will take time in tunes of milliseconds, the campaign send times won't increase substantially.
Q If there are multiple campaigns scheduled at the same time and all of them get picked up at once, will minimum delay setting continue to work e.g. 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 exact 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.