Platform DocumentationE-mail Campaigns

E-mail Campaigns

Sidebar: E-mails → Campaigns

Module: E-mail marketing — Plus and Prime.

A campaign is a bulk dispatch that runs on FlyB’s servers. You schedule it once and close the tab — logging out or losing your connection changes nothing.

This is the difference between a campaign and the immediate bulk send available from the Contacts screen, which runs in your browser and stops when the tab closes.

Campaigns require a paid plan and a configured SMTP server. Every message counts against your plan’s monthly e-mail allowance — going over it never stops a campaign mid-list, it only tells the account owner.

Creating a campaign

The campaign form is a short sequence of steps — E-mail, When, Engagement automation, Who receives it and Review and schedule. Each step says whether it is complete, Continue stays disabled until it is, and the review lists every answer with a Change link back to the step that decides it.

Who receives it

A campaign is always defined by its audience, so that is the first question. You can start from:

  • A filter or a CRM stage — open the campaign from that screen and the cohort comes with it
  • Everyone in my base — every contact in the organization
  • A filter built on the spot — the same condition builder as Contacts, without having to save the filter
  • The same contacts as an existing campaign — re-mailing a list you already curated is the most common follow-up

A member restricted to their own contacts builds every one of these cohorts over their own leads only — “everyone in my base” included. See Settings & Team.

The list is frozen

Creating a campaign takes a snapshot of the audience. It is not a filter that re-runs at send time. If someone new starts matching the filter tomorrow, they are not added — because you curated that list, and the campaign should send to the people you chose.

Preflight

Before you confirm, FlyB tells you how many contacts will actually be mailed and why the others will not:

  • no address
  • unsubscribed
  • blocked address (a previous hard bounce or spam complaint)
  • already received this e-mail in the last 24 hours
  • not found

Those contacts stay on the campaign, recorded as skipped with the reason, so you can always answer “why didn’t so-and-so get it?”.

What goes out

Pick the template. See E-mails & Templates. The step also tells you how many of the template’s buttons have click tracking on — that is what click-based automation rules and the click rate can use.

When it goes out

Send now starts within the next minute. Schedule takes a date, a time and a time zone — the campaign is stored as a wall-clock time plus a zone, so a daylight-saving change never shifts it.

Best time to send reads when your audience actually opens e-mail, bucketed by hour in the zone you selected, and offers that hour in one click. It is reported as a peak, never an average, and is withheld until there are enough opens to mean something.

A campaign that never started refuses to go out excessively late — a “today only” blast sent two days later is the one mistake you cannot undo.

Engagement automation

Prime plan. On Plus the step is shown, locked, and the campaign goes out without it.

An engagement automation is the set of e-mails a campaign sends on its own, after the first one, depending on what each contact did with the previous e-mail. Each rule is one sentence:

Wait 3 days after the campaign e-mail — if the contact did not open it — send “Reminder”.

PartOptions
Wait1 hour to 90 days, in hours or days
AfterThe campaign’s own e-mail, or the e-mail another rule sends — that is how a sequence is built
If the contactOpened the e-mail · Did not open it · Clicked a button · Opened but did not click · Did not click
ButtonFor the click conditions: any button, or one tracked button of the e-mail being watched, listed by its label
SendAny of your templates — including the campaign’s own, to resend it

For example, a complete sequence:

RuleWaitAfterIf the contactSend
13 daysthe campaign e-mailclicked “See pricing”Offer
23 daysthe campaign e-mailopened but did not clickReminder
33 daysthe campaign e-maildid not openthe campaign e-mail again
44 daysthe e-mail of Rule 3did not openLast call

A rule that watches another rule’s e-mail sits indented under it, with the day it happens on. Three ready-made models — resend to non-openers, follow up with clickers and the full sequence above — fill the rules in one click, and you only pick the e-mails.

How it runs

  • Each rule is checked once, at its exact moment, for each contact. When the e-mail a rule watches is sent to a contact, FlyB schedules one check for that contact at send time + wait. Nothing is checked before then, and once checked it is never looked at again: “condition not met” is final, and nobody receives the same follow-up twice.
  • A rule that watches another rule’s e-mail only exists for the contacts who received that e-mail.
  • A click also counts as an open: someone who clicked a button obviously read the e-mail, even if their mail app blocked the invisible image that measures opens.
  • Follow-ups go out at the campaign’s own pace — the same gap between sends, and at most the campaign’s average rate (per-batch amount over the pause) — so a backlog never becomes a burst.
  • Follow-ups go through the same checks as every e-mail: a contact who unsubscribed, or whose address bounced, since the campaign e-mail is skipped with the reason. So is a contact whose campaign e-mail bounced or was reported as spam.
  • A follow-up checked more than 48 hours after its moment (for example, after the campaign was paused for a weekend) is skipped rather than sent late, with the lateness in the reason.

Pausing the campaign pauses its automation too; cancelling it — or the circuit breaker stopping it — ends the automation. On a finished campaign, Stop automation cancels whatever is still scheduled; it can also be used while the campaign is still sending, so no follow-up is scheduled from then on. The rules themselves are fixed when you create the campaign, like the pacing.

Opens are estimated with an invisible image — some apps open e-mails on their own (Apple Mail) and others block images — so clicks on tracked buttons are the most reliable condition to build a sequence on.

What FlyB refuses to save

The automation is checked as you write it, and the campaign cannot be scheduled while any rule is marked in red:

  • Loops — a rule that waits on its own e-mail, directly or through other rules
  • A rule that waits on the e-mail of a rule that no longer exists
  • A chain more than 5 e-mails deep, or more than 20 rules in total
  • A rule with no e-mail to send, or a wait outside 1 hour – 90 days
  • A click condition on an e-mail that has no tracked button, or on a button that is not in the e-mail being watched, or whose tracking is off
  • Two e-mails at the same moment — two rules that one contact could satisfy together and that would reach them at the same instant (for example “3 days, opened” and “3 days, clicked”: whoever clicked also opened). Change a wait, or split the audience with conditions that cannot overlap, such as clicked / opened but did not click / did not open
  • The same e-mail twice — two rules on separate branches that one contact could both satisfy and that send the same template. (Re-sending an e-mail further down the same chain — “did not open it, send it again” — is allowed.)
  • Re-sending the watched e-mail within 24 hours while duplicate protection is on: every contact would be skipped

Sending speed and safety

Every pacing value is copied onto the campaign when you create it. A running campaign cannot change shape under you, and a campaign from last month stays explainable by its own settings.

Rate

SettingWhat it controlsRange
Per batchE-mails sent before pausing1 – 1000
Pause (min)How long between batches5 – 1440
Gap (ms)Delay between individual sends (100 ms = 10/s)100 – 60000

Batching is what keeps Gmail and Outlook calm, and the pause also gives bounces time to arrive before the next batch goes out.

Safety — the circuit breaker

Before each new batch, FlyB checks how the previous one landed. Three guards, each reading a different denominator on purpose:

GuardMeasured overWhy
Max failures (%)The last batchCatches a broken configuration on the first 200 e-mails, not the first 2,000
Max bounces (%)Everything sent so farBounces arrive asynchronously during the pause
Max spam reports (%)Everything sent so farSame — and this is the one that damages your domain

If any guard trips, the campaign stops on its own and writes down why, as a sentence with the numbers in it, on the campaign and on every recipient it did not reach.

Duplicate protection

Do not re-send to contacts who got this e-mail in the last 24h is on by default. Turn it off only when you are deliberately sending the same e-mail twice.

While it runs

StatusMeaning
ScheduledWaiting for its moment
SendingIn progress
PausedPaused by you
FinishedCompleted
CanceledCancelled by you
StoppedHalted by the circuit breaker to protect your reputation
FailedCould not run

The campaign detail shows the progress, the current batch, the next batch time, the estimated time remaining, opens, clicks, bounces, and the full recipient list with each recipient’s status (will receive, queued, sending, sent, failed, skipped, cancelled), batch number, whether they opened or clicked, and how many follow-ups they received.

Open and click rates count the campaign’s own e-mail only. With an engagement automation, the detail also lists every rule with what it has done so far — scheduled, waiting, sent, did not meet the condition, skipped, failed, cancelled — the open and click rates of the follow-ups it sent, and when its next check is. The campaign list shows the automation too, so a campaign can read Finished for its first e-mail while its follow-ups still have days to run.

You can pause, resume or cancel at any time — cancelling asks for confirmation, because the contacts still queued will not receive the e-mail. Stop automation also asks first.

Deleting a campaign removes it and its recipient list. A finished campaign whose automation still has follow-ups scheduled must have its automation stopped first. The e-mails that really went out stay in your delivery report, where follow-ups are marked with the rule that sent them.

Marketing versus transactional

The delivery report separates the two: an e-mail sent by a campaign carries its campaign identifier, and an e-mail sent by an automation or by hand does not. That is how you read your marketing volume apart from your transactional traffic.

Your obligations

Bulk e-mail is the feature most likely to get an account suspended, and the rules are not negotiable: a lawful basis for every recipient, no bought or scraped lists, a working unsubscribe link, honest subject lines and sender identity. Read the Acceptable Use Policy before your first campaign.