What is a “frequency cap”?

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

You've built a welcome series, a post-purchase flow, a winback automation, and a weekly newsletter. Then one subscriber triggers all four in the same week. That's where a frequency cap saves you.

A frequency cap is a global rule that limits how many marketing emails a single recipient can receive within a set time window, no matter how many automations or campaigns would otherwise fire. Think of it as a safety valve that sits above everything else.

Common cap structures look like this:

  • Max 1 marketing email per day
  • Max 3 to 5 marketing emails per week
  • Separate caps for different categories (promotional vs. educational vs. behavioral)

When a subscriber hits the cap, messages queue up or get skipped entirely, depending on how your ESP handles it. The cap forces a decision about which message matters most, which is honestly a useful discipline for any sending program.

What usually counts toward the cap (and what doesn't):

  • Marketing campaigns and newsletters: yes, these count
  • Automations (welcome, winback, abandoned cart): yes, these count too
  • Transactional emails (receipts, password resets, shipping updates): typically exempt, because subscribers expect and need those

Some teams set different caps by segment. A highly engaged subscriber who opens everything might tolerate 5 emails a week without a second thought. A dormant subscriber who hasn't opened in three months probably shouldn't be getting more than one. Matching frequency to engagement level is one of the smarter moves you can make for long-term deliverability.

So most advanced ESPs have frequency cap controls built in. Klaviyo calls them "smart sending" limits. Braze and Iterable have dedicated frequency management settings. Lighter platforms like Mailchimp or MailerLite may not have native global caps, so you'd manage it through careful segmentation and suppression logic instead.

One thing worth building in: an override for genuinely time-sensitive messages. A flash sale ending in 24 hours or a critical account alert might need to reach a subscriber even if they've hit the weekly cap. Just make sure "urgent" doesn't become the label you slap on everything.

If you're seeing complaint spikes or unsubscribe rates creep up, a frequency cap is often the first thing worth testing. You can also check your sending patterns with our free Email Header Analyzer to see what's actually hitting inboxes and when. Or if you're not sure where to start, drop us a line and we'll take a look with you.

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

Get frequency cap recommendations for your setup

My subscribers are getting too many emails because multiple automations and campaigns overlap. Based on my setup below, what frequency cap settings would you recommend, and how should I handle segments with different engagement levels? - Email type (promotional / transactional / mixed): your answer - My ESP: your answer - Average sends per subscriber per week right now: your answer - Segments I'm working with (e.g., new, active, dormant): your answer Please suggest: (1) a starting cap structure, (2) how to handle transactional exceptions, (3) whether different segments should have different limits.

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