Agent-readable docs index: /docs/llms.txt. Full docs in one file: /docs/llms-full.txt. Download /docs/docs.zip to grep all markdown files locally.

Create campaigns and inspect delivery results

Campaigns send reviewed content to a contact audience. Use them for audience messaging from the dashboard, with a selected purpose, delivery strategy, sender, content, and timing. Transactional application notifications use the messages API instead.

Choose the audience

Select lists or a published segment supported by the composer. Inspect the audience and remove accidental test or internal records. A segment campaign uses a single channel and pins the published definition when sending starts.
Matching is not delivery eligibility. Consent, unsubscribe, suppression, missing destinations, channel reachability, sender readiness, and current sending controls can exclude recipients later.

Compose the message

Choose a saved template or write custom content. Personalize with available contact fields, review missing data, and confirm every link. Email requires a subject and active sender; WhatsApp provider requirements and SMS Sender ID approval still apply.
Set the purpose accurately. Marketing audiences require appropriate permission. Review the selected routing strategy so you understand how the composer will distribute recipients.

Review and launch

  1. Audience: confirm list or segment, count, and exclusions.
  2. Channel and sender: check the intended number, SMS sender, or email From/Reply-To identity.
  3. Content: inspect the final rendering and variable substitutions.
  4. Timing: check the displayed date, time, and timezone for scheduled delivery.
  5. Funds and allowance: inspect the estimate and current availability.
  6. Launch: use the campaign's final review action when ready.
Delivery is background work. Convert prepares recipient records, reserves/captures funds as applicable, and paces provider submissions. A large connected-number WhatsApp audience intentionally takes longer than an instantaneous burst.

Interpret results

Read recipient-level outcomes alongside campaign totals. Sent means provider acceptance, delivered comes from receipts, and read/open/click data is available only where supported. A completed send phase can contain failed, skipped, or excluded recipients.
Investigate before resending. Inspect failure reasons and existing provider IDs. Do not duplicate an accepted message merely because its delivery receipt is late.

Read campaigns through the API

GET /api/v1/campaigns and GET /api/v1/campaigns/:id require campaigns:read. They expose recent campaign summaries and details. These documented customer API routes do not create or launch campaigns; use the dashboard review flow for launch.
Next: review billing, deliverability, and webhooks.
Segment edits do not change a pinned campaign definition. A new campaign can use the newly published version; inspect the campaign's own audience snapshot when troubleshooting.