Send Frequency
Optimization

The Frequency-Reputation Relationship

The connection between send frequency and inbox placement works through a single primary mechanism: complaint rate. Complaint rate is complaints divided by emails delivered. If you double your send frequency to a particular subscriber without generating proportionally more value for them, each email becomes a new opportunity for that subscriber to click "Report Spam." Their tolerance for your email has a threshold — and frequency determines how quickly you reach it.

For engaged subscribers (Tier 1 in your engagement model), that threshold is high. They want to hear from you. Adding a third weekly email doesn't push them toward spam reporting — they're in an active relationship with your brand. For disengaged subscribers (Tier 3 and Tier 4), that threshold is already low. They haven't engaged in months. They've been meaning to unsubscribe but haven't gotten around to it. When your 5th email of the week arrives, the path of least resistance is "Report Spam."

The compounding damage is what makes frequency-related reputation problems particularly harmful: a complaint generated by an over-mailed disengaged subscriber doesn't just affect that subscriber's future deliverability. It affects your domain's aggregate complaint rate, which affects inbox placement for all your emails — including the campaigns going to your Tier 1 Champions who were happy to receive them.

The Frequency Threshold Is Per-Subscriber, Not Per-List

Every subscriber has their own frequency tolerance. Your Champions might be comfortable with daily email; your At-Risk subscribers might complain after the second email in a week. Treating your entire list with a single frequency policy guarantees you will over-mail some subscribers and under-mail others. The solution is applying frequency rules per segment — which is exactly what engagement-tier-based frequency limits accomplish.

ISP Fatigue Signals and How to Read Them

ISPs don't tell you directly when your frequency is too high. They communicate through the only language that matters: changes to your domain reputation score and inbox placement rate. Learning to read these signals early — before they escalate to significant deliverability damage — is a core skill for maintaining inbox placement at scale.

Google Postmaster Tools: Domain Reputation Trends

Google Postmaster Tools provides your domain reputation as a categorical score: High, Medium, Low, or Bad. The most important metric for frequency monitoring is not your current reputation score but the trend over time. A domain that was "High" for three months and then dropped to "Medium" one week after you increased send frequency has given you a clear signal.

The typical pattern for frequency-related reputation damage is: frequency increases on Monday, reputation holds steady for 7-14 days (reputation is weighted on recent signals, so the damage builds slowly), reputation drops to "Medium" 2-3 weeks later, and if frequency isn't reduced, continues declining toward "Low" over the following weeks.

InboxEagle's Google Postmaster monitoring tracks your domain reputation score daily and alerts you when it changes category — giving you early warning before a "High" to "Medium" drop affects open rates and before a "Medium" to "Low" drop causes significant inbox placement loss.

Yahoo Sender Hub: Complaint Rate Trends

Yahoo's Sender Hub provides complaint rate data for your sending domain at Yahoo and AOL. Monitor the trend — a rising complaint rate that begins after a frequency increase is a frequency signal, not a content signal. Complaint rates from Yahoo FBL tend to be more responsive to frequency changes than Gmail's reputation score, making Yahoo data a useful early warning system even for senders whose primary audience is Gmail users.

Inbox Placement Rate Trends

The most concrete fatigue signal is declining inbox placement rate — fewer emails landing in inbox, more in spam or promotions. Monitor inbox placement per major ISP using seed list testing. If your inbox placement at Gmail drops from 95% to 80% over two weeks following a frequency increase, that is quantifiable frequency damage. Seed list testing per segment shows you whether the placement drop is isolated to your disengaged segments (expected) or spreading to your engaged segments (serious problem requiring immediate frequency reduction).

Optimal Send Frequency by Engagement Tier

The frequency recommendations below are derived from aggregate industry data and represent safe starting points for most senders. Your optimal frequency will differ based on your audience, industry, and content type — but these ranges are defensible defaults while you gather your own data.

The frequency gap between Tier 1 and Tier 3 is intentional and significant. Tier 1 subscribers are generating positive reputation signals with every open, click, and purchase — they can handle higher frequency because their engagement partially offsets the complaint risk. Tier 3 subscribers are generating weak signals at best, and every additional send to them increases the probability of a complaint event.

Seasonality Adjustments

During high-volume send periods — Black Friday/Cyber Monday, holiday season, major sales events — senders typically increase frequency significantly. This is safe for Tier 1 subscribers, manageable for Tier 2, and risky for Tier 3. During seasonal campaigns, restrict your frequency increase to Tier 1 and Tier 2 only. Do not extend high-frequency seasonal campaigns to Tier 3 or Tier 4 just because you want more reach — the reputation damage will outlast the campaign's revenue benefit.

Using Google Postmaster to Find Your Optimal Cadence

Google Postmaster Tools provides the data you need to empirically determine your optimal sending cadence — rather than relying on industry benchmarks alone. The process involves changing frequency deliberately, monitoring Postmaster reputation closely, and using the observed response to set your frequency policy.

The Cadence Discovery Protocol

Start from your current frequency and make one change at a time. If you currently send 2x per week to your full list and want to test 3x per week, increase frequency only to your Tier 1 and Tier 2 segments. Hold the new frequency for 30 days — this is important, reputation changes are slow. After 30 days, check Postmaster:

• Reputation held at "High" for 30 days → frequency increase is sustainable for Tiers 1-2; consider carefully before extending to Tier 3
• Reputation dropped from "High" to "Medium" → roll back to previous frequency immediately; the current subscriber mix cannot sustain 3x/week
• Reputation held but spam rate trend is slowly increasing → you're at the edge of your sustainable frequency; hold here rather than increasing further

Reading Postmaster Domain Reputation Correctly

A Postmaster reputation of "High" means Gmail is classifying your domain as a trusted sender with good engagement history. "Medium" means Gmail has detected some negative signals but still delivers most of your email to inbox. "Low" means Gmail is routing a significant portion to spam. "Bad" means Gmail is blocking or heavily filtering your email.

When assessing frequency impact on Postmaster, look at the User Reported Spam Rate metric, not just the domain reputation category. User Reported Spam Rate is the percentage of emails Gmail users marked as spam. A rising User Reported Spam Rate is an earlier warning signal than a domain reputation category change — categories change only after the spam rate has sustained above thresholds for long enough to shift Gmail's classification.

Waterfall Segmentation: Preventing Email Overload

Even with per-tier frequency caps, a subscriber can receive too many emails in a short window when you have multiple active campaigns, automations, triggered flows, and transactional sequences all running simultaneously. A subscriber who just received an abandoned cart email, a win-back email, and a promotional campaign in the same 24-hour period is being bombarded — and will respond accordingly.

Waterfall logic (also called "frequency capping" or "send-window suppression") prevents subscribers from receiving more than a defined number of emails within a specific time window, regardless of how many campaign triggers or flow enrollments apply to them.

Waterfall Rules to Implement

• 24-hour rule: if a subscriber received any email in the last 24 hours, suppress them from broadcast campaigns (automations and transactional are exceptions)
• 48-hour triggered rule: if a subscriber received a triggered email (cart abandonment, browse abandonment) in the last 48 hours, suppress them from the next broadcast campaign send
• Weekly cap by tier: Tier 2 subscribers who have received 3 emails this week are suppressed from additional sends until next week; Tier 3 subscribers who have received 1 email this week are suppressed for the rest of the week
• Win-back isolation: subscribers in an active win-back sequence are suppressed from all broadcast campaigns for the duration of the win-back flow

Implementing Waterfall Logic in Major ESPs

Klaviyo: Use Smart Sending (Settings → Smart Sending) to set a global minimum time between emails per subscriber. Configure per-flow send windows using the "Profile has been in flow for X hours" condition in flow filters. Klaviyo's Smart Sending skips a subscriber's scheduled campaign send if they've received an email within the Smart Sending window.

ActiveCampaign: Use Contact Tag-based suppression — add a tag when an email is sent ("email-sent-today") with a 24-hour expiry automation, and add a campaign condition to exclude contacts with that tag. More complex waterfall logic requires building suppression automations that tag and untag contacts based on send events.

Mailchimp: Mailchimp's built-in frequency controls are limited. Implement waterfall logic by building suppression segments based on last send date (using custom merge fields updated via API) and applying those segments as exclusions in each campaign.

Testing Different Frequencies Without Hurting Reputation

Testing frequency safely requires a different approach than typical A/B testing. A standard A/B test divides your list randomly and sends each variant simultaneously. For frequency testing, this approach is dangerous: your losing variant (the too-frequent group) may generate enough complaints to permanently affect your domain reputation, and the test runs for such a short time that natural reputation cycles aren't accounted for.

Frequency Testing Principles

Test on your lowest-risk segment first. Never run frequency tests on cold or disengaged segments. Start with your Tier 1 Active segment where complaint rates are lowest and engagement is highest. If your Tier 1 segment can sustain a higher frequency without elevated complaint rates, you have better evidence before considering extending that frequency to Tier 2.

Run tests for full 30-day cycles. Reputation changes are slow. A 7-day frequency test does not give you enough data to assess reputation impact — you're testing inbox placement during a period before the reputation consequences of the new frequency have had time to materialize. Minimum 30-day test windows for frequency changes.

Monitor Postmaster throughout the test. Check Google Postmaster domain reputation and User Reported Spam Rate weekly during frequency tests. If you see a rising spam rate within the first 2 weeks, end the test early — the signal is already appearing before the full 30 days are complete.

Use holdout groups, not A/B splits. Instead of randomly splitting your list, create a holdout group — a segment that continues receiving your original frequency while the test group receives the new frequency. This gives you a cleaner comparison because the holdout group controls for external factors (seasonality, news events) that might affect engagement independent of frequency.

Interpreting Frequency Test Results

When analyzing a frequency test, look beyond revenue metrics. Higher frequency often generates more short-term revenue (more sends = more purchase opportunities) even when it's damaging deliverability. The metrics to weigh are: complaint rate change (any increase above 0.02% per send is a warning), unsubscribe rate change (higher frequency should not increase unsubscribe rate by more than 20%), and Postmaster domain reputation (must hold steady or improve). If higher frequency increases revenue but also increases complaint rate above 0.05% and starts a Postmaster downtrend, the deliverability cost outweighs the short-term revenue gain.

The Sustainable Frequency Formula

The right send frequency is the highest frequency at which your complaint rate stays below 0.05% and your Postmaster domain reputation holds at "High" over a sustained 30-day period. This is your sustainable frequency ceiling — it will be different for your Tier 1 segment than for Tier 2, and very different for Tier 3. Finding it through careful monitoring and incremental testing gives you a data-backed frequency policy that maximizes revenue without sacrificing the inbox placement your entire email program depends on.