Your Black Friday and Cyber Monday Checklist

Eleven tips to get ESPs and deliverability teams through the busiest online shopping event of the year.

Black Friday falls on 27 November 2026, followed by Cyber Monday on 30 November. Last year, shoppers spent $44.2 billion online over the entire Cyber Week. As one of the year's largest online shopping events approaches, email teams get nervous, and for good reason. This is one of the few times of the year when every business with an online offering wants to send more emails in roughly the same timeframe and hit the same mailbox providers.

Preparation goes beyond having enough servers. ESPs and delivery teams need to understand how much volume each customer can support, what happens when providers slow down, and how quickly they can stage an intervention without disrupting other customers. Here are eleven tips to put you in the best position for the email silly season.

Everybody knows they should ramp up ahead of Black Friday and Cyber Monday. The more subtle consideration is how fast. If you send one million emails a day and suddenly send five million on Friday, the receiving side sees a major change in behavior.

Unfortunately, there’s no single safe number. The speed at which you can increase volume depends on your sending history and audience quality, as well as how recipients and mailbox providers respond over the weekend.

Take two domains sending the same daily volume. One has more than 20% measured human opens and a click rate above 1%. The other has around 8% opens and a 0.2% click rate. Their room to grow may be very different.
The first audience shows stronger interest, while the second is already ignoring much of the email it receives. As such, increasing volume to that second audience can make an existing problem worse.

A useful way to approach this is to group audiences into three engagement bands. Use these alongside delivery and conversion data to guide your increases and hold or reduce volume if delivery signals worsen. 

Measure honestly

Privacy features and security scanners can generate opens and clicks without a person reading the email. Filter recognized machine activity where your platform supports it and understand the limitations of the remaining engagement data.

Measure by mailbox provider 

A domain can perform well at Gmail and poorly at Microsoft. Your ramp plan needs to reflect that difference. A healthy overall average can hide a provider-specific problem.

Grow from the inside out

Add the next most engaged audience at each step. You might begin with people who have been active in the last 30 days, then cautiously expand to 60 or 90 days. Use clicks, purchases, and other relevant activity where possible. Decide how far you are willing to extend and do not rely on the oldest section of your list to find your extra volume.

Check the impact of every increase

After each increase, hold volume steady long enough to assess the impact. Are deferrals or complaints rising? Are there new blocks or signs of worsening inbox placement? If delivery signals deteriorate, reduce volume and investigate what’s changed.

Prepare sending IPs and domains, too

If you need additional capacity, introduce and warm it now. A new IP or subdomain with little history, introduced during Black Friday week, creates uncertainty at the worst possible time.

For ESPs, preparation also means understanding each customer’s ramp plan. Ask your biggest senders for campaign dates, expected volumes, daily send frequency, and the audience segments they plan to add. Too many teams discover a customer's Black Friday plan from the queue graph.

The weeks before Black Friday are an opportunity to build engagement ahead of the peak. With everyone competing for attention in November, another “20% off” subject line may not stand out. Use October and early November to get people interested and participating before asking for a sale. Give them a reason to interact:

• A mystery offer revealed on Friday.
• A scratch card or spin-the-wheel experience for early access.
• A countdown with a new clue each day.
• A quiz or poll asking which deal people want unlocked.
• A wish list people build now, followed by a notification when the offer goes live.

AMP for Email, which Gmail calls dynamic email, can support interactive experiences inside compatible inboxes. Forms, polls, and other interactions can happen without sending the reader to a separate landing page. Specific game mechanics need to be designed and tested within AMP's supported components. Wish list selections and poll answers also give you segmentation data for the weekend itself. Use what people tell you to send more relevant offers. Below are three practical considerations:

Check support and provide a fallback

AMP's support list includes Gmail, Yahoo Mail, and Mail.ru, but support varies by provider, client, and user settings. Include an HTML fallback that carries the same idea for recipients who cannot see the interactive version.

Allow time for registration and approval

If you plan to use AMP for this year’s Black Friday, follow AMP’s sender registration guidance and check each provider’s requirements. For example, Google requires registration for each sending email address and a production-ready example. It aims to respond to most requests within five business days, but your schedule also needs to allow for development, testing, and any revisions.

Where possible, measure interactions directly

An in-email form submission may not register as a conventional click. Measure these interactions directly where possible. Adding a game alone does not guarantee a better reputation. The objective is genuine interest in relevant mail, supported by observable recipient behavior.

I think about capacity in three parts: scale, slow acceptance, and backup.

Scale: find your real ceiling

Most teams know their average throughput, but fewer know their real ceiling, especially when queues are deep. A system that runs quickly with an empty queue may slow sharply as the backlog grows. The bottleneck could be storage, a logging pipeline falling behind, or the database processing delivery and bounce events.

To find your ceiling, take last year’s peak-hour volume, add this year’s expected growth plus some headroom, and test against a controlled receiving sink. Watch where performance starts to degrade, testing SMTP throughput as well as the systems supporting the MTA. Slow acceptance: plan for backlogs

Slow acceptance: plan for backlogs

Allow for changes in mailbox provider behavior. Do not assume mailbox providers will accept mail at their usual pace over the weekend. Plan for slower acceptance and temporary failures. The same volume can take longer to deliver because messages spend more time in the queue, connections remain occupied longer, and a single message may require several attempts. That does not automatically mean you should open more connections. Your platform needs capacity to handle the backlog while respecting provider-specific limits and backoff.

Test a real-world scenario. Game out what happens if one large provider accepts mail at half its usual rate for four hours. Where does the mail wait? Does that backlog interfere with delivery to other providers?

Include inbound processing in your tests. Some bounces arrive during the SMTP conversation; others arrive later as messages. Complaints, unsubscribes, and replies add load too. If processing and suppression fall behind, later sends may continue to include addresses that should already have been removed.

Backup: make it usable before you need it

A server can fail at peak. An IP pool can develop a reputation problem. You need spare capacity and a tested response. Can you lose one server and still meet your send windows? If a server goes down with two million queued messages, can you recover those messages elsewhere, or do they wait until the server returns?

Backup sending capacity needs appropriate history with providers. Carry a planned share of real traffic during preparation, within your reputation and routing policies. If a pool is blocked because of harmful traffic, fix that cause before moving the traffic elsewhere. Test how quickly you can add a server with the correct policies and configuration. Cover DNS, logging, tracking, and monitoring. Sending capacity without visibility leaves you operating partly blind.

On Black Friday and Cyber Monday, some of your most important emails will be order confirmations, password resets, one-time codes, and shipping notices. Customers have paid or are trying to complete a purchase, and they are waiting. When promotional volume rises and a provider starts deferring, a receipt or password reset can end up stuck behind a huge queue of promotional messages.

The answer is to separate the streams. Appropriate IP pools and subdomains can help manage reputation, but you also need distinct queues, limits, and resource allocation. A marketing backlog should not consume the connections and concurrency needed by transactional mail. Subdomains alone do not guarantee independent reputation. ESPs should apply the same principle between customers so one customer's bad weekend doesn't delay everyone else’s receipts.

During the weekend, you may see more temporary SMTP failures than usual. A 4xx response means the attempt has temporarily failed, but its cause matters. It may reflect rate limiting, reputation, authentication, recipient-specific conditions, or another problem, so read the response and act accordingly.

If a provider asks you to back off, more aggressive retries and hundreds of extra connections are the wrong response and can aggravate the problem. Instead, reduce sending pressure for the affected provider, IP, and stream. Then hold and recover cautiously.

To help avoid this issue, check ahead of the weekend that:

Provider-specific limits are in place
Gmail, Yahoo, Microsoft, and smaller regional providers behave differently. Include providers important to your customers, even if they represent a small share of total platform volume.

Backoff rules recognize current responses
Providers can change wording and codes. Review recent unclassified responses and brittle matches on exact text.

Limits can change safely and quickly
If an adjustment requires editing configuration on every server and reloading it, the team may make fewer adjustments, later than it should.

During Black Friday and Cyber Monday, the queue becomes one of the main things you manage. Three capabilities matter.

Expiry. A four-hour offer delivered six hours after sending can annoy a customer and lead to a complaint. Set expiry according to the campaign and message purpose. A flash sale and a receipt should not automatically have the same retry window. Otherwise, Saturday's queue can contain Friday's expired offers competing with Saturday's live campaigns. For codes and other time-sensitive transactional mail, align delivery expiry with the useful lifetime of the message too.

Priority. Decide in advance what goes first when capacity is constrained. Transactional mail should receive the resources it needs. Among promotional campaigns, a time-limited offer may need priority over a general newsletter.

Control. View and analyze the queue by customer, campaign, provider, stream, and other relevant dimensions. Hold, release, or drop a specific slice without affecting unrelated traffic. Agree with customers beforehand how expired campaigns will be handled and who can authorize stopping them.

Provider dashboards are valuable, but they do not give you a complete live view. Google says Postmaster Tools data typically updates within 24 hours and can take longer, while SMTP conversations tell you what providers are saying right now. Combine those responses with queue and processing telemetry for a more complete picture of what’s happening across your platform.

Once you have a more holistic view, watch five things:

Every year, someone says: “It's Black Friday. Let's send to everyone.” That often includes recipients who have not engaged for two years. From an operations standpoint, this is one of the weekend's biggest self-inflicted risks, and it hits when you need your reputation most. Old addresses can bounce, others may have become recycled spam traps, and recipients who no longer remember the sender may complain.

Gmail and Yahoo require spam rates below 0.3%. Treat that as a boundary to stay well away from, not a budget to spend. Provider-reported rates may use different denominators from your ESP's complaint metric, so do not assume they are interchangeable.

If the business wants to reach a dormant segment, test it earlier, in small batches. Watch results, retain people who show genuine interest, and stop mailing those who do not. By Black Friday, use an audience whose behavior you have already tested.

ESPs should have this conversation with customers now. They also need a way to contain the customer who ignores the advice.

A platform that discovers harmful traffic only after a shared pool is blocklisted is reacting too late. Monitor for customer-specific anomalies and maintain the ability to isolate the affected traffic promptly.

About two weeks before the weekend, run a preflight check to cover some basic items. Remember: These may seem simple and obvious, but each can cause a serious incident.

Freeze structural changes, keep operational controls available

After validation, freeze planned upgrades, refactoring, and structural infrastructure changes from roughly a week before Black Friday until the Wednesday after Cyber Monday.

Be explicit about operational actions that remain available: rate changes, traffic holds, campaign cancellation, and safe routing adjustments. Preserve a controlled emergency change process too.

With so much scheduled activity, you should plan for something to go wrong. The best responses are usually thought through and rehearsed, not improvised on the spot. I find a five-point plan is an effective way to bring all the key points together. Write down:

1. Coverage and escalation. Who is on call, during which hours, and who can help? Peak US hours can fall late at night for teams in Europe or India.
2. Authority. Who can pause a campaign or customer under agreed conditions? Avoid discovering during an incident that nobody present can act.
3. Initial checks. Prepare short runbooks for heavy provider deferrals, a blocklisted IP, a queue that will not drain, and delayed transactional mail.
4. Fallbacks. What happens if a server or pool becomes unavailable? Is spare capacity ready, and when is rerouting appropriate? Do not move a harmful campaign into another healthy pool.
5. Customer communication. Who writes the update, where does it go, and when is the next update due?

Reducing pressure on the affected stream so you can investigate is a useful first move for provider throttling or suspected harmful traffic. Pushing through can turn a manageable delay into a much longer incident. Other causes, such as authentication failures, need their own corrective action.

I’d recommend running a drill on a quiet afternoon. Measure how long each step actually takes because the slowest step is often the one everyone assumed would be quick.

The work does not end on Cyber Monday.

Avoid unnecessary abrupt changes in sending patterns. December can remain busy with shipping notices, last-order dates, and holiday campaigns. Continue watching reputation: delayed complaints and provider data can reveal weekend effects later in the week. Then review the weekend while the details are fresh:

• Peak-hour volume against the plan.
• Where queues built up and how long they took to drain.
• Which providers pushed back, and when.
• Transactional delivery latency, including the worst delays.
• Every manual intervention.

That last point is especially valuable. Each intervention is something to assess for automation, a clearer runbook, or a change to the infrastructure that made the task harder than it needed to be.

Black Friday and Cyber Monday usually go better for the teams that did the work in October. They ramped at a pace their audience and delivery signals supported, tested capacity, separated their streams, and agreed the runbook.

During the weekend, two capabilities matter repeatedly: how quickly you can see what is happening, and how quickly you can change what the system does for one provider, one customer, or one campaign without disrupting everything else.

Go back through the questions in this guide. If the system handles most of them reliably, you have a better chance of a quiet weekend. If most require someone to act by hand, your weekend depends on that person's availability and judgment.

It is worth knowing that now, while there is still time to prepare. This year, the answer may be more on-call coverage and a tighter runbook. For next year, it may be a bigger conversation about the infrastructure you run on.

Have a good Black Friday and a successful Cyber Monday. I hope it is a boring weekend!