Email Campaigns

Email campaigns let you reach the people in your contacts CRM. Build an audience, compose a send, and Aglyn handles delivery, caps, and unsubscribes.

Plan availability

Paid, with tiered send caps — how many emails you can send per period depends on your plan.

Send a campaign

1. Build an audience — leads, site members, segments, or an email list.
2. Compose the campaign from the Marketing page.
3. Send — subject to your plan's send cap.

Your monthly send cap

Every plan includes a number of campaign emails per calendar month. The count resets on the 1st; it does not roll over.

Only campaigns count against it. Transactional mail — order confirmations, booking reminders, password resets, teammate invites, workflow notifications — is never refused by this cap on any plan. A busy month of orders cannot use up your campaign allowance, and reaching the cap never stops a receipt from reaching a buyer.

You can see where you stand in two places, without having to be refused first:

• In the composer, under the recipient count: 340/500 campaign emails this month.
• On the Billing page, as the Campaign emails (this month) meter, per site.

The cap is counted per site, so each site in your organization has its own allowance. One recipient is one email: a campaign to 200 people spends 200.

When a send would take you past the cap, the composer says so while you are still writing rather than after you press Send. Upgrade your plan or shrink the audience.

Personalize with merge tags

Use {{name}}, {{firstName}}, or {{email}} anywhere in the subject or body — they resolve per recipient at send time from the audience's stored details. Add a fallback with a pipe for recipients without a stored name: Hi {{firstName|there}}!.

See who it will reach, before you send

As soon as you pick an audience the composer counts it, and shows the count under the audience picker:

Recipients 1,240 · 12 unsubscribed

The number is not an estimate. It is produced by running the real send path with nothing written — the same audience resolution, the same de-duplication, the same suppression list, and the same monthly cap — and stopping immediately before the first write. Nothing is created, no counter moves, and no campaign appears in your history.

That means the count already reflects things you would otherwise only discover afterwards:

• Duplicates are removed. One person on two lists is one recipient.
• Unsubscribes are removed, and reported separately as · 12 unsubscribed, so a smaller-than-expected number has a visible reason.
• A single send is capped at 500 recipients. A larger audience is counted at the cap.
• A refusal appears here rather than at send time. An empty audience, an audience where everyone has unsubscribed, or a month already at your plan's send cap all say so while you are still writing.

While it works it reads Counting recipients…. It re-counts whenever you change the audience.

Counting an audience needs the same permission as sending to it — the size of someone else's site's audience is not public information.

Schedule a send

Pick a Send at time in the composer and the button becomes Schedule campaign. Scheduled campaigns appear in history with a Scheduled chip and a Cancel action until the send time; they deliver through the same caps, suppression list, and merge tags as an immediate send.

Three things about the timing are worth knowing:

• Due campaigns are picked up every 15 minutes, so a send scheduled for 09:00 goes out between 09:00 and about 09:15. Schedule to the quarter hour if the exact minute matters.
• The time is your browser's local time at the moment you set it, stored as an absolute instant. Someone in another timezone reading the history sees the same instant in theirs.
• A scheduled campaign is checked against your caps when it actually sends, not when you schedule it. A month that has since reached its send cap makes the campaign fail rather than send, and it appears in history with a Failed chip carrying the reason.

The statuses a scheduled campaign moves through are Scheduled → sending → sent, or Canceled if you cancel it in time, or Failed with the reason.

Email lists

Lists are static audiences shared across your organization's sites. Create them on the Marketing page, then grow them with the "Enroll in a list" automation step (e.g. on form completion) or popup email capture. Target any list from the campaign composer.

Experiments

Business plans can A/B test screens, sections, and emails from the Experiments card on the Marketing page: weighted variants, deterministic visitor assignment, a conversion goal, and per-variant exposure/conversion rates with a pick-the-winner flow.

Two ways to finish a test without watching it:

• End date — past it, visitors get the default and stats stop accruing until you pick a winner.

• Auto-declare winner — opt in with a minimum exposure count per variant and a confidence level (90/95/99%); once a challenger clears the bar (or every challenger confidently loses to the control), the experiment completes itself and serves the winner. Auto-completed tests carry a chip in the results dialog.

• Screens & sections — variants pin a screen version; visitors are split deterministically and the winning version serves to everyone once you pick it. Start a section test straight from the Besigner's Interactions panel.

• Emails — variants override the campaign's subject and/or body. Attach a running email experiment in the campaign composer; each recipient deterministically receives one variant (re-sends reach the same variant), sends count as exposures, and once a winner is picked every later send uses the winning copy.

Opens & clicks

With the Resend webhook configured, campaign history shows opens and clicks per campaign, and clicks on A/B sends count as that variant's conversions — so the experiment results table fills in by itself.

Compliance

• Every send includes an unsubscribe link, and the header mailbox providers look for — Gmail and Yahoo's one-click List-Unsubscribe.
• Clicking it opens a confirmation page; only confirming actually unsubscribes. That matters because corporate mail scanners open every link in a message before the recipient sees it, and a link that unsubscribed on open would quietly shrink your list.
• Unsubscribes are honored automatically so you stay compliant.

Suppressions

Emails ▸ Suppressions lists every address your campaigns skip, with the reason and the date:

Reason	What happened
Unsubscribed	They clicked the unsubscribe link.
Bounced	The mailbox does not exist. Recorded only for a permanent bounce — a full mailbox or a temporary server problem never suppresses anybody.
Marked as spam	They reported a message.

This is where the gap between a campaign's recipient count and what it actually sent comes from, and a rising Bounced count is the earliest sign a list is going stale.

Remove puts an address back on your list — use it when somebody asks to be re-added, or when a suppression was recorded by mistake. Removing a bounced address means your next campaign will try a mailbox that has already said it does not exist, which mailbox providers hold against your sending reputation, so the confirmation names the reason before you do it.

Related

• Contacts CRM
• Forms & lead capture
• Marketing overlays (email capture popups)