
Cold email merge tags are the placeholders — like {{first_name}} or {{company}} — that your sequencer replaces with each prospect's data at send time. Used well, they let you send relevant messages at scale. Used badly, they produce "Hi {{first_name}}," in a prospect's inbox or awkward sentences no human would write. This guide covers the standard and custom variables worth using, how to prepare your CSV so tags never break, fallbacks and spintax, examples of merge-tag sentences that read naturally, and the line between surface-level tokens and personalisation that actually earns replies.
Cold Email Merge Tags: The Short Answer
Merge tags (also called variables, personalisation tokens or placeholders) pull values from columns in your lead list into your copy. Syntax depends on the tool — commonly double curly braces such as {{first_name}} or {{firstName}} — so check your sequencer's documentation.
Tier | Example tags | What it achieves |
|---|---|---|
Basic | {{first_name}}, {{company}} | Table stakes; prospects expect it |
Contextual | {{title}}, {{industry}}, {{city}} | Segment-level relevance |
Custom | {{trigger}}, {{first_line}}, {{pain_point}} | Individual relevance — where replies come from |
💡 Key Takeaways
Use few tags, clean data and a fallback for every tag. The tags that move replies are custom columns you research or generate per prospect, not the standard fields.
Standard Merge Tags Every Campaign Uses
Variable | Use it for | Watch out for |
|---|---|---|
{{first_name}} | Greeting | ALL CAPS, initials, full names in the field |
{{last_name}} | Rarely needed in cold email | Sounds formal |
{{company}} | References to their business | Legal suffixes: "Acme Holdings, Inc." |
{{title}} | Role-specific lines | Long or odd titles: "VP, GTM & RevOps (EMEA)" |
{{industry}} | Vertical messaging | Vague data-provider categories |
{{city}} / {{country}} | Regional relevance and timing | Headquarters vs person's location |
{{website}} | Custom references | Raw URLs in copy look automated |
{{sender_name}} | Signature | Must match the sending inbox |
Custom Variables That Actually Drive Replies
Custom columns are where merge tags become real personalisation. Fill them from research, enrichment or AI-assisted drafting reviewed by a human:
⚡{{trigger}}
A recent event: hiring, funding, launch, expansion.
✍️{{first_line}}
A one-sentence personal opener per prospect.
🎯{{pain_point}}
The likely problem for their segment or role.
🏆{{case_study}}
A relevant customer in their industry.
🧰{{tech}}
A tool they use that your product works with.
🤝{{mutual}}
A shared connection, event or community.
Building these columns starts with good data: list building, finding and verifying leads and prospecting.
Preparing Your CSV So Merge Tags Never Break
Name columns exactly as the variables you use (or map them on import).
Fix capitalisation: "sarah" and "SARAH" become "Sarah".
Shorten company names: drop Inc., LLC, Ltd. and taglines; use the name people say out loud.
Normalise titles to short versions or map them to a role group.
Remove blanks or plan fallbacks for every column you use.
Check for stray characters: emojis, extra spaces, encoding errors.
Verify emails before upload (verification tools, list cleaning).
Preview a random sample of 10–20 rendered emails before launching.
Fallbacks, Spintax and Conditional Content
Fallback values
A fallback is the text used when a field is empty — for example "there" for a missing first name, or "your team" for a missing company. Many sequencers support default values for variables; check how yours handles them and test an empty row.
Spintax
Spintax rotates phrases, such as {Hi|Hey|Hello}, so not every email is identical. It can reduce sameness across a large send, but keep variations natural and equally good; spintax is not a substitute for relevance.
Conditional content
Some tools support if/else logic based on a field (for example a different line per industry). Use it for segment messaging, and keep rules simple enough to QA.
Identical, robotic-looking sends are one reason outreach gets flagged — see cold email bot detection.
Merge-Tag Sentences That Sound Human
Weak (obvious template) | Better |
|---|---|
I see you are the {{title}} at {{company}}. | Saw {{company}} is {{trigger}} — congrats. |
I help companies in {{industry}} grow. | Most {{industry}} teams we talk to struggle with {{pain_point}}. |
Hi {{first_name}}, hope you're well! | Hi {{first_name}}, {{first_line}} |
We work with companies like {{company}}. | We helped {{case_study}} with the same issue. |
Are you in {{city}}? | Reaching out to a few {{city}} teams this week. |
More full examples: cold email examples and the cold email ultimate guide.
Merge Tags in Subject Lines and Preview Text
A {{first_name}} or {{company}} in the subject can add relevance but can also look automated if every email follows the same pattern. Remember that the first line of your body usually becomes the preview text, so a strong {{first_line}} doubles as your inbox preview — see cold email preview text. And make sure your closing question works with the variables too (cold email CTA examples).
Merge Tag Mistakes That Hurt Replies
🏷️Raw tags showing
Missing column or typo in the variable name.
🔠Bad capitalisation
"Hi JOHN" reads as a database dump.
🏢Formal company names
"Acme Corporation Ltd." in a casual sentence.
🔁Too many tags
Every sentence templated still reads as a template.
❓Wrong data
Old titles or companies are worse than no personalisation.
🧪No QA
Launching without previewing rendered emails.
🖼️Heavy formatting
Fancy HTML undermines a personal message (plain text vs HTML).
Scaling Personalisation Without Burning Inboxes
Better personalisation lifts replies, but it doesn't change the sending limits each inbox should respect. Scale by adding inboxes and domains rather than volume per inbox:
Keep per-inbox volume low (safe sending limits, inbox sizing).
Authenticate every domain (SPF, DKIM and DMARC).
Start with pre-warmed inboxes or warm gradually (warm-up guide).
Connect inboxes by OAuth to your sequencer (Smartlead setup, Google Workspace + Smartlead, Microsoft 365 + Lemlist).
Follow Google's email sender guidelines.
Monitor placement (Postmaster setup, blacklist tools).
Team-specific guides: agencies, SaaS, recruiters and SDR infrastructure.
Inboxes Built for Personalised Outreach at Scale
LiteMail | Infrastructure behind your merge tags
Fresh from $2.50/inbox
Official Google Workspace and Microsoft 365 inboxes ready for your sequencer
LiteMail provisions official Google Workspace and Microsoft 365 inboxes on secondary domains with SPF, DKIM and DMARC configured automatically and dedicated US and EU IPs, then exports them in bulk by OAuth to tools like Instantly, Smartlead and Lemlist — where your merge tags and sequences live.
Strengths | Keep in mind |
|
|
See pricing, the inbox calculator or pre-warmed Google Workspace and pre-warmed Microsoft 365.
Personalise every email — and send it from inboxes built for outreach. Get Pre-Warmed Inboxes →
Frequently Asked Questions
What are cold email merge tags?
Placeholders in your email copy that your sequencer replaces with each prospect's data, such as first name or company, at send time.
What's the syntax for merge tags?
It depends on the tool; many use double curly braces such as {{first_name}} or {{firstName}}. Check your sequencer's documentation.
Which merge tags should I use in cold email?
First name and company as basics, plus custom variables like a trigger or personal first line for real relevance.
What is a fallback value?
Text used when a field is empty, such as "there" instead of a missing first name.
How do I stop merge tags from breaking?
Match column names to variables, clean the data, set fallbacks and preview a sample of rendered emails before launch.
Is spintax the same as merge tags?
No. Merge tags insert prospect data; spintax rotates alternative phrases to vary wording.
Can I use merge tags in subject lines?
Yes, but vary patterns and make sure the data is clean, because errors are very visible there.
How many merge tags should a cold email have?
Few. One or two meaningful custom variables usually beat many standard fields.
Personalise Smarter, Send Safer
Authenticated Google Workspace and Microsoft 365 inboxes with bulk OAuth export to your sequencer.
Automated DNS · Dedicated IPs · OAuth export
About LiteMail — LiteMail provides fresh and pre-warmed Google Workspace and Microsoft 365 inboxes for cold email outreach, with automated SPF, DKIM and DMARC setup, dedicated US and EU IPs, separate client workspaces and one-click OAuth export to Instantly, Smartlead, Lemlist and other sending tools. View pre-warmed inbox plans →
Related reading: Cold Email Examples · Email List Building · Find and Verify Leads · Smartlead Configuration · Email Outreach 101 · Bulk Email Inboxes


