To make sure a campaign Send (also called just "Send/s") is sent, no matter the saturation levels of contacts, saturation control can be disabled for a Send.
To do this:
- Inside DESelect Engage, from the Overview Screen, on both the Calendar View and List View, you can click on a Send and disable the Apply Saturation Control by sliding the setting off. Once a Send is excluded, it will show up on the Excluded Sends section on the List View page. Sends in this section are excluded from saturation control. DESelect Engage will not apply any logic and let all Sends through, and ignore these Sends in future saturation control decisions.
- Inside Journey Builder, on the DESelect Engage Journey Builder component, there is a switch called 'Saturation Control enabled'. For Sends that have been marked as excluded in Engage, this switch will be turned off already. If you turn off the switch in Journey Builder for that Send, the Send will be shown as excluded inside Engage.
Note: alternatively, you could also not add the Engage journey builder component to your journey. Note that in that case the Send will still be considered as the Data Views are ingested. DESelect Engage will take this Send into consideration in a contact's history and it will impact the contact's saturation levels.
For example: if you sent an email through Journey Builder without the DESelect Engage component, the Send will still be ingested by Engage. While the system does not know the Campaign Type in this case, it does know the Channel, so this will count against Rules like 'max. 3 emails per 7 days'.
In contrast, when you add the Engage component but turn off 'Saturation Control enabled', this Send will be ignored completely. Engage will send all contacts through the Undersaturated branch, and the Send will also not be ingested, so it will not count toward contacts' saturation levels and rules.