Broadcasts & audiences

One list, one send, one place your contacts live.

Transactional mail goes to one person because they did something. A broadcast goes to everyone on a list because you decided to send it. Different intent, same infrastructure: audiences, contacts, and campaigns run through the identical EU pipeline as the rest of your mail.

Newsletter · EU1,284 contacts
1,280 sent4 suppressedpaused at ceiling
REST APIPOST /emails
SMTP:465 · TLS
Broadcastto an audience
Authenticatekey or credentials
Verify domainDKIM · SPF · DMARC
Suppress & meterbounces · ceilings
Sign and relayEU MTA · TLS
deliveredbouncedopenedclicked
Webhooksigned · retried
A broadcast is one call that becomes many messages, and each of them still walks the whole pipeline — suppression and ceilings included.

Audiences and contacts

An audience is a named contact list — “Newsletter subscribers”, “Beta customers”. Contacts carry an email address, optional first and last name, and a subscription status. Create as many audiences as you need to segment, and add contacts through the API or by importing a CSV in the dashboard.

Contact data is stored and processed in EU data centres alongside everything else. For a European team, that removes the awkward split where transactional mail is compliant and the marketing list quietly sits on a US platform.

Unsubscribe, handled properly

Every broadcast includes a footer unsubscribe link pointing at a hosted opt-out page. Confirming removes the contact from that audience and excludes them from future broadcasts to it. The contact record is kept — only the subscription status changes — so you retain the proof that they opted out.

Broadcast unsubscribes are deliberately scoped to broadcasts. They do not suppress transactional mail sent through the API — someone who leaves your newsletter still needs their password reset to arrive.

The same safeguards, applied to volume

Suppression still applies
Addresses that hard bounced or complained on any send are excluded, so a campaign can’t reintroduce a list-hygiene problem you already fixed.
Limits pause, they don’t fail
A broadcast that hits your monthly or daily ceiling moves to paused rather than erroring out, and resumes from where it stopped once the limit clears.
Review on early list sends
New accounts can reach 500 recipients by broadcast before we’ve reviewed the account. Most first campaigns are under that and go out in full — the check exists because a large first campaign from an unknown sender is the exact shape of the abuse that burns shared IP reputation.

Tracking resolved once

A broadcast has no per-message send call to carry flags, so open and click tracking are resolved from your organization default when the broadcast is created, and that answer is kept for the whole campaign. Results land in the same event stream and the same dashboard charts as transactional mail.

Set up your audiences now.

Create audiences, import contacts, and build the integration against the documented API while broadcast sending is being scaled up.

Create a free account
Keep reading
Audiences documentation →Contacts →Unsubscribe →Broadcasts API →