Contacts, broadcasts and automations with consent kept for you
Every subscription change is recorded with where it came from.
Every subscription change is recorded with where it came from.
Contacts
rui.okafor@example.com
Consent
Fernbank
Unsubscribe from Product updates
rui.okafor@example.com
On links.minket.com
Opening a link changes nothing, so a link scanner cannot unsubscribe anyone; only the button does.
| Page | What it does |
|---|---|
| GET /unsubscribe/<token> | Shows the address and what it will stop receiving. |
| POST /unsubscribe/<token> | Unsubscribes, from the button or the mail client. |
| /preferences/<token> | One checkbox per topic. |
| /optin/<token> | Confirms a double opt-in. |
So a scheduled email never reaches someone who left in the meantime.
Properties are strings, numbers, booleans or dates, and up to 50 topics let people choose what they get.
pro142026-10-21Up to 100,000 rows run in the background and resume where they stopped.
email,plan,orders rui.okafor@example.com,pro,14
A broadcast sends one email to each contact, paced to protect your domain's reputation; an automation finishes on the version it started.
contact.createdA confirmation link that lasts 72 hours.
Two subjects tried on a sample of a broadcast; the winner goes to the rest.
Up to 200,000 contacts at a time.
Contacts, topics, broadcasts and automations.
Yes, as RFC 8058 describes it: marketing mail carries the headers, and the hosted page answers the click.
No. They carry your project's name.
No. A segment is a set of rules, read whenever it is used, so a contact can match many.