Understanding how different journey versions interact with DESelect Engage and when those changes reflect in your Calendar View is crucial for accurate saturation control.
Journeys without the Engage Component
If you have an active journey that does not contain the DESelect Engage Component, saturation control still runs automatically in the background: Engage will automatically account for this journey and exclude any saturated contacts based on your configured frequency rules.
Because the Engage Component is missing, the journey will not appear as a scheduled Send in the Calendar View.
Journeys without the Engage Component are being included by DESelect Engage in calculations. However, these journeys don't appear on the Calendar View and cannot apply granular Rules, Channels, Priorities, or Contact Categories to them.
Adding the Engage Component to a new version
To gain full visibility and control, create a new version of the journey and add the Engage Component. This unlocks the ability to exclude contacts based on your specific setup of Rules, Channels, Priorities, and Contact Categories.
The new version will appear in the Calendar View immediately after activation.
However, the new version will not be included in Engage's saturation control calculations until the next scheduled Daily Automation Run Time (its colour will remain gray).
Important timing consideration — If you activate the new journey version at 10:00 AM but your Daily Automation Run Time is set for 3:00 PM, Engage will not calculate the new journey's impact until after 3:00 PM. Until that automation runs, saturation control continues to calculate based only on the previous version of the journey.
What about priority rules?
This timing gap has an important implication if you rely on journey priorities. Consider a scenario where you have a rule allowing 1 email per day applied to all contacts, and two journeys are both scheduled to send before your Daily Automation Run Time: All contacts will be included in both Sends, because the new version's priority setting has not yet been considered by Engage's calculations. If there are the same Contacts in both journeys/Sends, they will only receive 1 email randomly based on 1 email per day rule.
What can happen is that even if the second journey has a higher priority configured, that priority will not take effect until after the Daily Automation Run Time has passed.
Priority rules on new journey versions are not enforced until after the next Daily Automation Run. Scheduling two Sends in the same window before that automation runs means both will go out (if activated) regardless of priority settings.
Best practice
When introducing the DESelect Engage Component to a new journey version, always account for your Daily Automation Run Time. The Calendar View updates immediately — but the underlying saturation control calculations only sync after that automation has run. Plan your activation timing accordingly to avoid unintended sends.
Comments
0 comments
Please sign in to leave a comment.