Email Segmentation and Personalisation for B2B (2026)

#01Which segmentation dimensions matter in B2B?

Our view: role and stage do more for B2B results than any other split. A CFO and an AP clerk want completely different proof, and a trial user and a customer need completely different next steps.

#02How do you get the data right?

1. List the fields you want to segment on.
2. Give each one a source of truth and an owner (see the table above).
3. Define values. "Role" with 400 free-text job titles is unusable. Map titles into 6 to 10 role buckets with rules or an enrichment tool.
4. Set sync frequency. Lifecycle stage and unsubscribe status: near real-time. Firmographics: daily is fine.
5. Audit fill rate. If 60% of contacts have no role, do not build role-based content until you fix that.
6. Add progressive profiling: ask one new question per form fill, or in a preference centre ("Which best describes your role?").

#03What segment recipes work?

Recipe 1: high-intent visitors

Contacts who viewed pricing or integration pages twice in 14 days and are not in an open deal. Send a short, plain email with a relevant case study and a calendar link, from a real person. Notify sales in the CRM.

Recipe 2: trial users stuck before activation

Trial started more than 3 days ago, activation event not reached. Send help focused on the exact step they have not completed (lesson 10).

Recipe 3: customers not using a key feature

Plan includes feature X, feature X not used in 30 days. Send a how-to with a 2-minute video and a customer example.

Recipe 4: role-based newsletter blocks

Same newsletter, but the "this week's tactic" block changes by role bucket: AP managers get a process tip, controllers get a reporting tip, CFOs get a cost or risk angle.

Recipe 5: account-based nurture

Contacts at named target accounts (from the sales account list) who are subscribed. Show industry-specific proof and invite them to a small-group event. Coordinate with sales so they do not get both a marketing invite and a cold email the same day.

Recipe 6: low-engagement frequency cap

Tier D contacts get the monthly digest only, not weekly sends.

#04How do you personalise safely?

Rules:

• Always set a fallback for every merge field and dynamic block.
• Test with bad data: empty field, all caps, very long values, non-Latin characters.
• Avoid surprising data. If you would not say it on a first sales call, do not put it in an email.
• Keep it true. A personalised claim that is wrong destroys trust faster than a generic one.

#05Worked example: Ledgerline

Ledgerline is a fictional accounts-payable software company. Figures are illustrative, not benchmarks.

Ledgerline sends one weekly newsletter to everyone. Controllers say it is too basic; AP clerks say it is too strategic.

Walkthrough

1. Audit fields: role is filled for 41% of contacts. Company size for 78%.
2. Fix role: job titles mapped into six role buckets with rules; a one-question preference centre added; enrichment fills more. Fill rate reaches 74% in six weeks (illustrative).
3. Build blocks: the newsletter keeps one shared lead story and adds a role-based tactic block with a generic fallback.
4. High-intent recipe: pricing-page visitors get a personal email from the account executive; sales gets a CRM task.
5. Measure: links tagged with utm_content per role block. Controllers' clicks on the tactic block rise while unsubscribes fall.

#06Common mistakes

• Creating segments without different content.
• Segmenting on fields that are mostly empty.
• Using opens to decide who is engaged.
• No fallback, so emails say "Hi ,".
• Personalising with data the reader never shared.

#07Try it yourself

List the ten fields you would most like to segment on. Record source, owner, fill rate and sync frequency. Pick one recipe above, build the segment and count it. If it is under 200 people, decide whether it should be a flow trigger instead of a broadcast segment.

#08Quick quiz

1. When is a segment worth creating? Answer: When you will send it different content.

2. What two dimensions matter most for B2B? Answer: Lifecycle stage and role.

3. What should every merge field have? Answer: A fallback value.

4. How can you measure conversion by segment in GA4? Answer: Tag links with a segment value in utm_content.

#09What should you check before the next lesson?

• Field inventory with sources and fill rates.
• Role buckets defined.
• Fallbacks set for all dynamic content.
• At least one behaviour-based segment live.

Previous: How to choose an email service provider · Next: Lifecycle, onboarding and nurture flows

Or return to the Email Marketing for Marketers track.

Related: List building and lead magnets · AI writing, personalisation and AI inboxes · n8n lead enrichment

#10Common questions

How many segments should a B2B email program have? Start with five to eight that change what you send, such as lifecycle stage, role, and engagement tier. More segments only help if you have content that differs for each.

Is first-name personalisation still worth it? It rarely moves results on its own and breaks badly when data is wrong. Personalise on role, company context and behaviour instead.

Should segments use opens? No. Apple Mail Privacy Protection inflates opens. Use clicks, replies, product events and site visits.

Can AI personalise each email? AI can draft variations by segment, but every claim must come from data you hold, and a human should review templates before they go live. Lesson 18 covers the safe workflow.