One audience engine, now in the inbox.
Send one-time, recurring and triggered email from your own SMTP server. The same real-time audiences that drive push and on-site personalization decide who receives each message, and recorded consent decides who never does.
Still thinking it over?
[email protected] · to you
Unsubscribe · sent from your own domain
One-time
Send now or at a chosen moment to every consenting profile in one or more audiences. A completed send becomes read-only, so the same list is never mailed twice by accident.
Recurring
Run daily, weekly or monthly in the account's timezone. The audience is resolved again on every run, so a newsletter always reflects who qualifies today.
Triggered
Respond to a customer state such as an abandoned cart after the configured delay, minimum value and eligibility checks — reading the same cart signals mobile push uses.
Write it once, and it arrives personally
A block builder for marketers, a raw HTML mode for agency templates, and one rendering path shared by the preview, the test send and the real campaign.
Template builder
- • Drag-and-drop heading, text, image, button, divider, column, social and footer blocks
- • Responsive, inline-styled HTML that survives older mail clients
- • Raw HTML mode for templates built elsewhere
- • Reusable account templates, snapshotted per campaign
- • Subject and preheader written side by side
Personalization and preview
- • Placeholders resolved from any visitor attribute you already collect
- • Fallback defaults for missing values, so nothing renders blank
- • Cart variables for triggered sends: item count, total, first item name
- • Desktop and mobile preview rendered against a real profile
- • Send a test to yourself through the live pipeline
Consent is the first filter, not the last
Every campaign is checked against consent and a permanent suppression list — at targeting time and again at delivery, because people opt out in between.
Consent on the profile
Subscription state lives on the customer profile beside every other attribute, so audiences can target it directly and a reach estimate counts only mailable people.
Permanent suppression
Opt-outs, bounces and complaints are kept in a durable list that data-retention rules never expire, and an existing do-not-mail file can be imported on day one.
One-click unsubscribe
Standards-based one-click headers, plus an optional preference page hosted on your own domain so the opt-out experience never leaves your brand.
Managing consent in the panel: search by address or profile, change a single customer with a recorded reason, bulk-update thousands of addresses at once, or upload a CSV suppression file. Every change is audited, and an unsubscribe applies to the very next send rather than the next indexing cycle.
Your mail server, your sending reputation
Bring your own relay: connect Amazon SES, SendGrid, Postmark, Mailgun or an in-house SMTP server. Mail leaves your own domain, so the deliverability you have built stays yours.
Validated before it is saved: credentials are encrypted at rest, the connection is tested on save, and a deliverability checklist covers SPF, DKIM, DMARC and a monitored return path.
Throttling that respects the relay: per-minute, per-hour and per-day limits, plus connection and messages-per-connection caps, enforced at send time across every worker.
Quiet hours and UTM tagging: hold campaigns that fall outside the delivery window, and decorate every outbound link with the campaign's UTM parameters at render time.
Campaign funnel
Bounced, unsubscribed, complained and failed are reported alongside. Sent means accepted by your relay, never a guess at delivery. Illustrative interface values.
Email that knows the rest of the journey.
Reuse the audiences, cart signals and customer profiles you already have, and keep the inbox, mobile push and on-site personalization telling one story.
Plan your first campaign