Cold Email Merge Tags: Personalization Variables That Actually Work

By Puzzle Inbox Team · Apr 23, 2026 · 8 min read

Merge tags like {{first_name}} and {{company}} are the foundation of cold email personalization. Here is how to use them without breaking deliverability.

What Are Merge Tags in Cold Email?

Merge tags (also called personalization tokens or placeholders) are variables in your cold email copy that get replaced with data from your prospect list at send time. Every cold email sending platform supports them: Instantly, Smartlead, Lemlist, Reply.io, and others all use similar syntax — typically {{first_name}}, {{company}}, {{custom_variable}}.

Standard Merge Tags Every Cold Email Needs

• {{first_name}} — the prospect first name; never use last name alone in cold email
• {{company}} — the company name; this is how you anchor relevance
• {{job_title}} — the prospect role; useful for role-specific framing
• {{city}} or {{country}} — geographic variables for regional plays
• {{industry}} — industry variable for vertical-specific campaigns

Custom Merge Tags That Drive Reply Rates

The basic tags above are table stakes. The merge tags that actually move reply rates are custom variables you build yourself. Examples:

• {{funding_stage}} — Series A, Series B, etc.
• {{recent_news}} — a specific news article or announcement
• {{tech_stack_tool}} — a specific tool they use (scraped from BuiltWith or similar)
• {{job_posting}} — a role they are hiring for
• {{competitor_used}} — a competitor solution they use
• {{first_line}} — a pre-written opening line per prospect

Tools like Clay and Apollo let you enrich prospect lists with custom fields that you then map to merge tags in your sending platform.

The Fallback Problem (Why Bad Merge Tags Kill Cold Email)

The fastest way to destroy a cold email campaign is a broken merge tag. "Hi {{first_name}}" becoming "Hi {{first_name}}" or "Hi ," or "Hi null" in the actual sent email is an instant delete and sometimes a spam flag. Every merge tag needs a fallback value.

Syntax varies by platform but the concept is universal: {{first_name|there}} renders "there" if first_name is missing. Always test with missing data before launching.

How to Test Merge Tags Before Sending

1. Send yourself a test: Add your own row to the prospect list with all fields filled. Check the rendered email.
2. Test with missing data: Add a row with first_name blank. Verify fallback renders correctly.
3. Test edge cases: Special characters in names (O'Brien, umlauts, hyphens). Long company names that might break formatting.
4. Preview in the platform: Every cold email platform has a preview mode. Scroll through 10+ prospect previews before launching.

Advanced Merge Tag Patterns for Cold Email

Conditional Blocks

Some platforms support if/else logic based on field values: {{#if funding_stage == "Series A"}} [Series A specific copy] {{/if}}. This lets one email template serve multiple segments.

Nested Merge Tags

Occasionally used for compound personalization: "{{recent_news|{{job_title}} at {{company}}}}" — if recent_news exists use it, otherwise fall back to the role/company combo. Not all platforms support nesting.

Dynamic Date Tags

{{current_day}} or {{current_month}} let you reference the time of sending without hardcoding. Useful for campaigns that run over weeks.

Common Cold Email Merge Tag Mistakes

• No fallbacks: Every tag needs a default value. "Hi {{first_name|there}}" is non-negotiable.
• Over-personalization: Stuffing 8 merge tags into one email feels mechanical. 2-3 well-placed tokens beat 8 basic ones.
• Wrong syntax: {{first_name}} vs {FirstName} vs {{ first_name }} varies by platform. Check docs.
• Using merge tags in subject lines without testing: Broken merge tags in subject lines hurt opens more than broken body tags.