How Often Should You Actually Email Your List
There's no universal right frequency — there's a right frequency for your list's engagement level, and most companies are guessing instead of testing for it.
“Once a week” is the answer you’ll get from most marketing blogs, and it’s wrong often enough to be actively unhelpful. A 400,000-subscriber e-commerce list and a 2,000-person B2B newsletter for a niche vertical tool have nothing in common in terms of what frequency their audience will tolerate, and treating “email cadence” as a universal best practice rather than a per-list optimization problem is why so many companies either under-mail a highly engaged list (leaving revenue on the table) or over-mail a lukewarm one (quietly training people to stop opening, then eventually unsubscribe or mark as spam).
Frequency is a function of engagement, not a fixed rule
The right question isn’t “how often should we email” in the abstract — it’s “how often can we email this specific segment before marginal engagement turns negative.” Those are very different questions with very different answers depending on where a subscriber sits in their relationship with your brand.
A subscriber who opened your last five emails and clicked through on three of them can probably handle daily or near-daily sends without meaningful fatigue — that behavior indicates a genuine desire for your content, not tolerance you’re testing the limits of. A subscriber who hasn’t opened anything in 60 days is already disengaged, and adding more emails to their inbox at that point does nothing but harm your sender reputation with the mailbox providers who are watching how recipients treat your mail — and increasingly, that reputation affects whether your emails reach the inbox at all, for everyone on your list, not just the disengaged segment.
This means the answer to “how often should we email” should never be a single number for your whole list. It should be a frequency tier structure, calibrated to engagement level, reviewed and adjusted on a recurring basis as subscribers move between tiers.
Building an engagement-tiered sending model
A workable structure most email platforms can support without custom development: split your list into three or four engagement tiers based on rolling 90-day open and click behavior, then assign a different maximum frequency to each.
Highly engaged (opened/clicked in the last 30 days, multiple times): these subscribers can typically sustain 3-5 emails per week without meaningfully rising unsubscribe rates, provided the content quality holds — this tier is where most companies are actually leaving revenue on the table by artificially capping frequency to match a company-wide policy that was set for the disengaged tier.
Moderately engaged (opened within 60-90 days but not consistently): 1-2 emails per week is usually the sustainable range — pushing this segment to daily sends is where fatigue starts showing up in the data as declining open rates over successive sends within the same week.
Disengaged (no opens in 90+ days): drop to a monthly or even quarterly cadence, focused specifically on re-engagement content (a “we miss you” style campaign, a genuinely compelling offer, or a direct ask about whether they still want to hear from you) rather than your standard content — mailing this segment at the same frequency as your engaged tier does measurable damage to deliverability with very little offsetting benefit, since they’re not opening anyway.
Run a hard sunset policy for the bottom of the disengaged tier — subscribers with zero opens across 6+ months and no response to a re-engagement attempt should be suppressed or removed. This feels counterintuitive (a smaller list looks worse on a vanity metric) but it directly protects deliverability for the subscribers who are actually reading your emails, since mailbox providers weight engagement rates, and a list padded with dead addresses drags down your sender reputation for everyone.
Reading the actual signals of over-mailing
Unsubscribe rate is the metric most teams watch, but it’s a lagging and fairly blunt signal — by the time someone unsubscribes, you’ve usually already lost meaningful engagement from them over several prior sends. Watch for earlier warning signs instead: a declining open rate trend across consecutive sends within the same week (a sign the current cadence is fatiguing people faster than they’re recovering interest), rising spam complaint rate even if unsubscribes look stable (complaints hurt deliverability more directly and faster than unsubscribes do), and a growing gap between your highly-engaged tier’s behavior and your list average (a sign your top tier is being under-served relative to what they’d tolerate, while your bottom tier is dragging your aggregate metrics down and possibly masking the top tier’s real appetite).
A specific pattern worth testing for directly: send the same content to a held-out segment at your current frequency and to another at a reduced frequency for a month, then compare total engagement (not per-email engagement, total across the period) between groups. Teams that run this test are often surprised to find that reducing frequency for a moderately engaged segment increases total monthly clicks, because each individual email gets read more attentively and generates less “delete without opening” fatigue — fewer, better-targeted emails frequently outperform more frequent, lower-quality ones on total engagement, not just rate metrics.
The under-mailing mistake nobody talks about
Frequency discourse online skews almost entirely toward “don’t over-mail,” which has led a lot of B2B marketing teams to under-mail out of excess caution, sending a single monthly newsletter to a highly engaged list that would happily engage with content two or three times a week. This is a real, measurable cost — every week you don’t send to an engaged, opted-in subscriber is a week of foregone revenue or pipeline you could have generated with content they wanted.
The tell that you’re under-mailing: your highly-engaged tier’s open rates stay unusually high (60%+) across every send with almost no decay over time, and your unsubscribe rate on that tier is near zero. That combination usually means you have headroom to increase frequency for that specific segment before you’d start seeing any negative signal — and the only way to know where that ceiling actually is is to test upward in small increments (adding one additional send per week to the top tier for a month, watching the engagement and unsubscribe metrics, then deciding whether to hold or pull back) rather than assuming a conservative default is automatically safer.
A worked example of tiering in practice
Take a 100,000-subscriber list currently sending one weekly newsletter to everyone. A rolling 90-day engagement pull typically shows something like: 20,000 highly engaged (opened/clicked multiple times in 30 days), 35,000 moderately engaged, and 45,000 disengaged — a distribution that’s common for lists that have been growing for a few years without active engagement-based segmentation.
Moving the highly engaged 20,000 from 1 send/week to 3 sends/week and holding content quality constant typically adds meaningfully more total monthly clicks from that segment alone than the entire disengaged tier generates in a month, simply because the base engagement rate per send is so much higher. Meanwhile, dropping the 45,000 disengaged subscribers from weekly to monthly cadence doesn’t just save on a smaller ESP bill — it removes roughly 180,000 sends a month (45,000 × 4) to addresses that were dragging down your aggregate open rate and, by extension, your sender reputation with Gmail and other major mailbox providers, who use aggregate engagement signals to decide whether your next send goes to the inbox or the promotions tab or spam folder for everyone, including your engaged tier. The math works in both directions: sending more to people who want it and less to people who don’t both improve the numbers, and neither improvement is visible if you’re only looking at one blended “list average” metric.
The deliverability spiral: how over-mailing becomes self-reinforcing
The reason over-mailing is dangerous isn’t just annoyed subscribers — it’s a feedback loop with the mailbox providers themselves. Gmail, Outlook, and Yahoo all track engagement signals (opens, deletes-without-opening, “mark as spam,” time spent reading) in aggregate across your sending domain, not just per-subscriber. If you increase frequency and a meaningful share of recipients start deleting without opening or marking as spam, that degrades your domain’s sender reputation, which in turn causes more of your total sends — including to subscribers who do want your mail — to land in spam or promotions instead of the inbox.
Once that spiral starts, the fix isn’t just reducing frequency again; sender reputation recovers slowly, typically over weeks of consistently clean sending behavior, not immediately after the behavior that caused it stops. This is why the tiered approach matters so much more than a single company-wide frequency number: mailing your disengaged tier aggressively isn’t just wasted effort on those specific subscribers, it actively degrades inbox placement for every subscriber on the list, including the ones who’d happily read a daily email from you. Teams that notice a mysterious drop in open rates across their entire list, including previously reliable segments, should check whether a recent frequency increase to a low-engagement segment is the actual root cause before assuming content quality slipped.
Sequencing the rollout of a tiered sending model
Don’t flip your whole list to tiered frequency in one send. Roll it out in stages: first, pull the engagement data and define your tier boundaries and cadences without changing anything live, so you can sanity-check the segment sizes look reasonable (a “highly engaged” tier that’s only 2% of your list, for instance, suggests your thresholds are too strict). Second, implement the frequency cap changes for the disengaged tier first, since reducing send volume is lower-risk than increasing it and buys you an immediate, measurable deliverability benefit within a few weeks. Third, once the disengaged-tier change has run for a full send cycle without issues, test increasing frequency to the highly engaged tier in one additional-send increments, watching unsubscribe and complaint rates weekly rather than monthly during this phase since that’s where problems would surface first. Only after both ends of the tier system are validated should you touch the moderately engaged middle tier, since it’s the segment where the wrong call is hardest to detect quickly — engagement decline there tends to be gradual rather than an obvious spike.
B2B and seasonal cadence look different from consumer lists
Engagement-tiering logic holds across B2B and B2C, but the absolute numbers and seasonal patterns differ enough that borrowing a benchmark from the wrong context leads to bad decisions. B2B audiences check email in bursts tied to the workweek — Tuesday through Thursday mornings reliably outperform Mondays and Fridays for opens, and the weeks around major holidays (the last two weeks of December, the week of July 4th in the US) show engagement drops of 30-50% that have nothing to do with your frequency and everything to do with people being out of office. A B2B team that increases frequency in early December and sees falling open rates is likely to misdiagnose fatigue where the real cause is seasonal absence, and should discount that period entirely when evaluating a frequency test rather than drawing conclusions from it. Consumer lists tied to retail or seasonal buying patterns show the opposite skew — engagement often rises sharply around key shopping periods regardless of frequency, which can just as easily mask an actual over-mailing problem if a team assumes the lift is proof the higher cadence is working when it’s really the calendar doing the work.
Content type should drive frequency decisions as much as list size
Not all email serves the same purpose, and lumping every send type into one frequency policy is a common structural mistake. Transactional and lifecycle emails (onboarding sequences, usage-triggered nudges, renewal reminders) operate on entirely different logic than broadcast newsletter content — they’re triggered by behavior, not calendar, and frequency there should be governed by the lifecycle stage and event, not a blanket weekly cap. A user in week one of onboarding might reasonably get four or five emails in that week as part of a structured sequence, while the same user six months later gets your standard newsletter cadence — conflating these into one “how many emails per week” number misses that the right question is really several separate questions for several separate email programs.
Separate your reporting and frequency planning by program type: newsletter/broadcast, lifecycle/triggered, and promotional/campaign. Each has its own sustainable cadence, and a subscriber’s total weekly email volume from you is the sum of all three — which is easy to lose track of if each program is planned in isolation by a different team member without visibility into what the others are sending the same subscriber that same week.
Setting a review cadence for your frequency policy itself
Treat your email frequency tiers as a policy to revisit quarterly, not a decision made once and left alone. List composition shifts as you acquire new subscribers through different channels (a webinar list behaves differently than a content-download list from month one), seasonal patterns affect tolerance (B2B audiences often show measurably lower engagement in the weeks around major holidays regardless of frequency, which can look like a frequency problem when it’s actually a timing one), and content quality changes over time as your team and topics evolve.
The most reliable operating pattern: review engagement-tier movement and aggregate metrics monthly, run a deliberate frequency test (up or down, on a specific segment) at least once a quarter, and resist the temptation to set a single company-wide “we send X emails per week” rule that gets treated as permanent policy rather than a hypothesis you’re actively testing against your actual list’s behavior.
