Frequency Caps Belong in the Preference Center, Not Just in the Send Calendar
Most frequency caps are a planning tool. The team agrees no subscriber gets more than four emails a week, and then the exceptions begin: the transactional team has its own stream, the product launch is exempt, the partner send does not count. The subscriber experiences none of those distinctions. She experiences eleven messages. A cap that lives only in the send calendar caps intentions. A cap offered to the subscriber, inside the preference center, and enforced at the point of send across every stream is a promise, and promises are what preference centers are supposed to contain.
Let the subscriber set the ceiling
Offer a simple choice in plain numbers: at most one email a week, up to three, or as many as we send. Most subscribers never touch it, which is fine. The ones who do are disproportionately the engaged subscribers drifting toward fatigue, exactly the people a team most wants to keep. Honouring their ceiling, even when a campaign is important, is the test of whether the preference center is real. The first time a major launch bypasses subscriber caps for revenue, the center becomes decoration and the next hundred subscribers who set a cap learn that it means nothing.
Enforcement is a data problem
A subscriber cap only works if every send checks it, including the streams that consider themselves separate: lifecycle triggers, back in stock alerts the subscriber requested, loyalty programme mail, and the manual campaign built outside the main platform. That means the cap has to live in one place, attached to the profile, and be read by the send decision, not copied into each tool's settings where versions drift. Count sends per subscriber per rolling seven days, not per calendar week, so a Sunday and Monday send do not pretend to be a week apart.
Decide what outranks a cap, and write it down
Some messages should pass a marketing cap: order and delivery updates, security notices, and alerts the subscriber explicitly requested for a specific item. State that list in the preference center in plain language, so the subscriber setting a cap knows what will still arrive. The grey zone is triggered marketing dressed as service: a shipping email carrying a promotional banner is a marketing send wearing a service costume. If it promotes, it counts. Keeping that line bright is what makes the cap legible to subscribers and defensible when a regulator or an inbox provider asks how consent is honoured.
Caps change campaign maths for the better
Once caps bind, send volume stops being free, and campaign selection improves. Teams start asking which email deserves a slot in a capped subscriber's week, which is a question unlimited sending never forces. Measure the capped group separately: their unsubscribe and complaint rates should fall, and their per email revenue should rise because they receive fewer, better chosen messages. If total programme revenue holds while sends drop, and it often does, the cap has exposed how much of the old volume was waste the team was paying to deliver.
Keep reading
Related guides on this site: Preference Centres: Ask for Less Up Front, Learn More Over Time Transactional and Marketing Preferences Are Two Different Promises Practical answers about personalization.
Frequently asked questions
What is a frequency cap?
A limit on how many marketing messages a subscriber can receive in a period. Caps can be set by the sender as a policy or chosen by the subscriber in a preference center.
Should transactional emails count toward a cap?
Pure service messages such as order confirmations usually sit outside a marketing cap, but any promotional content in them blurs the line. State clearly in the preference center which messages will still arrive.
What happens when a subscriber hits their cap?
Lower priority marketing sends are held or dropped for that subscriber until the window resets. Priority should be decided in advance, not argued per campaign.