Campaigns
Review, schedule and send an issue, deliver it at each reader's local time, and resend to non-openers.
A campaign is one issue of your newsletter. Write it in the editor, press Continue, and the review step brings together everything you need to check before it goes out.
Review and preflight
The review step runs the same checks as the Send button. Blockers must be fixed; warnings need a tick to acknowledge.
| Check | Type |
|---|---|
| A sending provider is connected and its test send succeeded | Blocker |
| Your sending domain is verified, and the From address is on it | Blocker |
| A postal address is set for the footer | Blocker |
| The email has a subject and renders without errors | Blocker |
| There is at least one recipient | Blocker |
| Enough sending quota for everyone | Blocker |
| Complaint and bounce rates are under the limits | Blocker or warning |
| A large first send from a domain with no history | Warning |
The same page shows the spam score, the content checks and, with warm-up on, how the send will spread over the coming days.
Choosing recipients
Send to everyone who is subscribed, or pick a segment. Segments are evaluated when sending starts, so people who joined after you wrote the issue are included. Unsubscribed, bounced and suppressed addresses are always left out, and the suppression list is checked again for every single email.
Scheduling
- Schedule any time from one minute to one year ahead.
- Scheduled campaigns can still be edited. Unschedule to turn one back into a draft.
- At send time the checks run again. If a blocker has appeared in the meantime, such as a lost DNS record, the campaign is not sent and the reason is shown.
Timed delivery
Choose when each reader receives the issue. The newsletter's default is set in Settings → Send timing, and each campaign can override it on the review step.
| Mode | Each reader gets it |
|---|---|
| Everyone at once | as soon as sending starts |
| A set local time | at that clock time in their own time zone, such as 08:00 wherever they are |
| When they're most active | at the start of the hour they usually open or click; straight away if there is no history yet |
- Delivery times are worked out when sending starts and are never more than 24 hours later.
- A reader's time zone comes from their signup form, their first open or click, or a poll vote. Readers without one use the fallback time zone you choose.
- Settings → Send timing shows how many readers have a known time zone and most-active hour, so you can tell how well each mode will work.
Pause, resume, cancel
A sending campaign can be paused (it stops before the next small batch) and resumed later. Cancelling stops everything still queued. Emails already delivered can't be recalled. Sending also pauses on its own when the daily quota or the warm-up cap is reached, and carries on when there is room again.
Resend to non-openers
Give readers who missed an issue a second chance. On the review step, turn on Resend to non-openers:
- It waits between 12 hours and 7 days after the campaign finishes sending (48 hours unless you change it).
- It goes only to readers who neither opened nor clicked and are still subscribed. Readers with an Apple Mail automatic open are left out too, so nobody who may have read it gets it twice.
- Set a new subject, or keep the original with the prefix
In case you missed it:. - It needs open tracking on. A resend is never resent.
To resend every new campaign by default, use Settings → List maintenance → Resend to non-openers.
Sponsor reports
Running an ad? Mark the issue as Sponsored on the review step, optionally with the sponsor's name. The tag is internal: readers never see it. Once the issue starts sending, create a private report link from the campaign's report and send it to the sponsor.
What the sponsor sees
- Subscribers and recipients, delivered, opens and clicks (total and unique), unsubscribes, open and click rates
- Clicks for each link, and opens and clicks hour by hour for the first 72 hours
- How the issue compares with your previous 10 issues, and a link to it on your archive