Implementation Guides
...
Saturation Control
Prerequisites
edition requirements this guide uses features available in deselect segment plus and deselect segment advanced if you are on deselect segment enable, some required features are not available you can still follow the concepts, but you will not be able to replicate all examples users on segment plus can follow the entire guide the only limitation is waterfall selections however, a workaround is provided define your email frequency when defining your email frequency, you have to take into account two factors 1\ align frequency with your objectives the purpose of your email strategy directly influences how often you should contact your audience for example loyalty building campaigns typically require a lighter frequency traffic driving or promotion heavy strategies may justify a slightly higher cadence feedback collection emails may require more targeted timing rather than more volume if your strategy has multiple goals , you must decide which objective takes priority, as trying to maximize all goals simultaneously can lead to saturation 2\ email frequency changes over time your saturation limit should evolve based on performance start with a reasonable benchmark—such as 1–2 weekly emails , which aligns with industry standards—and test from there also, you can split your audience into three groups with different frequencies 80% → baseline saturation limit (n) 10% → lower limit (n − 1) 10% → higher limit (n + 1) compare open rate, unsubscribe rate, and click through rate across groups adjust your limit, retest, and iterate until you find your email frequency sweet spot a practical starting point is 2 emails every 10 days, then refine through testing data views overview salesforce marketing cloud stores behavioural data in data views in them, you will find all the emails sent to your audience and other valuable information like which of them were opened or which contents were clicked for this guide, the relevant data views are sent records all emails sent to customers open records which emails were opened click records which email links were clicked to learn more about data views, see https //support deselect com/hc/en us/articles/4414400519569 what do you need to know to work with data views in sfmc set up your saturation control framework to start off saturation control, begin by creating three core master data extensions contact interaction report tracks how many emails were sent to each customer within your defined time window (e g , 10 days) you may exclude specific messages, such as transactional or operational emails, to ensure only controlled sends contribute to saturation calculation this report provides historical insight into messaging pressure and helps validate whether frequency aligns with expectations fields contact id emails sent emails opened emails clicked contact available slots think of email frequency as a number of “slots” available per contact each email “fills” a slot by comparing available slots to emails sent, you can determine whether a customer has reached their threshold you may assign different slot configurations to audience segments for testing if all contacts use the same limit, you may skip segmentation and keep a single value fields contact id slots 3\ master contact saturation compares emails sent (from the interaction report) with slots (from available slots) to determine saturation status fields contact id saturated (true/false) this data extension is used directly in your campaigns to filter out saturated contacts when creating a campaign, include this data extension and select only contacts where saturated is set to false