Merge tags (personalization tokens)
Merge tags, also called personalization tokens or merge fields, are placeholders in a message template — like {{first_name}} or {{company}} — that are automatically replaced with each recipient's data at send time. They let one template produce individually personalized messages at scale without manual editing.
How it works
The template references fields from your CRM or list (first name, company, title, a custom snippet). At send, each tag is swapped for the recipient's value, ideally with a fallback default so a missing field doesn't leave a blank or a raw {{tag}} in the message.
Why it matters
Personalization lifts reply rates, but broken merge tags — an empty value or a visible {{first_name}} — instantly signal automation and damage credibility. Reliable merge requires clean, verified data and sensible fallbacks, which is why enrichment and personalization go together.
Which merge fields are worth using in B2B outreach?
First name and company are the baseline and no longer impress anyone on their own. The fields that change reply rates are the ones only you could have filled in: a custom first line written per prospect, the tool they use, a recent event, a mutual connection, or the specific team you think owns the problem. Many teams keep one free-text column, often called something like opener or icebreaker, and fill it by hand or with AI for the top-priority accounts.
Title fields are risky. Job titles in purchased data are often long, inconsistent or out of date, and "as the Senior Vice President, Global Revenue Operations and Enablement" reads worse than no title at all. Cold email personalization examples shows what good per-prospect lines look like.
How do you stop a broken merge from reaching a prospect?
Check the data before the template. Sort the list by each field you plan to merge and look at the top and bottom of the column: empty cells, ALL CAPS names, company names with legal suffixes like "Pvt. Ltd.", and first names that are actually full names all show up there. Clean those first, then set a fallback for every tag, such as "there" for a missing first name.
Then preview the rendered message for five to ten real contacts, including at least one with missing data. A preview catches casing problems ("Hi ANANYA") and grammar that breaks when a field is empty. How to clean your email list covers the data side, and email personalization at scale covers when manual lines beat tokens.
Do merge tags work the same on SMS and WhatsApp?
The idea is the same but the constraints are tighter. SMS messages are split into segments once they pass 160 GSM-7 characters (or 70 characters if any character forces Unicode encoding), so a long company name can push a message into a second segment and double its cost. WhatsApp business-initiated messages have to use a template approved by Meta, and the variables in that template are numbered placeholders whose position and meaning are fixed at approval time.
So the merge values for those channels need to be short and predictable. A per-prospect free-text opener that works in an email usually does not belong in an SMS or a WhatsApp template. See WhatsApp templates for how template variables are approved.
What is the difference between a merge tag and real personalization?
A merge tag inserts a stored value. Real personalization is a reason to write to this person that would not apply to their competitor. "Hi {{first_name}}, I saw {{company}} is growing" uses two tags and says nothing specific. "Saw the Pune warehouse opening last month; teams that add a second site usually hit the same routing problem" uses no tags at all. The practical approach is to use tags for the parts that genuinely vary by data (name, company, city) and write or generate one specific line per high-value prospect, stored in its own field.
How Autocloz handles it
Autocloz feeds verified, enriched contact fields into personalization tokens across every channel's templates, with fallbacks, so merged messages stay accurate and never expose a blank or raw tag to the recipient.
Free tools for this
No signup required — they run in your browser.
FAQ
What happens if a merge tag has no value?
Without a fallback, you risk sending a blank or a visible raw tag like {{first_name}}, which looks broken and automated. Always set default fallback text (for example, 'there') and verify data quality before sending to avoid embarrassing merges.
Are merge tags the same across channels?
The concept is identical, but the syntax and available fields vary by tool and channel. The key requirement everywhere is clean, populated source data plus fallbacks, so the personalization renders correctly in email, SMS, LinkedIn or WhatsApp.
Related terms
Multichannel sequencing is automating a coordinated outreach cadence across more than one channel — for example email, then a LinkedIn touch, then a call, then a WhatsApp follow-up — from a single sequence, with per-channel timing and safety rules.
Cold email is an unsolicited but permission-conscious, personalized outreach email sent to a prospect you have no prior relationship with, for a business purpose. Done well it is targeted and relevant (not bulk spam) and complies with laws like CAN-SPAM and GDPR.
A sales cadence (or sequence) is a structured, time-based series of outreach touches — emails, calls, LinkedIn actions, texts — designed to reach a prospect across multiple channels and attempts before disqualifying or moving on. It defines what to send, on which channel, and when.
Account-Based Marketing (ABM) is a B2B go-to-market strategy that treats individual high-value accounts as markets of one — coordinating marketing and sales to target a defined list of named accounts with personalized, multichannel outreach, rather than casting a wide net for individual leads.