Sending and scheduling

The review step

Before a campaign can go out, the review step checks it:

• a subject, and content;
• the unsubscribe link, which MailCheap adds to every issue written in the editor;
• a size under 100 KB, since Gmail cuts off longer emails;
• a postal address, set in the newsletter's settings;
• a from address the newsletter is allowed to send from.

It also warns about a subject over 70 characters, which inboxes cut off, a missing preview text and a missing test email. Warnings don't stop you.

Who gets it

By default, every active contact of the newsletter gets the issue, most engaged first: those who open and click the most get it before the others. To send to only some of them, pick one of your segments in To, which shows how many contacts it reaches out of all of them. New segment makes one without leaving the step, like your most engaged contacts. Segments

A draft whose segment was deleted waits until you pick another.

The same step shows the issue's web page address, which you can change, and what the list cleanup will do at this send.

Send now or schedule

Send now asks you to confirm, then the issue starts going out. Schedule opens a calendar, with today marked, and times every 15 minutes. Once you've sent an issue before, it tells you when a time matches your last one. A scheduled issue goes out by itself, up to a year ahead; the checks and limits run when you schedule it and again when it goes out. Unschedule turns it back into a draft.

First sends in steps

The first time an issue goes to contacts who never got an email from you, usually right after an import, they don't all get it at once. With more than 200 of them, a slice goes first: 5% of them, between 200 and 2,000. The rest follows 3 hours later, once the slice's bounces and spam complaints are in.

If the slice gets more than 2% hard bounces (at least 5) or 0.08% complaints (at least 2), the rest waits for you to resume it. Far over those rates, your account is blocked. A list with bad addresses shows itself in the slice, before it reaches everyone. Contacts you emailed before go out normally.

Pausing a send

Emails can't be recalled once they go out. While an issue is still going out, Pause on its page stops the rest: what's sent stays sent. Resume sends the rest, after checking your account again.

MailCheap pauses a send by itself when too many of its emails bounce or get marked as spam. Bounces, complaints and pauses

Sending to more

A send capped at a number of contacts, which the API can set, goes to the most engaged first. Send to more on the campaign's page then sends it to the next most engaged contacts who haven't got it yet. You pick how many, and each time starts a new step, so you can check the report in between.

The report

Each sent campaign's page shows how many emails were delivered, opened and clicked, and how many bounced, were marked as spam or led to an unsubscribe, with results by inbox provider, like Gmail or Outlook. It counts the list cleanup's last-chance emails apart. Opens are an estimate: some inboxes load every email's images on their own, which counts as an open, and some readers block images.

Its links come next, most clicked first: how many contacts clicked each one, every click, and each link's share of the contacts who clicked a link. A link counts once whatever its tracking parameters, like utm_source, and link scanners and the unsubscribe link don't count. An issue sent before clicks were counted per link only has the clicks since then. The API and AI assistants get the same list in the campaign's report.