People
Everyone in your Mimeo is a person — matched on lowercased email, never duplicated. This is where you find them, read what happened to them, and honor their requests.
Finding people
The people list searches and filters on email, name, tags, any custom
field you've defined, and suppression state. Combine them — "everyone
tagged customer whose plan field is
pro, excluding unsubscribes" is one filtered view, not
three steps.
Suppression is a first-class filter, not a footnote. You'll use it both ways: to exclude unsubscribes before a send, and to look only at unsubscribes when you want to understand why people are leaving.
The person page
A single person's page has five tabs. Overview holds their profile, attribution, fields and tags; Sales, Emails and Automation each hold the standard listings for what they contain, so a flow or a scheduled send looks the same here as it does on its own page.
| Section | What it holds |
|---|---|
| Profile | Email, first and last name, when they subscribed, when they arrived, and their first-touch attribution — the landing page, referrer, UTM parameters, device, and country from the very first event that created them. Attribution is written once and never overwritten. Subscribed on is the day they joined the list, which is the day they arrived unless an import or an event carried an earlier one; editing it here sets it outright, in either direction. |
| Fields |
Their values for every custom field you've declared. Editing one
here emits a field_changed event onto the timeline.
|
| Tags |
Add and remove tags inline. Each change emits
tag_added or tag_removed, so tagging is
auditable rather than invisible.
|
| Money |
Purchases, payments, and subscriptions, plus lifetime spend — the
sum of all their payments. This comes from the money events your
systems send; Mimeo never talks to a payment processor
itself. A subscription scheduled to cancel stays
active with a cancels <date> badge
beside its status until it actually ends.
|
| Emails | What's queued to go out to this person, and why it's queued — the same queue listing as Automation › Queue, minus the Person column. Cancel an individual send from its row. |
| Automation | The flows they're inside and the sequences they're partway through, as the standard flows and sequences listings with a note on each row saying where this person is in it. If they're stuck waiting on a step, the row's menu will move them on. |
| Timeline | Every event in order: signups, purchases, tag changes, field changes, sends, opens, clicks, unsubscribes. The full record. Click any row to open its full payload and details in a panel beside the list — the same reader as the instance-wide activity feed, narrowed to one person. |
Internal notes
The timeline also carries internal notes — plain-text
bookkeeping about the person, written by you or your coding agent
through the
people API or the
MCP server's add_person_note
tool: a support exchange, a manual correction, why something was
done. A note shows with a note icon, an internal badge, and
its readable text — not a raw payload — and clicking it opens the full
note (and any structured metadata it carries) in the side panel.
Notes are bookkeeping, not behavior: they never trigger automation. A note can't start a flow, open a gate, or send mail, and it never appears in the event trigger vocabulary — so leaving a paper trail on someone's record is always safe.
The engagement score
Every person carries a score from 0 to 100 answering "how alive is this address right now?" It sits in the person page's header, colored by band, and it's three observations added together: how recently they last opened or clicked anything (worth the most, decaying with a 45-day half-life), how many of the last 90 days' emails they engaged with, and whether they've been clicking — a click is a stronger signal than an open, and pixel-blocking can't fake it.
| Score | Band |
|---|---|
| 80–100 | Highly engaged |
| 60–79 | Engaged |
| 40–59 | Warm — where every new subscriber starts |
| 20–39 | Cooling |
| 1–19 | Cold |
| 0 | Suppressed |
Two rules sit above the arithmetic. Zero is reserved for the suppressed: unsubscribed and erased people score exactly 0 — below everyone, including a total stranger — and bounces and complaints land there too, because they suppress the address. A subscribed person never scores below 1, so 0 always means "do not send." And new subscribers start neutral, not high and not cold: until a few emails have actually reached them, there's no evidence either way, so they hold at 40 — one early click can't vault a stranger to the top, and silence in their first days isn't punished as cold.
Scores update the moment an open, click, or unsubscribe is recorded, and a nightly pass re-scores everyone — recency decays with time alone, so the silent cool off even when nothing happens. The score also decides the order a broadcast drains in: most engaged first.
Unsubscribing and resubscribing
You can unsubscribe or resubscribe anyone from their page — or your agent can, over the API and MCP. Mimeo always shows both the source and the reason alongside the status — whether it came from the person clicking the footer link (via link), a one-click header action from their mail client (via one_click), your own hosted unsubscribe page calling the API (via api), a CSV import that marked them already-unsubscribed, a provider webhook, or an operator doing it here.
That distinction matters when you're deciding whether to email someone. "Unsubscribed" from an inherited migration list is a different fact from "unsubscribed after your last send," and the record keeps them apart.
Your subscribers manage their own status through the unsubscribe link in every email — Mimeo's own unsubscribe page, which unsubscribes on load and then offers a resubscribe button or sends them on to a page of yours (which can offer resubscribe too, through the subscription-management API).
Exporting
Any filtered view exports to CSV. Filter down to exactly the set you want, then export — what you see is what you get, including the custom field columns.
GDPR: export and erase
Two actions on the person page cover subject requests.
Export person data
Produces a single JSON file with everything your Mimeo holds about that person: profile, fields, tags, attribution, events, money records, tracking, and send history. Hand it over as-is.
Erase person
Deletes the profile, their events, and their tracking data outright. Send-log and money rows are anonymized rather than deleted, so your aggregate history and financial records stay intact without still being attached to a name.
Erase has a keep suppression stub checkbox, and it's on by default. Leave it on. The stub is a minimal record that remembers "this address opted out" with no personal data attached — without it, the next CSV import or event containing that address recreates the person as a fresh, mailable subscriber, and you email someone who explicitly asked you not to.
Your provider needs cleaning up too. Sending providers don't offer a deletion API, so erasing someone in Mimeo can't remove them from the provider's own records. Mimeo surfaces a manual-cleanup notice telling you exactly what to go delete on the provider side. Do it — the request isn't fulfilled until both sides are clear.