Features

Everything Emerge does, in detail.

No feature-matrix marketing. This is what’s actually built, section by section.

  1. 01Sending
  2. 02Contacts & segments
  3. 03Templates
  4. 04Campaigns
  5. 05Automations
  6. 06Send API
  7. 07Tracking & deliverability

01

Sending

Every send goes through an account you connected and own — Emerge has no first-party sending infrastructure of its own.

Connect through OAuth (Gmail, Microsoft 365) or by pasting credentials (Amazon SES, SendGrid, Mailgun, Brevo, Postmark, Resend, Mailjet, Zoho ZeptoMail, Zoho Mail, generic SMTP) — each has a setup guide. If you sign in to Emerge with Google or Microsoft, that mailbox is connected as a sender automatically — signing in and connecting a sender are often the same click. (You can also sign in with an emailed magic link — Emerge then takes you straight to connecting your first sender, since nothing sends without one.)

  • Pool multiple connected senders together, one pool per workspace
  • Rotation is fixed (one primary, fall through on failure) or round-robin
  • A sender with 3 consecutive auth failures is parked, not retried forever
  • Provider limits are respected — Gmail and Microsoft aren’t treated as bulk senders
  • Sends over your plan’s quota stay queued and go out automatically as it frees up, not failed
  • A sender that hits its provider’s own limit (like Gmail’s daily cap) cools down while the rest of the pool carries on — it comes back by itself
  • Addresses on domains that can’t receive email are skipped before sending — no quota used, no bounce against your sender
  • So are mailboxes that bounced as nonexistent for another Emerge sender in the last 90 days — shared only as a keyed hash, and lifted the moment the address opens or clicks anything
  • A skipped address is suppressed like a hard bounce, and resubscribed automatically if its domain starts taking mail again

02

Contacts & segments

Import, segment, and target — without a condition-builder you'll never fully use.

  • CSV import — Emerge finds the email column automatically
  • Static segments: build a list by hand, by import, by pasting a list of emails, or as an automation step
  • Rule-based segments group contacts by status — subscribed, unsubscribed, bounced, complained. Sends only ever reach subscribed contacts
  • Personalization data travels with each campaign — upload or paste per-recipient merge fields when you send
  • Hosted signup forms with double opt-in — share the link, embed it as an iframe, or paste a plain HTML form into your site
  • New subscribers can join a segment automatically and kick off a welcome automation
  • Export your full contact list as CSV any time — it’s your data

03

Templates

One editor, reused everywhere a message goes out.

  • Rich-text editor with a real formatting toolbar and image upload, plus a raw-HTML edit mode
  • {{merge_tag}} personalization with autocomplete — in a campaign, suggested from your own uploaded columns
  • Campaign preview rendered against real recipients and their merge data before you send
  • Saved templates load into a campaign or an automation step as a starting point

04

Campaigns

One-time sends, done properly.

  • Send now or schedule for later, in your own timezone
  • Pause mid-send and resume later — queued recipients just wait
  • Per-recipient merge data from a CSV or pasted table at send time
  • Send a test email that bypasses your quota
  • Cc/Bcc, reply-to, and From-name overrides per campaign
  • Target all subscribed contacts or a single segment
  • Turn open/click tracking or the visible unsubscribe link off per campaign

05

Automations

A straightforward step sequence — not a branching flow canvas you'll spend a week designing.

Automations are an ordered list of steps you build and reorder freely: wait, send a template, check whether the contact is in a segment, or add/remove a segment. A contact that fails a condition exits the automation — there’s no branch to a different path.

  • Triggers: a new contact, joining a static segment, or your own webhook URL
  • Runs at most once per contact — no accidental re-triggering
  • Exits automatically if the contact unsubscribes mid-flow
  • Webhook trigger is available on Starter and above
  • Enroll contacts by hand, and pause or reactivate an automation any time

06

Send API

Transactional email from your own app — receipts, password resets, alerts — through the same senders you already connected.

  • One authenticated POST /api/v1/send per email, answered synchronously with a message id
  • Send a saved template or inline HTML, with {{merge_tag}} data passed per request
  • Goes through your sender pool with the same rotation, failover, and limits as campaigns
  • Recipients aren’t added to your marketing contacts; suppressed addresses are refused
  • Sent as you wrote it: no tracking unless you opt in, and no Emerge branding
  • Bounces matched back to the message, with your own reference attached
  • Safe to retry: send an Idempotency-Key header and a repeated request returns the first result instead of sending twice
  • Available on Starter and above, with API keys you create and revoke from your account — Emerge Mail for WordPress uses it on every plan

07

Tracking & deliverability

We don't own the pipe — but we still do the deliverability work.

  • Opens and clicks tracked per recipient, rolled up per campaign — and per enrolled contact for automations
  • Per-recipient campaign status: queued → sent → opened/clicked, or bounced / complained
  • RFC 8058 one-click unsubscribe header on every campaign and automation send, automatically
  • Bounce/complaint webhooks for SES, SendGrid, Mailgun, Brevo, Postmark, Resend, Mailjet, and ZeptoMail
  • Gmail bounce tracking via a small script you install in your own account — there’s no bounce webhook API for personal Gmail. One mailbox shared by several workspaces reports each bounce to the right one
  • Hard bounces and spam complaints suppress a contact everywhere, automatically
  • A recipient refused outright at send time is suppressed on the spot, without waiting for a bounce
  • Repeated soft bounces (5 in 30 days, with no opens or clicks since) are promoted to a hard bounce
  • Blocks over sender reputation or content are logged but never held against a good address
  • SPF, DKIM and DMARC checked for every sending domain, daily and whenever a From address changes — problems shown on the Senders screen, the dashboard, and before you send a campaign
  • Provider-specific SPF and DKIM setup guidance shown when you connect an ESP or SMTP sender
  • A campaign pauses itself if its hard bounces pass 5% or spam complaints pass 0.3% — only that campaign; site email and automations keep sending, and you review and resume
  • Add your mailing address once and it’s appended to campaign and automation footers, for CAN-SPAM compliance

Ready to send through your own account?

Get started for free