It is possible to globally control the sending of pushes within an organization through the Granular Distribution Control! With it, a DR Admin can set daily and weekly limits for users in an Organization to receive push and make sure no user will be impacted above it's limits.

🚧

This process is implemented but doesn't guarantee that the reach count will not be affect during the campaign execution due the conflict of campaigns. To do that, we count with the Preprocessing!

The user booking process: reserve users for your Single Day Campaigns

In order to be able to meet the requirements of sending limits and have the best reach count as posible, DR1 works with the process called "user reservation", which consists of separating users from a single day campaign at the time it is sent for approval. These users are reserved only for that campaign and with that we make sure that they will not be impacted again!

📘

Preprocessing guarantee that users for single day campaigns will always match the reach count, independently of multiday campaigns running at the same time with same audience.

It is important to emphasize that this process - user reservation (preprocessing) - will always happen in one moment: when the campaign is sent for approval. And the only way to make these users available again is by rejecting the campaign or after the campaign has already been sent (respecting the daily and weekly sending limits).

Variations in the number of users to receive a campaign

With this limit control process, it can seem confusing to know how many users will receive my campaign. However, you can find out the correct number using the reach count button!

When creating a campaign, regardless of whether you are going to use an audience created beforehand or you are creating one right away, you can click on Reach Count in the upper right corner of your campaign creator and find out the updated information on how many users will be impacted.

This is important because, for reuse of old draft campaigns, the number of users to receive a campaign may be out of date (since reserved users may not have been used in campaigns anymore). Therefore, the recommendation is: every time you need to know the correct number of users of your campaign that will be sent for approval, select the reach count button and check the updated number! So, every time we change the date for a campaign, we need to update the reach count as well.

📘

Clicking the reach count button shows the number of available users, but does not reserve them. So, if a single day campaign is created and remains in draft and another single day campaign with the same users is created and sent for approval before the first one (thus reserving users for it), the first one will show outdated numbers until the reach count is updated. When clicked, their number should decrease

Total Audience size vs Actual Reach Count for an Audience

It is posible to know the difference between the number of total audience size without the sending limit and users that will actually be impacted due to the limits.

As said, when you see a number of reach count on the campaign creation, it is already considering the distribution limits. But, if you want to check if there is any difference to how many users should be reached, you can create the same cluster on the audiences page. In there, reserved users will not be considered (since they would only be counted when creating the campaign)

ORGs with single day and multiday campaigns

In ORGs that already have multiday campaigns in progress and you send for approval single day campaigns with pre-processing using the same audience, users will be reserved for this new pre-processing campaign, so this may decrease the reach of the multiday campaign in progress (even though the system tries to redistribute the campaign to users on days when they have an available slot to receive).

Preprocessing and internal settings

For all of this work, a slider called preprocessing must be enable in the admin settings. This is only available for DR Admin. And it is because of it that we can make sure that all the single day campaigns will have it's devices reserved, even that we create other campaigns after this first one.