Email blast strategy: a blast is one message to everybody, so the only real question is whether everybody needed it

An email blast is a sending pattern, not a kind of content: one message, to the whole list, at one time. The word survives because it describes a real decision accurately, and the decision is almost always made by accident. Somebody has something to say, the platform offers a list called "All subscribers", and the send goes out to everybody because that was the default. The useful strategy is short: decide deliberately which sends are genuinely for everybody, build everything else as segments, and know what the all-subscribers send costs you when you choose it.

This page covers the three sends that do belong to the whole list, the arithmetic that explains why an unsegmented send is expensive even when it is free to send, how to rebuild one piece of content as three sends, the legal floor that applies either way, and a checklist for the blast you have decided to send anyway.

The three sends that genuinely belong to the whole list

• Something that affects every recipient's account, order or money. A price change, a terms change, an outage, a recall, a change of company name, a shipping cut-off that applies to all orders. Everybody on the list has a stake in it, nobody needs it tailored, and leaving anybody out is the error rather than including everybody.
• One genuinely universal dated event, used sparingly. The single annual sale, a closure, a move, a launch that replaces the thing people bought. The test is whether you would still send it to the person who has not opened an email in a year, because that is who makes an all-subscribers send different from a large segment.
• The re-permission message you send before cleaning the list. One message to the dormant portion asking them to confirm they still want it, with a plain statement that you will stop otherwise. That is a blast whose purpose is to shrink the list, which is the only blast that reliably improves the next ten sends.

Everything else is a segment wearing the all-subscribers label: a product announcement that applies to one tier, a case study from one industry, a webinar for one job title, a restock of one size. None of those is improved by reaching people it does not apply to, and each of them costs something when it does.

What one message to everybody costs, with the arithmetic shown

The cost is not the send, which is effectively free. It is your spam rate, and the spam rate is a ratio rather than a count, so the composition of the send decides it.

Google's bulk sender guidance tells senders to "Keep spam rates reported in Postmaster Tools below 0.10% and avoid ever reaching a spam rate of 0.30% or higher." Those are small numbers, and a whole-list send is the easiest way to reach them, because almost all complaints come from the part of the list that has forgotten who you are.

Take a 40,000 address list where 10,000 have opened something in the last ninety days and 30,000 have not. Put an illustrative complaint rate on each group, then replace both with your own figures from your platform's per-send reporting.

Send	Delivered	Complaints at 0.02% engaged and 0.25% dormant	Spam rate
Blast to everybody	40,000	2 plus 75, so 77	0.19%
Engaged segment only	10,000	2	0.02%

The blast reached four times as many people and produced a rate roughly ten times higher, which is the whole mechanism: the dormant 30,000 contributed 75 of the 77 complaints. Both of those numbers are inside the 0.30% figure Google says to avoid ever reaching, and one of them is comfortably inside the 0.10% target while the other is not.

Two consequences follow, and the second is the one that hurts.

• A blast can cross the bulk sender threshold on its own. Google's stricter requirements apply to senders who "send more than 5,000 messages per day to Gmail accounts". A 40,000 send crosses that in an afternoon, while the same content sent as segments over two weeks might never cross it at all.
• Reputation attaches to the sending domain, not to the campaign. The domain carrying your marketing is usually the domain carrying your receipts, password resets and appointment reminders. A rate earned by one promotional blast is applied to the mail people actually need, which is how a sale ends up delaying somebody's password reset.

The authentication and list-hygiene work that keeps all of this upright, SPF, DKIM, DMARC, one-click unsubscribe and the rest, is a separate subject and is set out in full in this guide to email deliverability and list health. Get that in place before deciding anything about sending patterns, because no amount of segmentation rescues an unauthenticated domain.

The same content, rebuilt as three sends

This is the practical substitute for a blast and it takes about twenty minutes longer than the blast did.

• Engaged, opened in the last ninety days. Send it as written, with the real subject line and the real ask. This is the group the content was actually for.
• Lapsed, on the list but quiet for ninety to three hundred and sixty-five days. Same content, different subject line, a smaller ask. Not "buy" but "is this still useful to you". Send it a day or two later so the first send's numbers are visible before the second goes.
• Never opened, or quiet for more than a year. Either the re-permission message or nothing at all. This is the group that generates the complaints, and sending them promotional content is paying for the privilege of damaging the first two sends.

Three sends from one piece of writing also gives you something a blast never does: a comparison. Same content, three audiences, three sets of numbers, and after three months of that you know which group is worth writing for. The shape of the issue itself, which decides whether any of them get read, is worked through with six worked examples in these examples of email newsletters.

The legal floor, which applies to a blast and a segment equally

In the United States the FTC's CAN-SPAM compliance guide sets out what every commercial message has to do. None of it depends on how many people you send to.

• Header information "must be accurate and identify the person or business who initiated the message". The From, Reply-To and routing details have to be truthful.
• "The subject line must accurately reflect the content of the message." A subject written to win an open on a false premise is the specific thing this rule exists to stop.
• The message must disclose clearly that it is an advertisement, with flexibility in how that is done.
• "Your message must include your valid physical postal address." A street address, a registered post office box, or a private mailbox registered with a commercial mail receiving agency.
• The opt-out has to work. You "must be able to process opt-out requests for at least 30 days after you send your message", and "You must honor a recipient's opt-out request within 10 business days". You cannot charge for it, require extra personal information beyond an email address, or make it more than a reply or a single web page.
• The penalty is per message. The FTC guide states that "Each separate email in violation of the CAN-SPAM Act is subject to penalties of up to $53,088", a figure it notes was updated in January 2024 for inflation. Per message is what makes this a blast-shaped risk: one wrong setting multiplied by the whole list.

If you send to the United Kingdom or the European Union, consent rules are stricter and sit on top of this rather than instead of it, so a list assembled under one regime is not automatically mailable under the other.

The blast you have decided to send anyway

Sometimes the answer genuinely is everybody. Then do these six things.

• Suppress the dead weight first. Hard bounces, role addresses, anything that has never opened in over a year. This is the single biggest lever on the rate and it takes one filter.
• Send in batches across hours, not all at once. A sudden spike from a domain that usually sends a trickle is itself a signal, and batching gives you time to see the first numbers.
• Watch the complaint rate during the send and set the number at which you stop before you press anything. A stop rule decided in advance is the only one that gets used.
• Put the unsubscribe where it can be found, including one-click support, because an easy unsubscribe is strictly better for you than a spam complaint. One removes an address, the other damages every future send.
• Send a seed copy to yourself on three providers and look at where it lands and how it renders, before the batch goes.
• Write down the result beside the date. Delivered, opened, clicked, unsubscribed, complained. Three of those entries tell you whether whole-list sending is something your list tolerates.

Questions about email blasts

What is an email blast?

One message sent to an entire email list at the same time, with no segmentation. The term describes the sending pattern rather than the content, and the opposite of a blast is not a better-written email, it is the same email sent to the part of the list it applies to.

Are email blasts bad?

The pattern is right for a small number of sends and wrong for most. It is right when the content affects everybody on the list, such as a price change or an outage, and when you are asking the dormant part of the list whether to keep them. It is wrong whenever the content applies to a subset, because the people it does not apply to supply the complaints that affect everything you send afterwards.

How often can I send to my whole list?

Let the complaint rate and the unsubscribe rate answer rather than a calendar. Send to everybody, record both numbers, and compare them with a segmented send of the same content. If the whole-list version produces several times the complaints for a similar number of clicks, you have your answer in your own data, which is worth more than any published frequency.

How many emails can I send a day before it becomes a problem?

Google applies its stricter sender requirements above 5,000 messages a day to Gmail accounts, so that is the number worth knowing. It is not a limit, it is a threshold: above it you need SPF, DKIM and DMARC and one-click unsubscribe on marketing mail, which you should have below it too.

What is a good subject line for a blast?

One that accurately describes what is inside, which is both the legal requirement and the commercially better choice. A subject that wins the open on a false premise moves the cost from the open rate to the complaint rate, and the complaint rate is the expensive one.

Should I buy a list to blast?

No. A purchased list is the fastest available route to the complaint rates described above, it fails the consent rules in several markets outright, and the damage lands on the domain that also sends your transactional mail. There is no version of this that is cheap.

The channel you do not own at all

Email is the channel where the list is yours and the reach is predictable, which is exactly why it is worth protecting from a careless send. There is now a channel at the other extreme, where you own nothing and the reach is decided entirely by somebody else's model: a buyer asks ChatGPT, Gemini, Perplexity, Claude or Google's AI Overviews who to use in your category, and gets two or three names back with a sentence about each. No list, no send, no open rate, and one way to find out whether you were named, which is to ask. Most businesses have never asked. Put your own buying question to two assistants, keep your own name out of the prompt so the answer comes back clean, and write down who was named. AI Knows Us runs those questions across the main assistants and records which companies get named and what each answer was built from.