An issue is one email to the whole list or a part of it.
Building the email
New issue opens the builder. Pick How the email is built:
| Mode | What it is |
|---|---|
| Blocks | Heading, text, image, button and divider blocks, in any order. Text takes **bold**, *italic*, [words](https://address) and lists |
| Own HTML | Your ready-made markup. An unsubscribe line is appended unless the markup has {{unsubscribe}} |
Set the subject and the preview line that mail apps show next to it. The preview shows the email as a subscriber sees it, on a phone or a desktop, and sends a test to yourself.
Variables fill in per subscriber: {{name}}, {{name|friend}} with a fallback, {{first_name}}, {{email}}, custom fields as {{city}}, and {{unsubscribe}}.
The list's header image and button colour are set in the list settings.
Who gets it
Audience is everyone subscribed, or only those with any of the tags you name, or those who read within some days, or the opposite: those silent for some days.
Sending
Send now shows how many people will get it and asks first: what is sent cannot be recalled. Schedule picks a time. Emails per hour spreads the sending, because mail providers throttle anyone who sends everything at once.
An issue pauses itself when too many emails bounce or people complain, or when the sending server keeps refusing; you get a notification. Clean the list and Resume.
A queued or sent issue cannot be edited; Duplicate copies it into a new draft.
Results
For each issue: sent, opened, clicked, unsubscribed, bounced and complaints, and clicks per link. Opens are an estimate, since some mail apps open emails by themselves and others never load images; clicks can be trusted. Turn Count opens and Count link clicks off to send the email exactly as written.