Email marketing
Campaigns to a segment resolved at send time. Automations that wait, email, book a task and branch. And the part most tools leave out: unsubscribes, bounces, a suppression list and double opt-in, so the mail actually arrives.
Templates, variables from the contact's data, open and click tracking, RFC 8058 one-click unsubscribe. A background worker sends, fairly across companies — another company's 20,000-row campaign does not queue in front of your password reset.
A saved filter as a list. "Customers in Budapest we have not contacted in 90 days" — recipients are resolved when the campaign goes out, not read from a membership table. The preview, the member list and the send run the same predicate.
Wait, send an email, create a task, change stage, tag, notify — and branch on a condition. Four recipes to start from, all arriving switched off, because a welcome flow activated with a blank template sends blank mail.
A public, embeddable form that creates a contact — and a deal if you want one. A honeypot against bots, utm attribution stored, and a repeat submission updates the existing record rather than creating a twin.
Connect an IMAP mailbox: incoming mail files itself against the sender's contact and lands on their timeline, threaded. The password is encrypted with AES-256-GCM, because it has to be replayed to the mail server.
Campaigns send only from a verified address. Double opt-in on forms; a suppression list that remembers unsubscribes, hard bounces and complaints beyond the record — a re-imported CSV cannot subscribe anybody again. The provider bounce webhook retires a bad address before your domain's reputation pays for it.
You get a link at registration. Until it is confirmed, no campaign goes out.
On import the subscribed column counts; forms can ask for double opt-in. Every change is recorded.
A saved filter or a static list. The preview says how many will receive it.
The worker sends; the campaign page shows queued, sent, opens and clicks.
The same thing step by step, in the help centre.
Verification, sender, double opt-in and the suppression list — what delivery depends on.
The four ready-made recipes, what they do, and what to fill in before switching them on.
Column mapping, the email uniqueness rule, and what happens to duplicates.
What a subject access export returns, what erasure removes, and what the law keeps.
It sends through the SMTP provider you configure, so the sender is your domain. Domain authentication (SPF, DKIM) is set up at your mail provider, not here.
The provider callback (Postmark, SendGrid and Mailgun shapes are recognised) unsubscribes the contact on a hard bounce and adds it to the suppression list; a soft bounce gets a grace window. A complaint counts as an unsubscribe.
It depends on the plan and is tabulated on the pricing page. The counter resets monthly and is checked before a send, not after.
14 days, no card. If it doesn't suit you, export everything and leave — the data stays yours.