Product guide
Campaigns
A campaign ties together an audience (segment), a message (template), and a schedule: send manually, once at a time, or on a recurring rule. Each execution creates a run with delivery stats.
What it is
You describe who gets mail, what they see, and when (or whether) automation should fire. Until segment and template are set and the schedule is valid, the campaign is “incomplete” and cannot send.
How it helps
- Clear blast scope — always tied to one segment, so you know exactly which list received each send.
- Automation-ready — recurring schedules and “new contacts” style flows reduce repetitive work.
- Traceability — runs and mail logs connect back to the campaign for support and reporting.
How to use it
In Campaigns, create a campaign, pick segment and template, configure schedule, then use Send now or wait for the scheduled time. Choose sending accounts if you want to override defaults.
Schedule types (summary)
- Manual — you trigger each send.
- Scheduled once — single datetime in ISO 8601.
- Recurring — interval + day/week/month unit.
- Recurring for new contacts — automation oriented toward newly added segment members (see in-app copy for exact behaviour).
Compared to one-shot “broadcast” tools
Campaigns are first-class objects with schedule metadata and run history—not only a one-off send. That makes API automation and auditing easier: the same campaign can be updated, re-sent, or inspected over time.