Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Email Marketing › Email Fundamentals

Email Segmentation

How to segment an email list: the data worth collecting, lifecycle and behaviour segments, engagement tiers, preference segments, and suppression.
Guideintermediate10 min readUpdated

Why relevance beats volume

Sending the same message to everyone is the default, and it fails in two directions. The people for whom the message is irrelevant ignore it, unsubscribe or complain, and their inaction lowers the engagement signals mailbox providers read. The people for whom it would have been relevant receive a diluted version written for an average subscriber who does not exist. Sending more to compensate makes both problems worse.

Segmentation reverses the trade. A smaller send to people with a reason to care produces more clicks and conversions per message, fewer complaints and a healthier reputation, which in turn improves placement for every other send. The relationship compounds: better placement produces more engagement data, which produces better segments. The costs are real, though. Every segment needs a message, and segments nobody mails are clutter. The discipline is to create a segment only when there is something different to say to it.

This guide is about segmentation within an email list. The segmentation strategy guide covers market segmentation, which decides who the business is for; the segments here assume that decision has been made and divide the people who have already said yes. The customer analytics section covers the analysis that often reveals which segments are worth building, including cohorts and customer lifetime value (LTV).

Data worth collecting

Segments are only as good as the data behind them, and data is only worth collecting if a message will depend on it. The table sets out the fields most programmes use, where each comes from and what it enables.

DataSourceEnablesCaution
Sign-up source and dateThe form or integration that added the addressLifecycle stage; cohort comparison; re-permission by originMust be recorded at capture; cannot be reconstructed later
Stated interests or preferencesSign-up form, preference centre, welcome surveyPreference segments; topic-specific sendsOnly ask for what will be used; keep the options few
Purchase historyCommerce platform or CRMBuyer against prospect; category affinity; replenishment timingNeeds a reliable join between email address and order
Lifecycle eventsAccount creation, first order, subscription start, renewal, cancellationStage-based flows and campaignsEvents must be defined once and used consistently
Email engagementThe sending platform: opens, clicks, repliesEngagement tiers; suppression; send-time judgementOpens are a weak signal in many mail clients; weight clicks
Site and product behaviourAnalytics or product events, where consent allowsBrowse and cart abandonment; feature adoptionConsent and privacy rules vary; do not assume tracking is permitted
Location and languageSign-up form, order address, browser localeLocal content, timing, legal variationsInfer carefully; let people correct it
Business attributesCRM for business-to-business lists: role, company size, industryRole-specific content; account-based sendsOften incomplete; verify before relying on it

Two rules. First, collect at the moment the data is natural to give, not in a long form at sign-up; a welcome survey with one question outperforms a sign-up form with six. Second, every field should map to at least one message that would be different because of it. A field that changes nothing is a maintenance cost and, for personal data, a liability. The list building and consent guide covers what to capture at sign-up and the consent record that must accompany it.

Lifecycle and behaviour segments

The most useful segments describe where someone is, not who they are. A lifecycle segment places each subscriber on the path from first contact to loyal customer, and the See-Think-Do-Care framing maps neatly onto it: people who have subscribed but never bought (see and think), people around a first purchase (do), and people who have bought more than once (care). Each stage wants a different message. Prospects need reasons and proof; first-time buyers need reassurance and a path to a second order; repeat customers need recognition, early access and reasons to stay rather than reasons to start. Where one send reaches several stages at once, the guide to personalising email content shows how content blocks give each stage its own section of the same email. Where the stage comes from a CRM field, a lifecycle segment is only as accurate as that field, and the tutorial on automating lifecycle stage changes sets it by rule rather than by hand.

Behaviour segments cut across lifecycle and are defined by what someone has done recently: viewed a category, abandoned a cart, downloaded a resource, used a feature, stopped using one, reached a usage limit. They are the raw material of automation. The nurture sequences guide covers how behaviour triggers a sequence of messages; this guide is concerned with the segments those sequences draw on and the campaigns sent to them.

Three lifecycle segments cover most programmes at the start: never purchased, purchased once, purchased more than once. Add a time dimension to each, such as how long since the last order, and the segments begin to describe risk: a repeat customer whose last order is well past their usual interval is a different audience from one who ordered last week. For subscription and software businesses the equivalents are trial, active, at-risk and churned, with usage standing in for orders. Define the boundaries once, write them down, and use the same definitions in reporting so that a segment's conversion rate (CVR) means the same thing every month.

Engagement tiers and suppression

Engagement tiers divide the list by how recently and how often each subscriber has interacted with mail. A common structure has three or four tiers: active (clicked recently), warm (opened or clicked within a longer window), cooling (no interaction for a while) and inactive (no interaction for a long time). The windows are the sender's choice and depend on cadence; a daily sender's "recent" is shorter than a monthly sender's. What matters is that the tiers are defined, refreshed automatically and used to decide who receives what. Purchase history can be tiered the same way: RFM segmentation scores customers on how recently, how often and how much they have bought, and its segments sit beside these engagement tiers. Whether those purchase segments or a cohort table is the right view for a given question is set out in the comparison of RFM segmentation and cohort analysis.

Suppression is the point of the exercise. Subscribers in the inactive tier should stop receiving regular sends, because every message they ignore lowers engagement signals and increases the chance that an abandoned address has been turned into a trap by its provider. Before suppressing, most programmes send a short re-permission sequence asking whether the person still wants to hear from them; those who respond return to the active tier, those who do not are suppressed. Suppression is not deletion. The consent record stays, the person can return through any sign-up point, and a transactional message still reaches them. The deliverability guide explains why this matters to the provider's view of the domain.

Tiers also guide what the active segments receive. The most engaged subscribers are the right audience for tests, for new formats and for the first batch of any large send, because their response is the quickest honest signal. Click-through (CTR) within each tier, tracked over time, is the measure that shows whether the tiers are set correctly; if the warm tier clicks almost as well as the active tier, the boundary is in the wrong place. The email marketing calendar template records, send by send, which segment receives each broadcast and which tiers are suppressed from it.

Preference segments

Preference segments are built from what people have said rather than what they have done. They come from the sign-up form, the preference centre and occasional surveys, and they cover topic (which kinds of content), frequency (how often) and format (a digest or individual messages, for example). They are the easiest segments to justify to a subscriber because the subscriber created them.

The trap is collecting preferences without honouring them. A preference centre that offers five topics while every send goes to everyone teaches people that choices are decorative, which makes the next unsubscribe more likely than the next preference change. Offer only the preferences that correspond to real streams of mail, and build the sending process so that a stated preference is enforced automatically rather than remembered by whoever builds the campaign. Frequency preferences deserve special care: a "less often" option should route a person into a lower-cadence stream, such as a monthly digest, and the sender should be able to show that the person received less. The list building guide covers the preference centre as a product; this section covers the segments it feeds.

Stated and observed preferences will sometimes disagree, as when a subscriber says they want everything but only ever clicks one topic. Behaviour is usually the better guide to what to send, and the stated preference remains the limit on what may be sent.

Keeping segments manageable

Segment sprawl is the common failure of a programme that has taken segmentation seriously. Dozens of saved segments with overlapping definitions, built for one campaign and never retired, make it impossible to know who received what, and they turn every send into an exercise in set logic. Three practices prevent it.

Name segments by definition, not by campaign: "repeat buyers, no order in the usual interval" survives; "spring sale group B" does not. Keep a short register of standing segments with their definition, owner, purpose and the messages that depend on them, and review it quarterly, retiring any segment nobody has mailed. Build segments from a small number of standard attributes, such as lifecycle stage, engagement tier, primary preference and a few behaviour flags, and combine them at send time rather than saving every combination. Report on the standing segments as part of the monthly email review, with the measures that matter for each (KPI): size, growth, click-through and conversion, so that a segment that has stopped earning its place is visible.

Illustrative example — not a real result

A software company's first segmentation pass

A project-management software company mails 27,000 addresses with one weekly newsletter. The team defines three lifecycle segments from product data: trial (2,900), paying (9,400) and churned or expired (6,100), with the remaining 8,600 as subscribers who never started a trial. Engagement tiers use 30, 90 and 180 days: 7,200 active, 9,800 warm, 5,500 cooling and 4,500 inactive. The inactive tier receives a two-message re-permission sequence; 410 people click to stay and the other 4,090 are suppressed. The newsletter now goes to 22,500 active and warm subscribers, with a trial-specific edition for the 2,900 in trial. Over the next quarter the click-through rate on the main newsletter rises from 2.1% to 3.4%, trial-to-paid conversion among newsletter recipients reaches 11% against 7% for non-recipients, and the complaint rate halves to 0.04%.

To decide which segments deserve retention effort at all, the guide to applying STP to customer retention ranks tiers by value at risk and names the ones to let go.

Common mistakes

  • Segmenting without a message plan. A segment is justified by what will be said to it differently, not by the data that makes it possible.
  • Collecting data nobody uses. Every field is a cost to maintain and, for personal data, a risk; collect what a message depends on.
  • Weighting opens over clicks. Opens are unreliable in many mail clients; a click is a decision.
  • Never suppressing anyone. Inactive addresses drag down engagement and placement for everyone still reading.
  • Deleting instead of suppressing. The consent record and the ability to return are lost for no gain.
  • Honouring preferences manually. A stated preference that depends on a campaign builder remembering it will be broken within months.
  • Saving every combination as a segment. Standard attributes combined at send time stay manageable; a library of one-off segments does not.
  • Changing definitions without telling reporting. A segment whose boundary moved cannot be compared with its own past.

The fundamentals hub places segmentation after list building and deliverability; relevance is the third foundation, and the one that turns the first two into results.

Frequently asked questions

How many segments should an email programme have?

As few as there are genuinely different messages to send. Most programmes do well with lifecycle stage, engagement tier and one or two preference or behaviour flags, combined at send time rather than saved as every possible combination. A segment that has not been mailed in a quarter should be retired.

Should inactive subscribers be deleted?

Suppress them rather than delete them. Suppression keeps the consent record, lets the person return through any sign-up point and still allows transactional messages, while removing them from regular sends that would otherwise drag engagement down. Send a short re-permission sequence first so that anyone who still wants the mail can say so.

What is the difference between segmentation and personalisation?

Segmentation decides who receives a message; personalisation changes the message for the person who receives it. A segment of repeat buyers might all receive a loyalty email, while personalisation inserts each person's name or recommended products into it. Segmentation comes first, because a personalised message to the wrong audience is still the wrong message.

Terms used on this page

Frameworks

Where this page is used

Also related

Related