Rémi KokabiNovember 19, 20269 min read
Email merge tags: how to personalize cold emails beyond the first name
“Hi ,” is still landing in inboxes right now. Somewhere a cold email sent with a blank first name field just told a lead exactly how little attention they got.
That blank space is what email merge tags are supposed to prevent, and most senders stop at the one tag everyone knows. First name and company name fill the gap, but they rarely earn a reply on their own.
Here’s what I’ll walk through: the tags that actually move reply rates, how fallbacks catch missing data before it embarrasses you, and how conditional content lets one email adjust itself for different industries or personas. You’ll also get copy-paste examples and the mistakes that make personalization look fake.
Get this right and your emails read like they were written for one person. Get it wrong and the lead sees the template underneath.
What are email merge tags
An email merge tag is a placeholder in your template that your sending tool replaces with each lead’s data at send time. First name is the bare minimum. The tags that move reply rates come from custom variables mapped to real context, clean data in every field, and fallbacks that catch the gaps.
Email merge tags (also called personalization tokens, merge fields, or variables) are placeholders you insert into a cold email template that get swapped for lead-specific data when the email sends. Every major outreach platform supports them using similar syntax.
Here is what that looks like in practice:
Before (template):
Hi {{firstName}}, I noticed {{companyName}} is growing fast.
After (sent email):
Hi Sarah, I noticed Acme Corp is growing fast.
The tag pulls the value from the matching column in your CSV, CRM, or lead record. If the column header says firstName, the tag must be {{firstName}}. Case matters. Spacing matters. One mismatch and the tag renders as raw text in the inbox.
Merge tags vs custom variables vs AI variables
Not all placeholders work the same way. The difference is where the data comes from and how much lift it does.
Type | Where the data comes from | Example | Best for |
|---|---|---|---|
Standard merge tags | Default lead fields | {{firstName}}, {{companyName}} | Basics every email needs |
Custom variables | Your CSV columns or CRM fields | {{recentHire}}, {{techUsed}} | Adding relevance tied to your research |
AI variables | Generated per lead by an AI prompt | A first line pulled from their website | Doing research at scale without manual work |
Standard merge tags cover the fields your platform already knows: name, email, company. Custom variables go further. You define the column, fill it with data you gathered (a tool they use, a job they posted, a trigger event), and the tag drops it in.
AI variables take a different approach. Instead of pulling a static field, they run a prompt across each lead’s data and generate a new value, like an icebreaker based on their LinkedIn headline or a one-liner from their company’s homepage. That means you can add AI-driven personalization to your emails without researching each lead by hand.
Merge tags worth using in cold email
First name and company name are table stakes. The tags below are the ones that make a lead stop and read.
For relevance
{{jobTitle}}: “As someone leading demand gen at {{companyName}}, you’ve probably noticed…”
{{industry}}: “Most {{industry}} teams we talk to are dealing with the same pipeline gap.”
{{signal}}: “I saw {{companyName}} opened a new office in {{city}}.”
For proof
{{similarCustomer}}: “We helped {{similarCustomer}} cut their ramp time by half.”
{{techUsed}}: “Since you’re already using {{techUsed}}, this plugs right in.”
For timing
{{recentHire}}: “Congrats on the new {{recentHire}} hire. That usually means the team is scaling outbound.”
{{fundingRound}}: “After a {{fundingRound}}, most founders want pipeline moving before the board meeting.”
Each of these works because it ties the message to something the lead recognizes as true about their own situation. The tag is the vehicle. The data behind it is what earns the reply.
Fallbacks for missing data
An empty merge tag turns your email into an obvious mass send. “Hi ,” with a trailing comma and a blank space tells the lead everything they need to know about how much attention you paid.
Fallbacks prevent that. In lemlist, the syntax is:
{{firstName|there}}
If firstName is empty, the email reads “Hi there,” instead of “Hi ,”. The format is {{variable|fallback}}.
A few rules for picking fallbacks:
Use natural words: “there”, “your team”, “folks”
Never use “MISSING”, “[First Name]”, or any bracketed placeholder
Match the tone of the sentence around it. If the sentence starts with “Hey”, “Hey there” works. “Hey valued prospect” does not
Before you launch, preview every lead’s email. If a fallback fires on more than a handful of leads, the real fix is cleaning your data, not relying on the fallback to carry the message.
Conditional content
Fallbacks handle missing data. Conditional content handles different data. When your list includes leads from multiple industries, countries, or personas, you can show each segment a different line without building separate campaigns.
lemlist supports Liquid syntax for this. Here is a simple example:
{% if industry == "SaaS" %}Most SaaS teams we work with struggle to fill mid-funnel.{% else %}We help growth teams turn outbound into a predictable channel.{% endif %}
A few things to keep in mind:
Keep each Liquid tag on one line. Line breaks inside the tag will cause it to render as raw text
Variable names are case-sensitive and cannot contain spaces
Test with leads from each segment before launching
lemlist also supports spin syntax, which creates random sentence variations so no two emails are identical. Spin syntax adds uniqueness. Liquid adds relevance. The two work together.
lemlist internal data from its users shows the difference. Campaigns using Liquid combined with spin syntax reply at 4.60% in Europe, compared to 2.94% for campaigns using variables only. In the US, the gap is wider: 4.46% with Liquid and spin syntax versus 1.71% with variables only.
Source: lemlist internal data from its users.
Spin syntax alone does not beat variables in Europe (2.31% email reply versus 2.94%). Spin works with Liquid, not instead of it.
Across all channels and all markets, campaigns using Liquid and spin syntax reply at 7.5%, compared to 3.1% for variables only and 2.5% for no personalization at all.
Source: lemlist internal data from its users.
Most teams stop at variables. Only a small share of campaigns use Liquid. That is the gap you can close. For more on tailoring messages by role, see persona-based messaging. If your list spans multiple languages, multilingual prospecting covers how to handle that.
Merge tags in subject lines
A merge tag in the subject line can work. {{firstName}} or {{companyName}} in the right context makes the email feel directed at one person. “Quick question about {{companyName}}'s outbound” reads like a real message.
The risk is overuse. When every cold email in the inbox starts with the lead’s first name, the pattern becomes a spam signal. A subject line like “{{firstName}}, {{companyName}} + [Your Company]” screams automation.
Use a tag in the subject line when it adds context, not when it adds a name for the sake of a name. And always set a fallback so the subject line still reads well if the field is empty. For more on what works, see cold email subject lines.
6 merge tag examples you can copy
1. Role-based opener
Hi {{firstName|there}}, running {{jobTitle|growth}} at {{companyName}} means you’re probably buried in pipeline meetings. Wanted to share one thing that’s helped similar teams.
2. Trigger event
Hi {{firstName|there}}, saw that {{companyName}} is hiring a {{recentHire|new sales lead}}. That usually means outbound is about to ramp. Here’s how we’ve helped teams in that exact phase.
3. Tech stack reference
{{firstName|Hey}}, since {{companyName}} already uses {{techUsed|a CRM}}, you might like how this plugs into your existing workflow. Worth a 10-minute look?
4. Social proof by industry
Hi {{firstName|there}}, we helped {{similarCustomer|a company in your space}} solve the same problem most {{industry|B2B}} teams run into with outbound. Happy to share what worked.
5. Location-based
{{firstName|Hi there}}, noticed {{companyName}} is based in {{city|your area}}. We’re working with a few teams nearby and thought this might be relevant.
6. Funding signal
Hi {{firstName|there}}, congrats on the {{fundingRound|recent round}}. Most founders we talk to post-raise want pipeline moving fast. Here’s one way to do that without adding headcount.
Mistakes to avoid
Broken formatting. Your data might store company names in all caps (“ACME CORP”) or append legal suffixes (“Acme Corp, Inc.”). Both look wrong in a sentence. Clean your data before import. Strip “Inc.”, “LLC”, and “Ltd.” from the company name column. Normalize capitalization.
Too many tags in one email. Three to four well-placed variables per email is enough. When every sentence has a tag, the email reads like a form letter with blanks filled in. The goal is a message that sounds written, not assembled.
Tags that sound creepy. Referencing a lead’s home city, the school they attended, or a personal detail they did not share publicly crosses a line. Stick to professional context: role, company, industry, public business events.
No preview before launch. One broken tag can send hundreds of emails with raw placeholder text. Always preview with real lead data. Check leads that have missing fields to confirm fallbacks render correctly.
For adding variation across your emails so they do not all read identically, see spintax in cold email.
How lemlist helps
lemlist gives you the full stack for merge tags and personalization in one place.
Import custom variables from a CSV or sync them from your CRM. Column headers become variable names, ready to use in the editor
AI variables generate per-lead values (icebreakers, cleaned names, segments) by running a prompt across your lead data
A preview panel lets you check each lead’s email before launch, so you catch broken tags, empty fields, and awkward fallbacks before they hit an inbox
Custom variables support up to 2,000 characters, long enough for full paragraphs, detailed icebreakers, or personalized URLs
Liquid conditions and spin syntax work inside any email step, so you can tailor content by persona, industry, or country without duplicating campaigns
For a full walkthrough on combining these features, see how to personalize at scale.
Final takeaway
Merge tags are the mechanics. Clean data, smart fallbacks, and conditional content are what make them work. Start with the tags that tie your message to something the lead cares about today: a hire, a signal, a tool they already use. Preview every email. Set a fallback on every variable. Then layer in Liquid and spin syntax to make each send unique.
Build your first signal-based sequence in lemlist and see how it comes together.
Build cold email campaigns that work
Find verified leads and launch personalized cold email campaigns.
Frequently asked questions
{{firstName|there}}, where “there” appears when firstName has no value.