Campaigns
Campaigns
One-time audience sends with an explicit delivery step.
A campaign is a one-shot send to everyone who currently matches an audience and is eligible. Membership is not re-checked after send starts — someone who joins later does not get it unless you send again.
Use a Journey when the send should be triggered by behavior, repeat, or be measured against a holdout.
Create
Campaigns → New campaign:
- Name the campaign (internal).
- Pick an audience.
- Write a new email or reuse a confirmed library document.
- Set communication class (marketing, newsletter, product updates,
operational, transactional) so the correct consent rule applies.
- Send now or schedule
sendAt. It stays a draft until that
action.
Send
Send queues a delivery per eligible contact. Missing consent or suppressions are skipped (counted as suppressed), not emailed “anyway.” Requires a verified ESP and deliver scope if you send via API.
Use a stable Idempotency-Key (send-${campaignId}) so retries do not double-queue. See Campaigns API.
After send
Open the campaign for queued / delivered / failed / suppressed plus opens and clicks. There is no holdout and no incremental lift number — that is Insights on Journeys.
Statuses you will see include draft, scheduled, sending, sent, and failed. Draft and scheduled campaigns can be deleted; sending/sent ones cannot be quietly erased from history.