Limiting the reception rate of campaigns

Contents

Limiting the reception rate of campaigns

Overview

To prevent bothering employees with bursts of campaigns, distinguish between urgent and non-urgent campaigns.

A couple of protection periods control the rate at which employees can receive Engage campaigns:

  • Do Not Disturb period
  • Non-negotiable Protection period
Applies to platforms: PlatformWindows.png

Urgency of campaigns

Urgent campaigns
Because urgent campaigns are never delayed by the protection periods, targeted users start receiving urgent campaigns as soon as they are published. Only prefer urgent campaigns to deliver critical information.
Non-urgent campaigns
Targeted users receive a non-urgent campaign only if they did not recently receive any other campaign. Prefer non-urgent campaigns in general.
  • If the targeted users previously received a non-urgent campaign, the Do Not Disturb period must elapse before they can receive another non-urgent campaign.
  • If the targeted users previously received an urgent campaign, the Non-negotiable Protection period must elapse before they can receive a non-urgent campaign.

Set the urgency of a campaign when specifying the recipients of the campaign. Although the protection periods cannot delay the delivery of an urgent campaign, note that the general conditions for receiving campaigns apply to both urgent and non-urgent campaigns.

The default duration of the protection periods are as follows:

  • Do Not Disturb: 6 hours
  • Non-negotiable Protection: 20 minutes

Set the duration of the protection periods in the configuration file of the Portal.

Examples of protection against campaign bursts

The following examples show how the protection periods would work for a particular user who receives different types of campaigns. The examples use the default values for both the Do Not Disturb period (6 h) and the Non-negotiable Protection period (20 min).

Non-overlapping case

In this example, two non-urgent campaigns are published within an interval greater than the Do Not Disturb period; therefore, the user receives both campaigns at the time of their publication:

  • Campaign Non-urgent 1 is published and received at 07:00.
  • Campaign Non-urgent 2 is published and received at 15:00.

DoNotDisturbNonUrgent.png

Overlapping case

In this other example, two non-urgent campaigns are published within an interval shorter than the Do Not Disturb period; therefore, the user receives the second campaign only after the Do Not Disturb period of the first campaign has elapsed:

  • Campaign Non-urgent 1 is published and received at 07:00.
  • Campaign Non-urgent 2 is published at 11:15, but received at 13:00.

DoNotDisturbOverlap.png

Overlapping case with urgent campaign

Consider now the two non-urgent campaigns of the previous example and add a third campaign that is urgent. The urgent campaign is published just five minutes before the Do Not Disturb period of the first campaign ends. Because the campaign is urgent, the user receives it without delay. On the other hand, the second non-urgent campaign is delayed not only by the Do Not Disturb period of the first campaign, but also by the Non-Negotiable period of the urgent campaign:

  • Campaign Non-urgent 1 is published and received at 07:00.
  • Campaign Urgent is published and received at 12:55.
  • Campaign Non-urgent 2 is published at 11:15, but received at 13:15.

DonotdisturbUrgent.png