Segments
List rebuilt 03:12 · 55,400 people, 18,598 we may write to
A segment here is a rule, not a stored number. Every figure on this page was produced by running the rule over the list when the page was drawn — which is why a clause can be taken apart and counted on its own.
Every cut of the list
A row is a rule. The figures beside it were produced by running that rule over the list a moment ago.
“May be written to” is people with an address the shop is allowed to use, permission on the record and a working mailbox. On the marketplace-only cut it is a rounding error, and that is the truest figure on this page.
On the list, never ordered
Signed up and never bought. They asked to hear from the shop, so they hear from it — but they are counted separately, because a send that lands well here can still have sold nothing.
The rule, clause by clause
- never ordered5,200
- gave permission for e-mail18,885
- All of them together4,841
Each bar is what that clause alone would select from the whole list. The clause closest to the total is the one carrying the segment; the ones far above it are barely narrowing anything.
Who it reaches
The same segment down both channels. Nothing is stored: each ladder is five filters over the 4,841 people the rule selected.
- In the segment4,841
- −Bounced hard before−72
- May be written to4,769
- −In the hold-out group−468
- Will receive it4,301
SMS
- In the segment4,841
- −No mobile number−3,405
- −Never gave permission−1,088
- −Took permission back−67
- −Number no longer works−7
- May be written to274
- −In the hold-out group−36
- Will receive it238
4,493 of the people who fell out could be recovered by the shop — by asking for permission again, by collecting a detail it never asked for, or by not sending something else to them first. The rest could not.
A send’s own ladder goes one step further than these two: it also takes off the people already carrying a message that day, and the group held back on purpose so the result can be measured.
A few of the records
Exactly as the channel hands them over. The shop never sees more than this either.
| Record | Came from | Orders | Spent | Last order |
|---|---|---|---|---|
| c***@outlook.com | Newsletter form | 0 | — | never |
| w***@proton.me | Newsletter form | 0 | — | never |
| l***@gmail.com | Newsletter form | 0 | — | never |
| v***@gmail.com | Newsletter form | 0 | — | never |
What the last sends did
- What comes off the roaster · 21 Aug4,301 reached · 27 orders above the held-back group, ₺19,031
Where the cuts overlap
People shared by each pair of segments, counted. This is the page's argument: a segment is not a box, and two sends in one week can arrive at the same person.
| Segment | Gone quiet, over six months | Bought the kit, not the coffee | Cold brew, last summer | On the list, never ordered | Regulars | Lapsing | First order, last 30 days | Top spenders | Shared, total |
|---|---|---|---|---|---|---|---|---|---|
| Gone quiet, over six months | — | 5,013 | 5,433 | — | — | — | — | — | 10,446 |
| Bought the kit, not the coffee | 5,013 | — | 392 | — | 882 | 865 | 378 | 401 | 7,931 |
| Cold brew, last summer | 5,433 | 392 | — | — | — | 620 | — | — | 6,445 |
| On the list, never ordered | — | — | — | — | — | — | — | — | 0 |
| Regulars | — | 882 | — | — | — | — | — | 1,006 | 1,888 |
| Lapsing | — | 865 | 620 | — | — | — | — | 165 | 1,650 |
| First order, last 30 days | — | 378 | — | — | — | — | — | — | 378 |
| Top spenders | — | 401 | — | — | 1,006 | 165 | — | — | 1,572 |
| Shared, total | 10,446 | 7,931 | 6,445 | 0 | 1,888 | 1,650 | 378 | 1,572 | 30,310 |
The diagonal is blank: a segment shares all of its people with itself, and printing that would flatten the scale. Where two segments overlap heavily, the calendar takes the second send’s share of them off — which shows up on the send as a named step called “in another send today”.
Sample data. The overlap figures are exact counts of shared records, not estimates: two segments that share people are two sends that can arrive at one person in a day, and the calendar takes the second one off.