Skip to main content
Use a campaign for a one-time send to a defined cohort, a product update, mint reminder, rewards announcement, or ecosystem activation.

​
Steps

1

Create the campaign

Name it for reporting: audience, goal, and date, e.g. “Base minters, claim reminder, Jul 2026”. Campaign names are what you’ll scan in analytics months later.
2

Define the audience

Pick contacts, segments, or both. A contact matching either is included.
3

Check the estimate

Confirm the recipient count is a number you expect before writing content. This is the cheapest place to catch a broken segment.
4

Add content

Choose a template or start blank, then set subject, preview text, and sender. See the template builder.
5

Validate

Run validation and clear every error, the same checks run at launch, so anything unresolved blocks the send.
6

Preview and test

Continue to Preview and Test Send.

​
Validation errors

RENDER_FIELD_MISSING is by far the most common. See Missing values block sends.

​
Setup checklist

  • Campaign name includes audience, goal, and date
  • Sender identity is verified and matches the project brand
  • One primary call to action
  • Every merge variable has a fallback
  • Audience estimate reviewed, including the smart-sending exclusion count

​
Duplicating a campaign

Duplicating copies content and audience but resets the status to draft and clears stats, the fastest way to run a recurring send without rebuilding it.

​
Goals

A campaign can carry conversion goals measured over an attribution window (1–90 days, default 14).
email_open and email_click goals always report zero. They look for recipient data under a key the send pipeline doesn’t write. Use campaign analytics for open and click rates instead, which reads the events correctly.
Goal measurement covers up to 10,000 contacts and flags the result as truncated beyond that.