Contacts, broadcasts and automations with consent kept for you

Every subscription change is recorded with where it came from.

Unsubscribe pages, hosted

Opening a link changes nothing, so a link scanner cannot unsubscribe anyone; only the button does.

The pages on links.minket.com
PageWhat 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.

Checked when it is accepted and again as it goes

So a scheduled email never reaches someone who left in the meantime.

  1. Acceptedsubscribed to Product updatesMon 09:00
  2. Unsubscribedone click, from another emailMon 14:12
  3. Suppressedchecked again before sendingTue 09:00

100 typed properties, segments of 50 rules

Properties are strings, numbers, booleans or dates, and up to 50 topics let people choose what they get.

plan
pro
orders
14
last_order_at
2026-10-21
Topics
Product updates, Receipts

Imports never resubscribe anyone

Up to 100,000 rows run in the background and resume where they stopped.

email,plan,orders
rui.okafor@example.com,pro,14
One row of a CSV import

Broadcasts and automations

A broadcast sends one email to each contact, paced to protect your domain's reputation; an automation finishes on the version it started.

  1. Triggeredcontact.created
  2. Waited2 days
  3. SentWelcome, part two

Opt-in, A/B tests and exports

Questions

Does one-click unsubscribe work?

Yes, as RFC 8058 describes it: marketing mail carries the headers, and the hosted page answers the click.

Do the pages show Minket's name?

No. They carry your project's name.

Are segments exclusive?

No. A segment is a set of rules, read whenever it is used, so a contact can match many.