Email Personalization: Levels and Tools

What is email personalization?

Email personalization is any change to an email's content that depends on who gets it. The template stays the same. A field, a block or a whole asset changes, filled from the data you hold on each contact. Your data quality sets the limit. If all you have is a first name and a company, you can't honestly personalize beyond that, and readers can tell when a line pretends otherwise. The four levels below differ in what changes, what data they need and how they fail.

Level	What changes	Data it needs	What goes wrong
Merge tags	Single fields: first name, company, job title	One clean attribute per field	An empty field renders as "Hi ," or the raw tag shows up in the message
Segment content	Whole blocks swapped by group (industry, region, role)	A reliable segment attribute on every contact	Wrong segment, wrong block: a logistics firm gets the retail case
Per-recipient lines	One or two sentences written for that person	Research per contact, kept in a custom field	Generic lines dressed up as research read as fake
Per-recipient video	The video version each recipient gets	A recording plus clean recipient data	Bad data shows up on screen, where the recipient can't miss it

How to personalize an email, step by step

Getting the order right matters more than picking the tool. Most failures start as data problems that only show up after the send.

1. 1 Decide which fields you'll use. Every field must be filled for every contact in the send, or have a fallback.
2. 2 Clean the list: use consistent capitalization for names, strip legal suffixes like GmbH or Inc. from company names you'll use in a sentence, and remove rows with no usable name.
3. 3 Write the template with placeholders in your platform's syntax. Brevo's template documentation uses {{ contact.FIRSTNAME }}. In Mailchimp, the first-name merge tag is *|FNAME|*.
4. 4 Set a fallback for every placeholder. Brevo's template language has a default filter, for example {{ contact.FIRSTNAME | default : "there" }}, so an empty field reads "Hi there" and not "Hi ,".
5. 5 Send test messages to yourself from contacts with full, partial and empty fields, and check how each one renders.
6. 6 Send from your own authenticated domain. Before launch, check the Authentication-Results header of a test message.

Which email personalization tool fits which job?

When people compare tools, they're mostly comparing where their contact data lives and what syntax inserts it. All three platforms below fill merge fields from stored contact attributes. They're built for permission-based campaigns, and their acceptable use policies restrict sending to purchased or rented lists. Read the policy before you import a cold prospect list.

Tool	How fields are inserted	Where the contact list lives	Suits	Where it stops
Brevo	Liquid-style placeholders such as {{ contact.FIRSTNAME }}, with a default filter for empty values	Brevo contacts, with custom attributes	Campaigns and transactional mail from your own domain	Per-recipient research lines have to go into a custom attribute first
Mailchimp	Merge tags such as *|FNAME|*, defined per audience	Mailchimp audience	Newsletter-style campaigns to opted-in subscribers	Its terms forbid purchased lists, which rules out typical cold lists
Constant Contact	Contact details inserted through the editor's personalization option	Constant Contact contact lists	Small-business newsletters and event mail	Built for permission-based marketing lists, not cold B2B prospecting

Why per recipient, not per company?

In B2B outreach you'll often reach several people at the same company. If personalization stops at the company name, they all get the same message, and colleagues compare notes. When they do, the message that looked personal turns out to be a template. Per-recipient personalization gives each person a version tied to their own name and role, so you need clean data for each person. If a column is filled per company, say one pain point copied to every contact at the firm, that's company-level personalization, whatever the tool calls it.

With video, that mistake is even easier to spot. Our article on sending a personalized video message per recipient instead of per company explains how that works.

How EmailFlow OS personalizes video email

EmailFlow OS, a EmailFlow OS product, personalizes video for each recipient without you recording a separate video per person. You record one video and upload it to EmailFlow OS. You connect your own Brevo account and sending domain, then import your prospect list into EmailFlow OS. EmailFlow OS personalizes that one recording for each recipient on the list, not once per company, and sends each version from your own inbox, through your Brevo account and your domain.

There's no shared platform sender. Your domain's SPF, DKIM and DMARC records, your Brevo account and your sender reputation stay under your control. The catch is that the prospect list feeds every version directly, so a wrong name or role in a row ends up in that recipient's video. Clean the list before you import it. You'll find the steps on the EmailFlow OS features page and on the personalised AI video email for B2B outreach home page.

Does personalization affect deliverability?

It doesn't change authentication. Receiving servers check SPF against the sending server and verify the DKIM signature on the message. DMARC also requires at least one of the two to align with the domain in the From header. None of these checks look at your merge fields. Personalization can still matter in two indirect ways. A broken token, like a raw *|FNAME|* or "Hi ,", makes the message look careless and can draw spam reports. And messages that differ by only one name field read like bulk mail to the people who get them. The receiving server decides whether a message goes to the inbox or the spam folder, and neither the sender nor the tool controls that decision. Get authentication right first. Our guide to DKIM, DMARC and SPF for cold email senders covers the setup.

What EU data rules apply to personalization data?

Every field you personalize with counts as personal data under the GDPR. If you collected it from somewhere other than the person, the GDPR's transparency rules require you to tell them where it came from, at the latest when you first contact them. Relying on legitimate interest requires a documented balancing test, and it doesn't automatically cover cold email. In Germany, the Act against Unfair Competition (UWG) requires prior express consent for advertising by email, and that applies to B2B recipients too. The more detail a per-recipient line contains, the more visible your data processing becomes to the reader. Only use data you can explain. None of this depends on the sending tool. Compliance comes down to how you collect, store and use the data.

Personalizing a sales follow-up email

Follow-ups are where personalization usually breaks down. The research goes into the first message, and the follow-up just says "bumping this". Each search below gets its own answer.

• Sales follow up email template: use three parts. Open with a line that refers back to the first message, add one new piece of information for this person (a role-specific example, or an answer to a likely objection), and ask one question they can answer in a line. Use the same placeholders and fallbacks as in the first message.
• Follow up sales email: send it as a reply in the same thread so the In-Reply-To and References headers link it to the original. Don't put a fake "Re:" on a new message. It won't thread, and it misrepresents what the message is.
• Sales email follow up templates: keep one template per situation (no reply, after a call, final message) instead of one generic version. Each template only needs the fields you actually have at that stage.
• Sales follow up email: stop the sequence after a reply, a hard bounce or an unsubscribe request. Following up after any of these risks your domain's reputation and gets you nothing.
• Sales follow up email examples: "Hi {{ contact.FIRSTNAME | default : "there" }}, one thing I left out last week: how teams in your role handle the handover step. Worth a quick look?" The fallback keeps the line readable when the name field is empty.

You'll find full copy-ready versions in our sales follow up email template examples.

Questions people ask

? How to personalize an email in Constant Contact?

Constant Contact takes personalization from the contact fields stored in your list. In the email editor, you insert a contact detail such as first name through its personalization option, and the field is filled in for each contact at send time. As in Brevo or Mailchimp, make sure the field is filled for every contact, or set a fallback, before sending to the whole list.

? Is email marketing still worth it in 2026?

It depends on your list and your setup more than on the channel. Email to people who opted in, sent from a domain with SPF, DKIM and an aligned DMARC policy, is a different operation from cold email to a bought list, which most marketing platforms' terms prohibit. Judge it by your own reply and meeting data. General benchmarks can't replace that.

? What's the difference between segmentation and personalization?

Segmentation sorts contacts into groups and sends each group its own version, so there's one message per segment. Personalization changes content for each individual, anywhere from a single merge field to a video per recipient. Most campaigns use both: the segment decides the content block, and merge fields fill in the details for each person in it.

? Does a first-name merge tag count as personalization?

Technically, yes, but it's the lowest of the four levels. It changes only one field, so two recipients at the same company get otherwise identical messages. It works when the first name is the only data you trust. When the field is empty and there's no fallback, the reader sees "Hi ," or the raw tag.