How a campaign works | AgentsMail.io Documentation

A campaign is one email sent once to one audience. It carries its own subject and its own HTML — copied from a template if you started from one, but never linked back to it. Editing the template afterwards changes nothing here.

The statuses

Status	What it means	What you can still do
`draft`	Being written. Nothing has left.	Everything
`scheduled`	Waiting for its departure time.	Cancel the schedule, which returns it to draft
`sending`	Emails are going out.	Nothing
`sent`	Finished.	Read its statistics
`failed`	The send stopped on an error.	Read the reason

There is no going back from sent. A campaign is never sent twice — resending means creating another one.

Choosing the audience

A campaign targets one list, optionally narrowed by a tag or a segment. Both narrow; nothing widens. The number shown before departure is an estimate. The real audience is resolved when the send runs: only subscribers, minus anyone who unsubscribed in the meantime, minus suppressed addresses, minus the people who declined the campaign's topic.

Sending, or scheduling

Sending is immediate and irreversible; the confirmation says so and shows what is about to go out. Scheduling asks for a date and time in your organization's time zone — the one set in sending settings, not the one your laptop is in. A scheduled campaign can be cancelled up to its departure and goes back to draft.

Send yourself a test first. A test delivers the real thing to one address, with sample data and a harmless unsubscribe link. It costs a real send against your quota, and it counts in no statistic. It is the only way to see what a mail client will actually do with your HTML.

Each campaign can be signed by a specific sender identity; without one, the organization's default is used.

What refuses

Sending is refused, with the reason named, when marketing sending is paused across AgentsMail, when your organization is not allowed to send, when your domain is not verified, or when your balance is short — the message says how many units are missing. In every one of these cases the draft is intact and no email left. The full list, and what to do about each, is on why a send is refused.

What it implies elsewhere

The unsubscribe link is verified, never injected: if the rendered HTML does not contain {{unsubscribeUrl}}, the send is refused. Nothing is appended to your markup on your behalf. Everything above works over HTTP as well — creating a campaign, checking its rendering, triggering it. See Content & Send.