How does frequency capping relate to consent?

Still have a question, spotted an error, or have a better explanation or a source we should cite?

Someone subscribes to your newsletter. They tick the box, confirm the double opt-in, and you've got their consent. So you can send them as many emails as you want, right? Not quite.

Consent gives you permission to email someone. It doesn't give you permission to email them at any volume, any cadence, or any time of day without limit. Think of it like being invited into someone's house. The invitation doesn't mean you can show up three times a day unannounced.

When a subscriber signs up, they form an expectation based on what you showed them. If your signup form says "weekly digest," they're consenting to weekly email. If you then send daily, you're operating outside what they agreed to, even if your legal T&Cs technically allow it. That gap between expectation and reality is where complaints come from.

Here's how it usually plays out. A subscriber who genuinely wanted your emails starts getting five in a week. They don't hate you, but unsubscribing feels like effort. The spam button is right there. One click and your complaint rate nudges up. Multiply that across a few hundred people and your sender reputation starts to feel it. This is why consent drift is such a quiet danger. You didn't lose permission at once. You eroded it through volume.

Frequency capping is one way to protect the relationship you built through consent. It sets a ceiling on how many touches a single contact receives in a given window, whether that's two emails per week or one per day across all your automation flows. The cap doesn't replace consent. It enforces the spirit of it.

But the strongest version of this is letting subscribers choose their own frequency. A preference centre that asks "how often do you want to hear from us?" turns implicit expectation into explicit agreement. That's genuinely more reliable from a compliance perspective, especially under GDPR where the lawfulness and scope of consent are taken seriously. (Some interpretations of GDPR do treat systematic over-mailing as exceeding the scope of the original consent.)

Practically speaking, you want your automation rules and your consent records to agree with each other. If someone signed up for a weekly product update, your flows shouldn't be stacking a welcome sequence, a re-engagement nudge, and a promotional drip all at once. That's where capping at the contact level, not just the campaign level, makes a real difference.

If you're unsure whether your automations are staying within the bounds of what subscribers actually agreed to, it's worth auditing your flows end to end. Check what someone who enters today would receive and when. If it would surprise you, it'll definitely surprise them.

Contributors

Who worked on this answer

Every name links to their profile. Every company links to their site. Real people, real accountability.

Ask an AI · tailored to your setup

Check my frequency against consent

Based on my email program, help me figure out whether my current sending frequency is within the scope of what my subscribers consented to. I'll describe my signup process and automation flows, and I'd like you to flag any gaps between subscriber expectations and what they're actually receiving.

Edit the yellow boxes, then send to the AI of your choice.