Campaigns
Launch
The Launch step is the final gate of the campaign builder. It checks that the campaign is actually sendable, lets you prove the email in a real inbox first, and then either starts sending or schedules a start time — with a live monitoring dashboard from the moment you commit.
In this guide you will:
- work through the pre-launch checklist
- send yourself a test email and preview per-recipient output
- launch immediately or schedule a future start
- read the monitoring dashboard while the campaign runs
The pre-launch checklist
The Pre-Launch Checklist card tracks completion with a progress bar. Items marked Required gate the launch buttons — they stay disabled until all three are satisfied:
| Item | Satisfied when | Required |
|---|---|---|
| Email account selected | A sender is chosen in the sequence editor's Sender panel | Yes |
| Valid recipients | At least one valid recipient in the Leads step | Yes |
| Sequence complete | Every email step has both a subject and a body — the checklist names the offending step ("Step 2 is missing a subject or body") | Yes |
| Test email sent | You have sent at least one test | Recommended |
Test emails and previews
- In the checklist's test row, enter an address and click Send Test. The email arrives with a
[TEST]subject prefix, sent through your selected account with tracking disabled, so it never pollutes campaign analytics. Spintax subjects are resolved to a single variant. - Preview Campaign opens a per-recipient preview: it resolves personalization variables and spintax against real recipients so you can see exactly what each person will get.
Send tests to more than one mailbox provider (Gmail, Outlook) before big sends — HTML renders differently across clients, and a test is the cheapest place to find out.
Launch now or schedule
The Ready to Launch? row shows the recipient count and three buttons:
- Launch Now— starts immediately. The campaign moves to Running and you are redirected to the campaigns list with "Campaign launched with N recipients".
- Schedule Campaign — opens a dialog with Date and Timefields and the note that the campaign will be scheduled in your campaign's timezone (set on the Sequence step's Schedule tab). The time must be in the future; the campaign then sits in Scheduled status until it fires.
- Preview Campaign — the per-recipient preview described above.
"Launch Now" still respects your sending window. With the default Monday–Friday, 09:00–17:00 schedule, a campaign launched Friday night starts delivering Monday morning — the monitoring dashboard will show recipients as scheduled, not stuck.
How fast does it send?
Sending speed is controlled by the Sequence step, not here: the lead pacingsetting ("Reach a new lead every N min") combined with your sending hours and days determines the daily throughput. The launch step shows the resulting estimate; internal batching is handled for you and has no user-facing knobs. See Sequence settings.
Monitoring after launch
Once the campaign exists, a Campaign Monitoring dashboard appears right on this step and updates in real time:
- Scheduled campaigns show a countdown banner ("Sending in: 2d 4h 12m 30s").
- Cards for Total Sent (progress against the recipient count), Pending, Delivery Rate, Open Rate, and Click Rate, plus a bounce alert when bounces climb.
- An Email Status Detailstable with each recipient's state — Pending, Sending, Sent, Delivered, Opened, Clicked, Bounced, Failed, or Cancelled — filterable by status. Before launch it lists recipients as Ready/Scheduled with estimated send times.
To pause, resume, or cancel a schedule afterwards, use the row menu on the campaigns list — Start, Pause, and Cancel Schedule live there.
Troubleshooting
- Launch buttons disabled — a required checklist item is incomplete; the checklist names which one.
- Test email not received — check spam, confirm the sending account shows Active on the Email Accounts page, and try another address.
- Nothing sending after launch — check the sending window first; outside your configured hours and days the campaign waits by design.
Do it via the API
Campaigns can be launched from code too. The API deliberately makes sending a two-step preview-then-confirm operation so an automation cannot fire a send unreviewed — see Sending via the API and the Campaigns reference.