People
Everyone in your instance 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; Billing, 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 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. |
| 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. |
| 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. |
Unsubscribing and resubscribing
You can unsubscribe or resubscribe anyone from their page. Mimeo always shows both the source and the reason alongside the status — whether it came from the person clicking a footer link, a one-click header action from their mail client, a CSV import that marked them already-unsubscribed, 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 page you build against the subscription-management API. Mimeo hosts no public pages of its own.
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 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. Bento offers no deletion API, so erasing someone in Mimeo can't remove them from Bento. 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.