SendForever help
Log in Get started

Help Campaigns

Campaigns

A campaign sends one template to everyone subscribed to one audience. It goes out from one of your domains and runs entirely inside your AWS account. This page covers how to create, duplicate, check, test, send, schedule, pause and stop a campaign, the automatic stop on bounces and complaints, and the report.

What a campaign is

All of a campaign's sending runs inside your AWS account:

  • The email is an Amazon SES template, which holds the subject, the content and the preview text. See Templates.
  • The recipients are an audience of the campaign's domain. Audiences are kept in the contacts table in your AWS account. See Audiences and contacts.
  • Each email's unsubscribe link points to the domain's links host and opens the domain's preferences page there. See Domains.
  • An AWS Step Functions state machine named sendforever-campaigns does the sending. Each campaign is one execution of it, named campaign- followed by the campaign's ID. The ID is at the end of the campaign page's address. The workflow runs as the IAM role sendforever-campaigns. That role can send through Amazon SES, read the audience from the contacts table, and read the campaign's own bounces and complaints.
  • An Amazon EventBridge Scheduler schedule starts a scheduled campaign. The schedule is in the schedule group sendforever, has the same campaign- name, and runs as the IAM role sendforever-campaign-schedules.
  • When you open the report, SendForever reads it from the activity log with Amazon Athena.

SendForever only starts, schedules and stops the workflow, and checks its progress while you have the page open. The work happens in your account, so a campaign keeps going after you close the page. SendForever defines and updates the state machine itself. If you change it in the AWS console, SendForever replaces your changes.

Campaigns are in each domain's Campaigns section. The list shows up to 100 campaigns of the domain chosen in the header, latest first. Its columns are Name, Status, Audience and When, and you can sort by any of them.

Who can do what

Team owners and admins can create, duplicate, edit, test, send, schedule, pause, resume, stop and delete campaigns. Members can open campaigns and read their reports, but cannot change them. See Teams and members.

What you need first

  • A connected AWS account. See Your AWS account.
  • A domain with its links host in use. A campaign belongs to the domain it is sent from, and its unsubscribe links point to that host. See Domains.
  • A template with an unsubscribe link.
  • An audience of the domain with people subscribed to it.

Create a campaign

  1. Choose the domain in the header, then open Campaigns.
  2. Click New campaign.
  3. Fill in the fields below. Each field saves as soon as you change it, and SendForever shows "Campaign saved." The campaign is not kept until you fill something in. Until you name it, it is called "Untitled campaign".

The new campaign is sent from the domain chosen in the header. You cannot move it to another domain.

Fields

  • Name: what the campaign is called in SendForever. Recipients never see it.
  • Template: the template to send. It holds the subject and the email. Edit followed by the template's name opens it. An isolated domain offers its own templates. A domain that is not isolated offers the templates of your AWS account.
  • Audience: who gets the campaign. The list offers only the audiences of the campaign's domain.
  • From name: the sender name people see, such as Example News. It is optional, up to 100 characters. A new campaign starts with the domain's Sender name (see Domains).
  • From address: the part before the @. The part after it is the campaign's own domain. It starts as newsletter. It can have up to 64 lowercase letters, numbers, dots, dashes, underscores and plus signs.
  • Reply to: where replies go. It is optional. Without it, replies go to the from address.
  • Pace: how fast the campaign goes out. See below.

Pace

Pace limits how many emails an hour the campaign sends:

  • As fast as the account allows (the default): as fast as your Amazon SES sending rate allows. SendForever matches the sending to the account's maximum send rate and retries when Amazon SES throttles.
  • Up to 500 an hour, Up to 1,000 an hour, Up to 2,500 an hour, Up to 5,000 an hour or Up to 10,000 an hour.

With a pace, the workflow reads up to 15 minutes' worth of people at a time and waits between those pages. Mailbox providers trust a new domain sooner when it sends at a steady pace than in one burst. A pace helps when you warm up a domain.

Preview

Once you choose a template, the campaign's page shows the email below the form, as an inbox lists it: the sender, the subject and the preview text. The email itself follows.

Duplicate a campaign

To send a campaign again, or a similar one, duplicate it. Choose Duplicate in its row's actions menu in the Campaigns list, or Duplicate campaign in the campaign's actions menu. You can duplicate any campaign, even one that is scheduled or sending.

The copy is a new draft with the same template, audience, from name and address, reply-to and pace. Its name is the original's with "(copy)" at the end, and it opens at once. None of the original's sending carries over. Send yourself a test of the copy, then send or schedule it.

Checks before sending

The Before sending card lists what SendForever checked. A red mark is a failing check. It blocks Send and Schedule until you fix it. An amber mark is a warning. SendForever points it out and leaves the choice to you. While a check fails, hover over the disabled Send or Schedule button to see the first failing check.

SendForever runs the checks against what your AWS account holds. It runs them when the page opens, when you change the template or audience, and again when you click Send now or Schedule. If a check fails at that last moment, nothing is sent and the page says "Fix what the checks ask for first."

Checks that block sending

  • Domain: the domain must be ready to send, with nothing failing or still pending on its page. If you or Amazon SES paused sending for the domain, the check says so. Click Resume sending in the domain's Settings first. See Domains.
  • Production access: an Amazon SES account in the sandbox only delivers to verified addresses, so it would refuse your audience. The check says which case applies: you still need to request production access on the AWS account page, AWS is still reviewing the request, or AWS declined it. If AWS declined, it explains why in the AWS Support Center. While AWS reviews the request, the campaign page reads AWS's answer each time it opens. The campaign can go out once AWS approves. See Production access.
  • Activity log: the configuration set the domain sends through must record to the activity log. The campaign's report and its automatic stop on bounces and complaints read from that log. If it does not record, open Activity and click Start recording.
  • Links host: the domain's links host must be in use, because every email's unsubscribe link points there. The check tells you when the domain has no links host, when it is still being set up, or when it could not be set up, and links to the domain's configuration. See Domains.
  • Audience: choose an audience of the campaign's domain that still exists and has at least one person subscribed. SendForever counts the audience in the contacts table each time it checks. For a very big audience, it shows the number counted with a "+". If SendForever cannot count the audience, this check becomes a warning, and the campaign goes to everyone subscribed when it starts.
  • Template: choose a template that Amazon SES still has. The checks on the template's content, below, appear once this one passes.
  • Unsubscribe link: the HTML must contain {{amazonSESUnsubscribeUrl}}. Each email fills it with the person's own unsubscribe link on the domain's links host. To add it, click Add next to "No unsubscribe link" in the For campaigns bar under the template's editor, or use the editor's Insert menu. If the HTML has the link but a text version does not, this is only a warning. Add {{amazonSESUnsubscribeUrl}} to the text version, or let SendForever make the text version from the HTML.
  • Variables: a campaign fills only {{email}} (the person's address), {{name}} (their name, or nothing if they have none) and {{amazonSESUnsubscribeUrl}}. Amazon SES drops every email whose template uses any other variable, such as {{firstName}}. Remove those variables from the template.
  • Size: the HTML must be 102 KB or less. Gmail clips larger emails and hides the unsubscribe link at the bottom. Shorten the email or use fewer inline images.

Warnings

  • Preview text: without it, inboxes show the first words of the email beside the subject. In a template written in SendForever's editor, fill in Preview text under the subject. In HTML made with another email builder, a hidden preview block (an element styled display:none) also counts.
  • Postal address: the CAN-SPAM Act asks for a postal address in every marketing email. Enter the team's address under Postal address in the team's Settings. Then add it to the template with Add next to "No postal address" under the editor, or from the Insert menu. SendForever looks for the address in the email's text, however its lines are broken.
  • Subject: most inboxes cut off a subject over 70 characters. A subject in all capitals reads as shouting and makes spam filters wary.
  • Links: a link that goes nowhere (empty, # or a script), or that goes to an address without https:// and a domain, to an example domain such as example.com, or to a test or local address such as localhost. The warning names the first three such links. The check skips email links (mailto:), phone links (tel:), links to a place in the email, and links Amazon SES fills in, such as the unsubscribe link.
  • Placeholder text: "Lorem ipsum", or words in brackets such as [First name], [Company Name] or [Insert link], left in the subject or the email.
  • Test: shown until you send yourself a test of the campaign.
  • Daily quota: the campaign would send more emails in the next 24 hours than your Amazon SES account's daily sending quota has left. It stops when the quota runs out, and you can resume it where it stopped once the quota allows. To send it in one go, ask AWS for a higher sending quota in the Amazon SES console first, or choose a slower pace. A pace counts here as the emails it sends in 24 hours.
  • Transactional domain: campaigns from a domain meant for transactional email can hurt the delivery of its receipts and password resets. A marketing subdomain keeps them apart.
  • Isolation: on a domain that is not isolated, complaints about a campaign count against the whole account. Isolating the domain (Isolate this domain in its Settings) lets Amazon SES pause only that domain.
  • DMARC: a domain with DMARC at p=none meets Gmail's and Yahoo's requirements, but a stricter policy protects it from people who send as the domain. See DNS records.

Send a test

Click Test to send the campaign's email to yourself, at the address you sign in with. The button stays disabled until you choose a template.

  • The test sends the template from Amazon SES by name, so blocks such as {{#if name}} are filled as they are in the campaign. It uses the template's subject and content as stored in Amazon SES, and the campaign's from address, name and reply-to. {{email}} becomes your address and {{name}} becomes your name.
  • The unsubscribe link opens a page on the domain's links host. The page says it comes from a test and changes nothing, because a test goes to nobody in the audience. If the domain has no links host in use, the link is filled with its own name in square brackets and does not work.
  • It goes through the domain's configuration set, so it also appears in Activity.
  • A domain sends up to 5 test emails an hour.
  • If your Amazon SES account is still in the sandbox and your address is not verified, Amazon SES emails your address a verification link instead. Open the link, then send the test again.

Send now or schedule

Send now

  1. Click Send.
  2. The dialog shows how many people the campaign goes to. Once sending starts, you cannot undo it.
  3. Click Send now.

The campaign goes to everyone subscribed to the audience when it starts.

Schedule

  1. Click Schedule.
  2. Under Send it on, choose the date and time. The time is in your browser's time zone, shown under the field as Time zone.
  3. Click Schedule.

The time must be between five minutes and a year from now. SendForever creates a schedule in Amazon EventBridge Scheduler in your account. The schedule starts the campaign at that time, even with SendForever closed, and deletes itself once it has run. The campaign page then shows the scheduled time with its time zone.

You cannot edit a scheduled campaign. To change it, click Cancel the schedule. The campaign becomes a draft again, so you can edit it and schedule it again.

While it sends

While the status is Sending, the campaign page shows its progress and updates every 15 seconds, for example "About 562 emails handed to Amazon SES so far." You can close the page.

When it starts, the workflow looks up where the domain's links answer. It then reads the audience from the contacts table in pages of up to 500 people and sends each person their own email through Amazon SES:

  • Each email has the person's own unsubscribe link for the audience and the campaign. The link is in the email and in the List-Unsubscribe and List-Unsubscribe-Post headers that Gmail and Yahoo use for one-click unsubscribe. It opens the domain's preferences page on its links host. One-click unsubscribe takes the person off that audience at once. When you save a template, SendForever keeps that link out of click tracking, so unsubscribing never counts as a click.
  • If the domain's links host is not in use when the campaign starts, the campaign stops before sending anything.
  • Each email goes through the domain's configuration set, and through its tenant when the domain is isolated.
  • Each email carries the message tag campaign with the campaign's ID, which the activity log and the report read. Amazon SES gives each email a Feedback-ID header of its own, for Gmail's complaint feedback, and replaces any other.
  • Right before each email, the workflow reads again whether the person is still subscribed to the audience. It skips anyone who left or was forgotten since their page was read, such as while a failed campaign waited to be resumed.
  • If Amazon SES throttles or fails briefly, the workflow retries. If Amazon SES refuses one address, the workflow skips it and continues. If Amazon SES refuses every email in a batch, the campaign stops instead of skipping the whole audience.
  • With a pace, the page says how fast it goes, for example "at up to 500 an hour".
  • Between two pages, the workflow checks whether the campaign is paused (see Pause and resume).

The first slice and the automatic stop

To protect your domain from a bad list, the workflow first sends a slice:

  1. Once 1,000 or more emails have gone out and more people are left, it waits one hour. That is long enough for most bounces and the first complaints to come back. The page says "The first 1,248 emails went out. The rest wait an hour, until their bounces and complaints are back, and go only if those stay low." (The number depends on the page size.)
  2. It then reads the campaign's bounces and complaints from the activity log with Amazon Athena, in the sendforever workgroup.
  3. It reads them again every 5,000 emails after that, without waiting.

The campaign stops for good when either of these is true:

  • Permanent bounces reach 3% of the emails Amazon SES attempted. This only counts once there are at least 10 bounces.
  • Complaints reach 0.08% of the emails Amazon SES attempted. This only counts once there are at least 3 complaints.

Amazon SES does not try some addresses at all, because they are on a suppression list, failed its address validation or unsubscribed. These count neither as bounces nor as attempted emails. For comparison, Amazon SES starts reviewing an account at a 5% bounce rate or a 0.1% complaint rate.

If nobody is left after the first slice, there is no wait. The checks read the activity log, so they only see a domain's emails if the activity log records them (see Activity).

When the workflow stops a campaign this way:

  • The campaign's status becomes Failed, with the reason.
  • The team's owners and admins get an email whose subject names the team and the campaign, such as "[Acme] Spring sale stopped". It gives the bounce and complaint rates at the moment the campaign stopped and has a Review the campaign button.
  • Emails already sent stay sent.

Pause and resume

  1. Open the campaign while it is sending.
  2. Click Pause.

The status becomes Paused at once. The workflow stops between two pages of the audience. Emails already handed to Amazon SES, up to one page of 500, still go out, and nobody else gets the campaign. If the workflow is waiting for its pace or for the first slice's bounces, nothing is being sent anyway.

To continue, open the campaign and click Resume. It picks up where it stopped, with the next page, and nobody it already reached gets it twice. AWS keeps the paused run for 14 days, and the page shows until when. After that, the campaign can only be stopped. To end a paused campaign for good, click Stop sending.

To pause, SendForever writes an item in the contacts table of your AWS account, with the key CAMPAIGN# followed by the campaign's ID. The workflow reads that item before each page. Resuming deletes the item and has AWS run the workflow again from that read.

Stop a campaign

  1. Open the campaign while it is sending or paused.
  2. Click Stop sending and confirm.

Emails already sent stay sent. The status becomes Stopped, and a stopped campaign cannot be resumed. If someone stops the execution in the Step Functions console instead, SendForever also shows the campaign as Stopped.

Statuses

Status What it means
Draft Not sent or scheduled yet. Only a draft can be edited.
Scheduled Waiting for its EventBridge Scheduler schedule to start it.
Sending The workflow is running in your account.
Paused Someone paused it. If resumed within 14 days, it continues from where it stopped.
Sent The workflow reached everyone in the audience.
Stopped Someone stopped it.
Failed It did not finish. The page says why under "The campaign did not finish".

SendForever reads the status from AWS when you open the campaign or the Campaigns list, never in the background.

A campaign fails, for example, when:

  • Too many of its emails bounced or drew complaints (see above).
  • Amazon SES refused every email in a batch. Check the template and the domain.
  • Amazon SES paused sending for the account or the domain, or suspended the account.
  • The account reached its daily sending quota in Amazon SES.
  • The domain's MAIL FROM is no longer verified in Amazon SES.
  • Amazon SES no longer has the template the campaign uses.
  • The domain had no links host in use when the campaign started.
  • The contacts table in your AWS account could not be read.
  • The schedule ended without starting the campaign, because someone deleted it in the AWS console or AWS refused to start it.

The report

Once a campaign has started, its page shows What happened, read from the activity log in your AWS account:

  • Sent: emails Amazon SES accepted.
  • Delivered: emails the receiving server accepted.
  • Opened and Clicked: emails opened or clicked at least once. Each email counts once, however often it was opened or clicked.
  • Bounced: emails that bounced, not counting suppressed ones.
  • Suppressed: addresses Amazon SES did not try, because they bounced or complained before.
  • Complaints: people who marked the email as spam.
  • Unsubscribed: people who unsubscribed through the campaign's unsubscribe link or headers.

Each figure after Sent also shows its share of the emails sent. Once the activity log has earlier campaigns of the domain, each figure also shows the Average share of up to the 10 latest of them, each weighted equally. Opens and clicks keep arriving for a few days after a campaign goes out, so until then a recent campaign trails an average of older ones.

When the campaign went to more than one mailbox provider, a table breaks it down by Mailbox provider: Gmail, Outlook, Yahoo and AOL, iCloud, and Other. Other is everyone on a company domain or a smaller provider. For each provider, the table shows how many emails were sent and what share of them were delivered, opened, clicked, bounced or drew complaints.

Below the figures, Opens and clicks, hour by hour charts the campaign's first three days in UTC, from the hour it started up to the current hour. Each email counts once in the hour it was first opened, and once in the hour it was first clicked. The chart is read from the activity log once the figures are on screen.

Clicks by link lists up to 50 links people clicked, most clicked first. Clicked is the number of emails in which a link was clicked, each email counted once however often. Links Amazon SES does not track, such as the unsubscribe link, are not listed.

See each email, beside What happened, opens Activity with only this campaign's emails, over the days it went out, each with its status. There you can filter them by status, for example to see who bounced, or export them. The button is there for 90 days after the campaign finished, while the bucket still keeps its events.

The report shows how recent it is ("as of"). SendForever reads it from the activity log at most every 15 minutes, and every minute while the campaign sends and in the hour after it finishes, since its emails reach the log a minute or two after they go out. Opens and clicks count only if the domain tracks them. Turn tracking on with Track opens and clicks in the domain's Settings.

Delete a campaign

Delete a campaign with Delete in its row's actions menu in the Campaigns list, or with Delete campaign in the campaign's actions menu. You cannot delete a scheduled or sending campaign. Cancel its schedule or stop it first. A deleted campaign's emails and their events stay in your AWS account.

What a campaign costs in AWS

AWS bills your account directly. Amazon SES bills each campaign email like any other email. The What AWS bills you section of the AWS account page estimates a month of sending. Beyond Amazon SES, a campaign uses AWS Step Functions for the sending, Amazon DynamoDB to read the audience, Amazon EventBridge Scheduler for a scheduled start, and Amazon Athena for the report and the automatic stop's checks. As that page notes, the activity log, the webhook, alerts and campaigns add cents at most, mostly within AWS's free tier.

Campaigns through the API

You can also create, duplicate, test, send, schedule, pause, resume, stop and delete campaigns, and read their reports and the links clicked in them, through the SendForever API and MCP server. The same checks must pass before a campaign is sent or scheduled. See API and MCP.

Common questions

Why are Send and Schedule disabled?

At least one check in Before sending fails. Hover over either button to see the first failing check, and fix what the card lists. Warnings never disable the buttons. If the buttons are missing, you may be a member rather than an owner or admin, or the campaign is no longer a draft.

How do I send a campaign again?

A campaign goes out only once. To send it again, duplicate it. The copy is a new draft with the same settings, ready to test, send or schedule. See Duplicate a campaign.

Why doesn't my audience or template appear in the list?

A campaign offers only the audiences of its domain, and an isolated domain offers only its own templates. Check that the domain chosen in the header is the one you want to send from.

How do I send to only part of an audience?

A campaign always goes to everyone subscribed to one audience. To reach a smaller group, create a separate audience with those people, then send the campaign to it. See Audiences and contacts.

Why didn't someone get the campaign?

The campaign goes to the people subscribed to the audience in the contacts table, the same people the audience page lists as subscribed. It leaves out people who unsubscribed from the audience or from everything the domain sends. Amazon SES does not try addresses on a suppression list, and they appear as Suppressed in the report. Amazon SES may also have refused the address, and the workflow skips refused addresses. Look the person up in Activity.

My campaign stopped for too many bounces or complaints. What now?

The workflow found that permanent bounces reached 3%, or complaints reached 0.08%, of the emails sent so far. It stopped the campaign before Amazon SES put the account under review. For bounces, remove the addresses that bounced before you send to this audience again. The activity log lists them. For complaints, check that everyone in the audience asked for these emails.

Can I resume a stopped or failed campaign?

You can resume a paused campaign within 14 days. It continues from where it stopped and sends nobody the campaign twice (see Pause and resume). You can also resume a failed campaign within 14 days, with Resume on its page, and it continues from where it failed. People it already reached get nothing twice, except for the batches in progress when it failed, of up to 25 emails each, which go out again. You cannot resume a campaign that stopped for too many bounces or complaints, or one you stopped yourself. A new campaign to the same audience goes to everyone subscribed to it again, including the people who already got the first one.

How big an audience can one campaign reach?

About 543,000 people, because AWS limits how long a workflow run can be. A pace lowers that limit, because each page of people is smaller: about 135,000 at 500 an hour, and about 271,000 at 1,000 an hour. A bigger audience fails the audience check before anything is sent. Split it, or choose a faster pace if there is one.

Why does my campaign still say Sending after a long time?

After the first 1,000 or so emails, the workflow waits an hour for bounces and complaints before it sends the rest. A pace also adds waits between pages. The page says when the campaign is waiting for either. SendForever reads the status only when you open the campaign or the list, so open the campaign to see its progress.

Why do opens look high?

Apple Mail can open emails on its own, which inflates open rates. Watch the trend rather than the number. Each email counts as opened once, however often it was opened.

Why does the report show no opens or clicks, or nothing at all?

Opens and clicks count only if the domain tracks them. Turn on Track opens and clicks in the domain's Settings. If the report is empty, check Activity. If it says the domain's emails are not being recorded yet, click Start recording. Emails sent before that do not appear. The report can also be up to 15 minutes old.

Can I change a campaign after scheduling it?

Not while it is scheduled. Click Cancel the schedule to make it a draft again, change it, and schedule it again.

Why does the test fail or not arrive?

A domain sends up to 5 test emails an hour. If your Amazon SES account is in the sandbox, Amazon SES first emails your address a link to verify it. Open the link, then send the test again. The link expires after a day.

Can I send a campaign from a different domain?

A campaign is sent from the domain chosen in the header when you created it, and you cannot move it. Choose the other domain in the header and create a new campaign there.

Still stuck?

, which answers from these pages.

No page or section has those words.

Ask AI

ChatGPT or Claude answers in a new tab, from the SendForever docs. Only your question goes with it, nothing about your team.

Or read the help center

ChatGPT Claude