Customer Segmentation Template for Email
Four documents and four sheets that give every segment a message nobody else gets, then show you who actually moved between them.
Free download · No account needed
Migration Summary · 1 Jan to 1 Apr
The segment that looked flat
| Segment | 1 Jan | 1 Apr | Net | Arrived | Departed | Gross |
|---|---|---|---|---|---|---|
| Loyal | 4,120 | 4,088 | -32 | 1,268 | 1,300 | 62.3% |
| Repeat active | 7,930 | 8,300 | +370 | 3,990 | 3,620 | 96.0% |
| At risk | 6,970 | 6,310 | -660 | 4,480 | 5,140 | 138.0% |
| Lapsed | 7,940 | 5,750 | -2,190 | 3,240 | 5,430 | 109.2% |
| Dormant | 11,430 | 14,000 | +2,570 | 4,120 | 1,550 | 49.6% |
Loyal moved by 32 profiles. 1,300 people left it.
What the size number cannot say
Departures were 40.6 times the net change, and the segment kept 68.4% of its members. Every dashboard in the business called this flat, so nobody asked the retention question, which was the most valuable question in the model.
Where the 1,300 went
1,180 aged past the 90-day boundary into At risk. 120 left the list. Nobody did anything to them. Time passed.
Where the 1,268 came from
All of them crossed from Repeat active on a fourth order, which makes the fourth order the event worth building a message around.
Rows track only the profiles present on 1 January, so the quarter's new subscribers sit outside this grid.
Ashgrove Supply sells garden hand tools to 64,250 email addresses. Twelve segments sat in the sending account, built over three years by three people, and nobody had ever retired one. Against those twelve there were four emails that said meaningfully different things. The monthly report called the programme segmented. The distinct angle test in this pack collapsed the twelve to seven rows, and no message was lost, because five of the segments were a value band, a score, a subset and a response history.
Then the second problem, which is arithmetic. Ashgrove's Loyal segment held 4,120 profiles on 1 January and 4,088 on 1 April. Net change of 32, and every dashboard called it flat. Underneath, 1,300 profiles left and 1,268 arrived, so departures ran at 40.6 times the net change and gross turnover was 62.3%. Flat size says leave it alone. A third of the segment ageing out per quarter says the retention question is the most valuable one in the model.
So the Migration Matrix here is a balanced from-to grid rather than a size report. Rows sum to opening sizes, columns to closing sizes, and the opening total equals the closing total plus exits. It sits beside the lifecycle email programme pack, which settles what a segmented programme may send in one week, and the welcome email sequence template, which times what the Prospect and New rows hear first. Then the rest of the template library. Send River your exports, or take the files blank.
What's in the pack
Migration Matrix
The full from-to grid across two dated snapshots, with an Exit column and three balance checks that either hold or tell you the snapshots are wrong.
Migration Summary
Every segment decomposed into stayed, arrived, departed, net change and gross turnover, so a flat size can never be reported on its own.
Segment Register
Seven rows with size, revenue per profile, share of revenue, the distinct angle and the merge log naming what came into each row.
Performance by Segment
One row per angle with revenue per send, unsubscribes per order, and whether a holdout was run, read against turnover rather than in isolation.
Segment Definitions
Seven definitions with every boundary derived from the order history, plus the four things deliberately left out of a definition and why.
Distinct Angle Test
The merge mechanism with all twelve of Ashgrove's segments worked through, against the six groups Klaviyo's RFM report documents.
Message Angle per Segment
Four fields per segment, including what the angle must not be, which is where the discount reflex and the premature loyalty language get caught.
Migration Method
The snapshot rules, the balance checks, and the three failures that quietly invalidate a matrix before anybody reads it.
How to use it
- 1
Open in River, or take it blank
Open the pack in River and send your exports, or download the Word documents and CSV sheets and fill them in yourself.
- 2
Send customer, order and engagement data
Any one of the three starts it. A screenshot of your current segments or a typed description of how you slice the list today is enough to begin with.
- 3
Watch the boundaries get derived
Three numbers come out of your own order history and set the New and active lines, instead of the 30, 90 and 180 days every template inherits.
- 4
Read the merges, then the matrix
You get the segments that survived with the merges logged, then the grid, and the segment where net change and gross turnover disagree most.
Frequently asked questions
Is this template free?
Yes. Download the Word documents and CSV sheets with no account, no card and no email gate. Edit with AI is the optional half: River derives your boundaries, runs the merge test and builds the matrix from your own exports. Every pack sits in the template library.
Does my sending platform not already do this?
Partly, and it gets credit for it. Klaviyo's RFM report writes a current and previous month group onto every profile, and its own guidance recommends building segments for the profiles that moved. That is a targeting property, not a balanced grid.
Why is a flat segment size a problem?
Because it is a stock, and the thing worth knowing is the flow. Ashgrove's Loyal segment moved by 32 profiles in a quarter while 1,300 members left and 1,268 arrived. Flat size says leave it alone. A third of the segment ageing out says the opposite. Which of them is genuinely late is what the win back email template computes.
How many segments should I end up with?
As many as you can write genuinely different emails for, which is usually fewer than you have. The test is whether swapping two segments' first sentences would go unnoticed by the recipient. If it would, merge them and keep the difference as a variable inside one angle.
What counts as a reason to stop mailing a segment?
Sends that buy nothing and cost list attrition. Dormant here produced 19.1 unsubscribes per order at ten cents of revenue per send, and complaint volume has a hard ceiling: Gmail asks senders to keep spam rates below 0.3%. An email list health audit quantifies the suppression first.
What format are the downloaded files?
Four .docx documents and four .csv sheets, in a zip. They open in Word, Pages, Google Docs, Excel, Numbers and Sheets with no conversion. Add ?format=pdf to the download link if you want the documents as PDFs for circulation instead.
What does Edit with AI actually do?
It signs you up, installs this pack as a private workspace, and starts reading. Send the exports in whatever shape they exist. You get the derived boundaries, the merge log, and the matrix with its balance check run out loud.
Find out which of your segments is one segment
Take the Word documents and CSV sheets blank, or open this exact pack in River and send it the customer and order exports you already have.
Edit with AI