How to Segment Your Contacts in a CRM: Lifecycle, Source and Behavior

Segmentation sounds like a marketing technique. In practice it is a simpler idea: send the right message to the right group of people, and do not send it to everyone else. A new lead who enquired yesterday, a customer who bought six months ago and a prospect who said no last year should not receive the same email, and a CRM is the place where you can tell them apart.

The catch is that segments are only as good as the data behind them. A beautifully designed “engaged leads” list built on half-filled records and inconsistent tags will quietly send the wrong thing to the wrong people. This guide covers the four axes that are actually useful, how to choose between tags, fields and lifecycle stages, five segments worth building first, and the suppression lists that protect you from the worst mistakes.

Key takeaways

Why segmentation only works on trustworthy data

Every segment is a question put to your database: who is recent, who is engaged, who is a customer? If the underlying records are wrong, the answer is wrong, and you will not notice until someone replies to say they already bought.

Before designing segments, check for duplicates, empty filter fields and labels that mean different things to different people. A modest set of segments on clean data beats an elaborate set on messy data.

Axis 1: Lifecycle stage

Lifecycle stage answers the question where is this person in our relationship? It is usually the most valuable axis, because what you should say to someone depends heavily on how far along they are. A common set of stages looks like this:

The labels matter less than two disciplines around them.

Write the definitions down

Each stage needs a sentence anyone could apply and reach the same answer: “replied to us or booked a call”, not “interested”.

Agree the hand-off rule

The most common failure is the gap between marketing and sales. Decide in advance what moves a contact from MQL to SQL, who makes the call, and how quickly sales must respond. A simple version: when a lead has booked a meeting or replied to a one-to-one email, sales owns them and the stage becomes SQL. Without a rule, good leads sit in a marketing list getting newsletters while they wait for a human.

Axis 2: Source

Where a contact came from is one of the most underused fields in a CRM. It matters because quality differs by source. People who found you through a referral usually convert differently from people who clicked an ad, and both differ from people you imported from a spreadsheet. You cannot know which is which unless the source was recorded when the contact was created.

Scalry records a source on each contact, with values such as manual, funnel, import, API, integration, social, referral, website, Facebook ads, WhatsApp and Google ads. Practical uses:

• Compare conversion by source. If one channel produces a lot of leads and almost no customers, you have learned something about where to spend.

Axis 3: Behaviour and recency

Behaviour is what people do, and it is the best predictor of what they will do next. The signals that are worth segmenting on are ordinary ones:

• Email engagement. Opened or clicked a campaign, or received one and did neither.
• Direct responses. Replied to an email or message.

Always pair behaviour with recency. “Opened an email” is almost meaningless on its own, because someone who opened one two years ago is not engaged today. “Clicked a campaign in the last 30 days” is a real signal. Time-based rules such as in the last N days, before, after or between are what turn a behaviour into something you can act on.

Axis 4: Attributes

Attributes are the facts about a contact or their company that do not change much: industry, company size, country, job role, the product they are interested in. They are useful for relevance, but add one only when you can name a segment or message that depends on it.

Tags, custom fields or lifecycle stage?

Most CRMs offer all three, and confusing them is how data gets messy. The rule of thumb is to choose by what you need to do with the information.

A few practical consequences follow.

• If you can only be one of them, use a field or a stage, not a tag. A contact tagged both “customer” and “lead” is a data error waiting to happen.
• If the value is free text, it is not segmentable. Prefer a fixed list of options so that “Healthcare” and “health care” do not become two industries.

Scalry supports all three: a lifecycle stage on every contact, tags that can be given colours so they are easy to scan, and custom fields for your own structured data. Segment rules can use any of them.

Building segments with AND and OR logic

A segment is a set of rules joined by logic. AND narrows the group: every condition must be true. OR widens it: any condition is enough. Most useful segments combine the two, with a group of OR conditions nested inside an overall AND.

Scalry’s CRM lets you build segments with nested AND and OR rules on contact fields, including name, email, phone, company, lifecycle stage, source, created and modified dates, tags and custom data. Date rules include before, after, between, in the last N days and in the next N days. Engagement rules include opened, clicked or received a campaign, and also not opened or not clicked any.

Five segments worth building first

You do not need dozens. These five cover most of the value, and each is a worked example of the rules above.

1. New leads in the last 7 days who have not been contacted

Rules: lifecycle stage is lead AND created in the last 7 days AND no recorded outreach. Why: speed to first contact is where many leads are won or lost, and this is your daily to-do list. Because “not contacted” depends on how you record activity, a simple route is to apply a tag when someone first reaches out and make the segment “lead, created in the last 7 days, without that tag”.

2. Engaged but not booked

Rules: lifecycle stage is lead or MQL AND clicked a campaign in the last 30 days AND not tagged as meeting-booked. Why: these people have shown interest but have not taken the next step. They are the right audience for a clear, direct invitation to talk, rather than another piece of general content.

3. Customers 90 or more days since last purchase

Rules: lifecycle stage is customer AND last purchase date before 90 days ago, using a custom field or the modified date if that is what you track. Why: it is the natural audience for a check-in, a reorder prompt or a win-back message. The 90 days is a placeholder; use the rhythm of your own business.

4. High-score leads with no activity

Rules: lead score above your threshold AND no campaign clicked and no reply in the last 30 days. Why: these look like good fits that have gone quiet. They deserve a personal message from a person, not another bulk email. Lead scores are stored on the contact, so you can use them as a rule alongside the others.

5. Lost deals that were a good fit

Rules: tagged lost AND a fit attribute such as the right industry or company size AND lost more than 90 days ago. Why: circumstances change, budgets reset and champions move. A well-timed, honest note to a lost deal that matched your ideal customer is among the cheapest pipeline there is.

Smart lists versus static lists

A smart list is a saved set of rules whose membership updates itself; a static list is a fixed snapshot.

The default should be a smart list. If a segment describes a state, such as “customers inactive for 90 days”, it should update itself. A static list suits a moment, such as “people at the March event”. If you do use a static list for a send, check it against your suppression rules on the day, not the day you built it.

In Scalry, saved filters, which act as smart lists, can be saved for contacts, companies and deals, so the same approach works for accounts and pipeline as well as people.

Suppression segments: the most important ones

Most teams think about who to include. The groups you must exclude matter more, because a wrongly included person can unsubscribe, complain or mark you as spam, and that harms deliverability for everyone else you send to. Build these first and apply them to every campaign.

• Opted out. Anyone who has asked not to hear from you, by email or by text. This is both courtesy and, in many places, a legal requirement.
• Bounced addresses. An address that has hard-bounced will not get better by retrying, and repeated bounces damage your sender reputation. Keep them out until the address is corrected.
• Existing customers, for cold outreach. Telling someone who already pays you that you would love to introduce your product is a quick way to look disorganised.

How you record these depends on your setup. Where a CRM tracks unsubscribes itself, rely on that. Where it does not, a clearly named tag or custom field, applied consistently, lets you exclude the group in segment rules. Whichever way you do it, test it by sending to a suppressed test contact and confirming nothing arrives.

Avoiding segment sprawl

Segments are cheap to create and expensive to understand. Use a naming convention that says what the rules do, give every segment an owner and a one-line purpose, review quarterly, and archive anything unused. Check whether an existing segment with one more rule already does the job.

The data hygiene that makes this possible

You will not get far without a baseline of tidy data. The practical minimum is short.

• One source of truth. Decide where contact data lives. If the same person is edited in a spreadsheet, an email tool and the CRM, they will drift apart.
• A small set of required fields. Typically email or phone, name, source and lifecycle stage. Anything you cannot segment on is optional.
• Deduplication. Merge duplicates on import and periodically afterwards, matching on email and, where relevant, phone.
• Consistent naming. Pick one spelling for countries, industries and company names, and use fixed option lists wherever possible.

Privacy and consent

Being able to segment on a piece of data does not mean you are allowed to. A few principles are widely shared, though the details vary by country and by channel.

• Purpose limits. Regimes in the style of the GDPR expect you to use personal data for the purposes people were told about. Data collected to deliver an order is not automatically fair game for marketing.
• Consent by channel. Email, SMS and WhatsApp each have their own rules, and consent for one does not always cover another.

This is general information, not legal advice. Requirements differ between jurisdictions and change over time, so check with a qualified adviser for your situation, particularly if you contact people in several countries.

Measuring whether segments are working

A segment is a hypothesis: these people respond differently, so treating them differently will help. You can test it with two simple measures.

• Segment size over time. A smart list that never changes, or doubles overnight, may signal broken rules or a bad import.
• Conversion per segment. What share moves to the next lifecycle stage, and how fast.

Common mistakes

• Too many tags. Dozens of overlapping tags make rules fragile and reports meaningless. Move structured facts into fields and clear out temporary tags.
• Overlapping segments that double-send. A person who qualifies for three campaigns on the same day will receive three emails. Decide a priority order or use a frequency cap.

How Scalry handles this

Scalry keeps segmentation inside the CRM, so the segment is built from the same records your team already works in. You can build segments with nested AND and OR rules on contact fields: name, email, phone, company, lifecycle stage, source, created and modified dates, tags and custom data. Lifecycle stages run from subscriber through lead, MQL, SQL, opportunity and customer to evangelist, and sources include manual, funnel, import, API, integration, social, referral, website, Facebook ads, WhatsApp and Google ads.

Date rules cover before, after, between, in the last N days and in the next N days, and engagement rules cover contacts who opened, clicked or received a campaign, as well as those who did not open or did not click any. You can save a filter as a smart list for contacts, companies or deals, give contacts coloured tags and custom fields, and use a segment as the audience for an email or SMS campaign. Lead scores are stored on the contact too.

The limits: Scalry gives you the rules and the records. Your lifecycle definitions, data quality and consent stay with you.

Questions to ask before you commit

Whichever way you are leaning, these are the questions that change the answer. Work through them against your own numbers rather than anyone's feature matrix — including this one.

• Do we have written definitions for each lifecycle stage? And does everyone apply them the same way?
• What is the hand-off rule between marketing and sales? Who decides, and how fast must they act?
• Is the source recorded on every contact? If not, we cannot compare channels.
• Which of our fields are filled in for most contacts? Those are the only ones worth segmenting on.
• Which suppression lists exist, and are they applied to every send?
• Who owns each segment, and when did we last use it?

If you cannot answer the first three, you are not ready to choose between Scalry and how you segment today yet — you are still deciding what you need, which is a cheaper problem to solve first.

A four-week plan

Week 1: write one sentence per lifecycle stage, agree the hand-off rule and the required fields. Week 2: merge duplicates, fill required fields and clear stale tags. Week 3: build and test the suppression lists, then the five segments as smart lists. Week 4: send one message to one segment, record size, clicks, replies and conversion, and retire anything unused.

Frequently asked questions

What is contact segmentation in a CRM?

It is dividing your contacts into groups based on shared characteristics, such as lifecycle stage, source, behaviour or attributes, so each group can receive messages that suit it. Done well, it means fewer irrelevant emails and more replies.

What is the difference between a tag and a custom field?

A tag is a flexible label, and a contact can have many; it suits events and temporary groupings. A custom field holds a structured value, such as industry or company size band, and is better when you will filter or report on it. Use a field when there is only one correct answer per contact.

What is a smart list?

A smart list is a saved set of rules rather than a fixed group of people. Membership updates automatically as contact data changes, so it always reflects the current state. A static list, by contrast, is a snapshot that you maintain by hand.

How many segments do I need?

Fewer than you think. Start with the suppression lists and about five working segments, such as new uncontacted leads, engaged leads who have not booked, quiet customers, high-score inactive leads and good-fit lost deals. Add more only when a specific message depends on them.

What are suppression segments?

They are groups you exclude from campaigns, such as people who have opted out, addresses that have bounced and existing customers who should not get cold outreach. They are the most important segments because they protect your sender reputation and keep you on the right side of consent rules.

Can I segment on any data I have?

Not necessarily. Many privacy regimes expect personal data to be used only for the purposes people were told about, and the rules differ by country and by channel. This is general information rather than legal advice, so check the requirements that apply to you.

How do I know if a segment is working?

Watch its size over time to catch broken rules, and measure what share of it moves to the next lifecycle stage. Compare clicks, replies and unsubscribes for the same message across segments. If two segments behave identically, consider merging them.