Minimum delay between campaigns

Marketers 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 one notification or message within 5-10 mins which deteriorates their experience.

To improve this notification/message delivery experience, marketers can ensure that two or more notifications/messages are not delivered in quick succession to any device/app/website using this setting. Marketers can configure a delay between two push/in-app/osm notifications delivered to a user.

If you do not want end users to receive two push notifications within 30 minutes, 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.

Configure and Setup Minimum delay

To enable minimum delay, go to the following navigation in the MoEngage Dashboard and set the delay to the desired duration to control the communication being sent out.

Settings -> Channels -> Delivery Controls -> Minimum delay

To enable minimum for a channel:

      1. Turn the channel toggle on.
      2. Set the minimum delay to the desired time limit.
      3. Click Save.

MinDelay.png

Previous

Next

Was this article helpful?
0 out of 0 found this helpful

How can we improve this article?