What Are Merge Tags? A Platform-Agnostic Guide
Your cold email opens with "Hi {FirstName}," and 200 recipients see exactly that - the raw tag, not their name. Reply rates tank. Your brand looks amateur. So what are merge tags, really? They're dead simple in concept but surprisingly easy to break in practice.
The Short Version
Merge tags are placeholders that swap in real contact data - name, company, title - when your email sends. Every email tool uses them, just with different syntax. Personalized emails deliver 29% higher open rates and 41% higher click-through rates than generic messages, and personalized subject lines alone can boost opens by up to 26%.
The catch: these placeholders are only as good as the data behind them.
How Merge Tags Work
A merge tag is a placeholder that inserts dynamic contact data into a fixed email template at send time. You write one email. The tag pulls each recipient's unique information from your contact database and drops it into the right spot before the message lands.
The concept dates back to word processors, but modern ESPs and cold email tools have expanded what's possible far beyond "Dear {Name}." You can now insert discount codes, personalized links, conditional paragraphs, and compliance footers - all through merge fields. That "up to 26%" subject-line lift? It can come from adding a simple first-name token in the right place.
Three Steps, Every Platform
Your contact database stores a field (like "FirstName" with the value "Sarah"). Your email template contains a tag pointing to that field - *|FNAME|* in Mailchimp, {FirstName} in GMass. At send time, the platform replaces every tag with the corresponding value for each recipient. Sarah sees "Hi Sarah," Mike sees "Hi Mike." Same template, different output.
Don't confuse merge tags with dynamic content. Merge tags keep the email structure identical for every recipient and swap individual data points. Dynamic content changes entire sections - headlines, images, product blocks - based on segment logic. Most teams only need the simpler approach.
Syntax Across Platforms
Every tool does the same thing. The syntax just differs.
| Platform | Example "First name" tag | Style |
|----------|---------------------------|-------|
| Mailchimp | *|FNAME|* | Pipe + asterisk |
| GMass | {FirstName} | Single curly braces |
| EmailOctopus | {{FirstName}} | Double curly braces |
Copy-pasting tags between platforms is the fastest way to break personalization. Always check the docs when migrating templates.
Every merge tag pulls from your contact database. If that database is stale, your personalization breaks - or worse, sends "Hi Sarah" to someone who left that company two years ago. Prospeo refreshes 300M+ profiles every 7 days with 98% email accuracy, so your {FirstName} and {Company} tags always resolve to real, current data.
Fix your data upstream and never send a broken merge tag again.
Beyond First Name
These placeholders handle far more than names. Using Mailchimp's merge tag cheat sheet as a reference:
- Personalization: first name, last name, company, phone, address
- Compliance: unsubscribe links (
*|UNSUB|*), physical address, preferences center - Utility: send date, subject line echo, preview text, translation tags
- Ecommerce: unique discount codes, product recommendations, cart URLs
- URLs & tracking: tags inside link URLs for personalized landing pages or embedding recipient emails in tracking pixels
- Conditional: IF/ELSE blocks that show or hide content based on field values
Teams also use them to insert personalized PDF links stored in a custom field, unique discount codes per recipient, or even full custom paragraphs - one user wanted to insert roughly 100 unique words per contact via a spreadsheet column. That's ambitious, but the mechanism supports it.
Setting Fallback Values
Always set a fallback. If a contact's first name field is empty and you don't have a default, they'll see "Hi ," or worse, the raw tag. Generic syntax looks like this: Hello *|FirstName|Customer|* - if FirstName is blank, the recipient sees "Hello Customer."
HubSpot takes it further with global default values set once in settings and per-email fallback overrides. Use global defaults for common fields like first name, and per-email overrides when context demands something specific - like "fellow marketer" in a campaign targeting that persona.
Merge Tags in Cold Email
Cold email tools often add extras on top of basic personalization tokens. Smartlead ($33-78/mo) supports spintax - {Hi|Hey|Hello} rotates greetings to reduce pattern detection. GMass uses conditional blocks in both subject lines and body text, which makes it especially flexible for outreach.
Here's the thing: none of this matters if your underlying data is garbage. We've watched teams debug tag syntax for hours only to discover the real problem was a stale contact list. "Hi [blank], loved your work at [company they left 2 years ago]" is worse than no personalization at all. Prospeo handles this upstream - 98% email accuracy across 300M+ profiles, refreshed every 7 days, so your personalization fields pull clean, current information instead of dead data.
Why Your Tags Break
Five reasons, ranked by how often we see them:
Wrong syntax or casing. |FNAME| isn't *|FNAME|*. One missing asterisk and the whole thing renders as plain text.
Formatting broke the tag. You bolded text that includes a tag, and the rich-text editor inserted invisible HTML between the characters. Clear all styles around tags before sending.
Test emails don't populate tags. Contact-specific placeholders won't fill in during a test send. In Mailchimp, use Preview Mode with "Enable live merge tag info" or send to a small real segment.
Whitespace edge cases. A Reddit user reported that a space after *|IF: passed preview but failed on every real send. The only reliable test was sending to a small segment.
Missing or bad underlying data. This is the real problem, and it's upstream. Your tags work perfectly - there's just nothing to pull. The fact that many ESPs still don't include a syntax checker in 2026 is genuinely frustrating.
Let's be honest: if your bounce rate is creeping past 5%, stop tweaking syntax and fix your contact data first. Syntax errors are visible and easy to catch. Bad data silently poisons every campaign you send.
You've nailed the syntax. Your fallbacks are set. But if 15% of your list has outdated emails or wrong company names, personalization becomes a liability. Prospeo's 5-step verification and 7-day refresh cycle - not the 6-week industry average - means your merge fields pull clean data every single time.
Stop debugging tags when the real problem is your contact list.
FAQ
Are merge tags the same as personalization tokens?
Yes - different names for the same concept. Platforms use labels like "merge tags," "personalization tokens," or "merge fields," but the function is identical: insert dynamic contact data into a fixed template at send time. Pick whichever term your ESP uses and stay consistent.
Do merge tags work in subject lines?
In most ESPs, basic tags work in subject lines. Mailchimp's conditional tags don't. GMass supports conditional blocks in both subject and body, making it more flexible for cold outreach where subject-line personalization drives opens.
How do I keep my merge tag data accurate?
Set fallback values for every tag so blank fields don't produce awkward output. More importantly, verify contact data before it hits your sending tool - stale records silently kill campaigns. We've found that weekly data refreshes catch the job changes and bounced addresses that a monthly or quarterly scrub misses entirely.