Email campaigns are designed for sending targeted bulk emails to your contact groups. Each campaign supports personalization, open/click tracking, A/B subject testing, automated follow-up sequences, and detailed analytics.

Click New Campaign to open the campaign wizard:

1. Content: write your email subject and body with personalization variables like {{first_name}} and {{company}}. This step also carries the plain-text option.
2. Recipients: select a contact group or add manual recipients.
3. Sequence: add automated follow-up stages triggered by recipient behavior (no reply, no open, no click), set how long each stage waits, choose whether a stage replies in thread, and pick what stops the sequence early.
4. A/B test: test subject lines, or write full versions of the email.
5. Review: choose your sending email, set tracking and category, schedule the send, and clear anything the send blockers list there.

Above the toolbar on the Campaigns list sits one quiet line about your sending. It shows one of these, and nothing else:

• Everything is fine. A muted line reads Sending from your address, then how many of that mailbox’s daily sends are still available, for example 1,240 of 2,000 daily sends available. With more than one mailbox connected, the extras are counted as +2 more beside the first address. The remaining number turns amber once it reaches zero.
• A campaign has been paused. An amber line names the campaign and why: it hit its daily send limit at your mail provider, or it was paused by the safety circuit-breaker. It ends with It will resume on its own when the quota resets. and links straight to that campaign.
• All sending is paused for the workspace. An amber line reads Sending is paused for this workspace by automatic safety protection, and says that campaigns and follow-ups are both on hold. It names the check that fired, with the measured figure and the limit it crossed, and asks you to review the audience and the recent sends and then contact support to lift it. This one does not clear itself.
• No mailbox is connected. An amber line reads Connect a mailbox to send campaigns and opens your integrations settings.
• Nothing at all. If the check has not answered yet, or could not work out your posture, the line is simply absent. It never guesses: an empty row would be a claim that you have no mailbox, and that claim would sit there for the rest of the session on a workspace that sends every day. It re-asks once and then fills in on its own.

The Review step of the composer follows the same rule under Send from. While the check is in flight it says Checking your connected mailboxes…; if the check fails it says We could not check your connected mailboxes just now. Refresh the page to try again.; only once it has genuinely answered that there are none does it show Connect a mailbox to send campaigns. Otherwise you get the list of connected addresses to pick from.

Enable A/B testing on the A/B test step to split your recipients between two subject line variants. Configure the test percentage (5 to 50%), the duration (2 to 72 hours), and the winning metric (open rate, click rate, or reply rate). After the test period, the winning variant is automatically sent to remaining recipients.

The same step also offers Full versions, which test the subject and the body together across up to eight complete versions of the email. A campaign runs one test at a time, so turning one on closes the other. See Testing Full Versions of Your Email.

Each campaign tracks sent, delivered, opened, clicked, bounced, unsubscribed, and replied counts. The Analytics dashboard shows trends over time, best/worst performing campaigns, and per-campaign breakdowns.

One figure can read Unavailable instead of a number: opens on a campaign that sends plain text only, which has no HTML part to carry the open pixel. Clicks on those campaigns are still real measurements.

The Deliverability view opens with a Sending safety panel. It shows the three figures automatic pausing acts on, over a fixed window of the last 7 days, against the same limits the pause uses:

• Unsubscribe rate. Sending pauses automatically above 2%, once there are at least 200 sends to measure.
• Bounce rate. Sending pauses automatically above 2%, once there are at least 200 sends to measure.
• Delivery failure rate. Sending pauses automatically above 20%, once there are at least 100 attempts to measure. Recipients skipped because they are unsubscribed or suppressed are not counted as failures.

Below the minimum volume a row reads Not enough sends yet rather than 0%, because a rate over a handful of sends is not a rate. The window is fixed at 7 days and does not follow the period selector at the top of the page. If automatic protection has paused your sending, a line at the top of the panel says so and names the reason; an administrator can lift it from the platform console.

Unsubscribe rate is the closest signal we can measure to a spam complaint, and the panel says so. We cannot read your actual spam complaint rate: mailbox providers publish that in their own sender dashboards, not to us. The panel deliberately does not draw a complaint threshold onto unsubscribe data.