Write, check, approve, send
Campaigns has a tab per channel, starting with Email. Start from a blank email or let Scout draft one from your project. The composer supports rich blocks, Markdown or HTML, with a subject, preview text, a plain-text version and an optional issue archive. Send a test, duplicate a campaign, schedule it or leave the time empty to send right after approval, and limit the audience when you need to.
Sending is deliberately a sequence of separate steps:
- Run checks for the sender, the unsubscribe link, size and audience.
- Request approval for that exact version and audience.
- Approve. Approving does not send.
- Send, once.
Changing the content or the sending credentials cancels the approval. Scout can draft, stage, pause and cancel campaigns, but it cannot approve or send them.
Sequences
Sequences are emails that go out on their own when a reader joins or when your app reports an event you choose.
Ways to send
- Sent by TractionScout through Amazon SES, with domain setup checks for DKIM, return-address records and DMARC. You can also use your own SES through an assumed role, so no AWS keys are stored.
- Brevo or Mailjet, connected as data sources. Lists and addresses stay in your own account.
- A paired self-hosted SDK host.
Reports you can believe
Each send reports accepted, delivered, opened, clicked, unsubscribed and bounced, with unique clickers per link and the mailbox providers your readers use. Rates are calculated from the accepted cohort. Opens and clicks count only for readers who allowed tracking, and signing up never grants that permission. Provider-side tracking is switched off for Mailjet and Resend so it cannot add its own pixels.
Limits
With Brevo or Mailjet, scheduling, audience limits, signup forms and the archive stay in the provider's account. Mailjet drafts cannot be deleted through its API.
