Between Black Friday and year end, send volumes triple while filters tighten. How to ramp into peak season so November's volume looks like growth, not an incident.
Every November, senders who mail weekly decide to mail daily, senders who mail daily go to three times a day, and dormant lists get resurrected for one more Black Friday. Mailbox providers watch global volume surge while complaint rates climb, and they respond the only way they can: filters get less forgiving precisely when your revenue depends on them most. Peak season deliverability is won in October, by making November's volume look like a pattern instead of an anomaly.
How filters experience your Q4
Reputation systems model your normal: typical daily volume, typical cadence, typical engagement per send. A domain that averages 50,000 messages a day and suddenly emits 400,000 matches the signature of a compromised account or a rented list, and providers respond with deferrals and heightened scrutiny first, questions later. The 4.7.x deferral patterns from our bounce classification guide are the mechanical symptom; the cause is a volume curve with a cliff in it.
The second seasonal force is your competition for attention. Recipients drowning in promotions engage with a smaller fraction of everything, so per-send engagement rates sag list-wide in late November. A sender whose placement was already engagement-marginal in September starts Q4 with no cushion, and the seasonal sag pushes them under. That is why the list work matters more than the calendar work.
October: build the ramp
The core move is simple: get your volume curve rising smoothly before it needs to be high. If Black Friday week needs 4x normal volume, October and early November should walk daily volume upward so the peak arrives as the top of a slope rather than a step function. Providers accommodate growth; they punish discontinuity. This is the same physics as IP warming, applied to a seasonal pattern on infrastructure that already has history.
The October checklist
- 1
Ramp sends weekly
Increase campaign frequency and segment reach incrementally each week of October, so early November volume is already within striking distance of the peak.
- 2
Run hygiene now, not in November
Sunset the disengaged, process the bounce backlog, and finish any re-engagement attempts in October. Every address you cut before peak is complaint risk removed from the highest-stakes sends.
- 3
Freeze infrastructure changes
No ESP migrations, no IP changes, no DKIM cutovers between late October and January, per the timing rules in our migration guide. Peak season is for sending, not for warming.
- 4
Verify authentication headroom
Confirm SPF is under the lookup limit, DKIM selectors are healthy, and DMARC reports show clean alignment. Quiet authentication debt becomes loud at 4x volume.
- 5
Pre-register the feedback channels
Postmaster Tools, SNDS, JMRP, and the Yahoo CFL should be collecting baselines now, so anomalies in November read against known-normal charts.
The dormant-segment temptation
Every Q4 plan eventually contains the sentence: we should also send to everyone who has not bought in two years, it is free revenue. It is not free. As the spam traps article laid out, segments dormant beyond a year carry recycled traps, dead addresses, and people who have forgotten you, and mailing them mixes their complaint and bounce rates into the same domain reputation your Black Friday revenue depends on. The math almost never survives contact with the incident it causes.
Protect the transactional lane
Q4 is when the stream separation argument from our transactional article stops being theoretical. Order confirmations, shipping updates, and password resets spike with sales, and they must keep arriving instantly while the marketing storm rages. If both streams share a subdomain, IP pool, or DKIM identity, a marketing complaint spike throttles the receipts your customers are actively waiting for. Verify the separation holds end to end: distinct subdomains, distinct pools, distinct signing, so a marketing incident stays a marketing incident.
Throughput planning belongs to the same review. Deferral-driven queue growth during peak sends is normal; queues sized for February are not. Check your MTA or ESP throughput ceilings against the peak-day forecast, and configure send scheduling so campaigns spread over hours rather than slamming providers in one burst. A 2 million message campaign delivered over six hours behaves; the same campaign in twenty minutes gets deferred at exactly the providers where your customers live.
During the peak: watch and hold the line
Through Black Friday week, the monitoring cadence goes daily: spam rate and reputation in Postmaster Tools, SNDS colors, deferral rates by provider, and per-provider engagement, exactly the incident dashboard from our playbook, read proactively. The operational rule that saves senders is pre-agreeing the response to warning signs: if the Gmail spam rate crosses 0.15% or deferrals spike, the next campaign narrows to engaged segments instead of shipping as planned. Deciding that rule in October takes ten minutes; deciding it live on November 28, against a revenue target, is how incidents become quarters.
Come January, resist the cliff in reverse: step volume back down over a couple of weeks rather than dropping from peak to nothing, and run the post-season hygiene pass while the data is fresh. The list you finish December with, minus the addresses that spent Q4 ignoring you, is the foundation of next year's baseline.
Frequently Asked Questions
How much can I safely increase volume per week?
Should I add IPs for Q4?
Do providers loosen filters for the holidays?
Black Friday campaign to the full list or engaged only?
Key Takeaways
- Filters punish volume discontinuity; ramp through October so the November peak is the top of a slope
- List hygiene and any reactivation attempts happen in early October, never in the peak weeks
- Dormant segments resurrected for Black Friday are the classic self-inflicted Q4 incident
- Verify transactional and marketing streams stay separated end to end before the surge
- Daily monitoring with pre-agreed fallback rules turns warning signs into segment narrowing instead of incidents
Related articles
2025 in Email: The Year Authentication Became Mandatory Everywhere
Microsoft joined the mandate, Gmail moved to hard rejection, and DMARCbis reached the finish line. What 2025 changed for senders and what it sets up for 2026.
Building a Deliverability Monitoring Stack
Postmaster Tools, SNDS, FBLs, DMARC reports, TLS-RPT, bounce logs, engagement data: the full observability stack, what each layer catches, and the alerts worth paging on.
Email Validation Services: What They Can and Cannot Do
Validation APIs verify syntax, domains, and mailbox existence. Where each check works, where catch-alls and traps defeat them, and where validation belongs in your stack.