Definition
A merge field is a placeholder in an email or message template that the sending platform replaces, recipient by recipient, with a value from that contact's record. The placeholder is written in the platform's own syntax, which is why the same thing is called a merge tag or a personalisation token in different tools. The value can be any field the record holds, such as a first name, a company, a last order date, a plan or a loyalty balance.
The guide to personalising email content sets merge fields beside two other forms of rule-based personalisation: content blocks, which swap whole sections of an email by rule, and recommendations, which choose products or articles for each person. A merge field changes how the email addresses the reader; a content block changes what it says.
Fallbacks and empty fields
Every merge field can go wrong in front of the reader in four ways, and each needs a decision before the send:
- Empty. The record has no value, and the greeting has a gap or a sentence stops making sense.
- Bad data. The value is wrong: capitals, a placeholder someone typed at sign-up, a company called "test".
- Stale. The value has changed since the data was last refreshed, such as an old balance or a former city.
- Exposed label. The raw tag appears instead of a value, usually in the plain-text part or the preheader.
The fix for the first is a fallback written for the sentence it sits in: a greeting falls back to a neutral greeting, and a sentence that names a last purchase falls back to one that makes sense without it, or is left out. The others are caught by cleaning obviously wrong values, using only fields refreshed before each send, and test sends with real records, an empty record and the longest plausible values.
In practice: when it helps, when it pretends, and links
A merge field helps when the value is something the reader would expect the business to know and the sentence reads naturally with it. It pretends when a name is dropped into a generic message. The guide to account-based marketing is blunt about this: pretending to personalise with a merge field and a generic message is worse than not personalising at all, because a buying committee notices. The guide to AI for marketing automation describes classic personalisation as merge fields and segments, the same template with a name and a few blocks swapped by rule, and contrasts it with content a model composes at send time, which nobody on the team may have seen.
Links are the hidden risk. The guide to personal data in analytics describes the route: someone building an email template adds a merge field to a link's campaign parameters to make it "personal", and every click then carries the subscriber's address into campaign reports. Its fix is a rule in the naming convention that bans personal merge fields in campaign parameters. The email campaigns section lists blank or wrong names among its common problems, with missing fallbacks and unchecked test sends as the cause.
A nursery fixes a blank greeting and a leaking link
Kleeffisk Hostas Nursery, an invented plant nursery, sends its spring catalogue email to 4,800 customers. About 700 records have no first name, so those customers receive "Hello ," with nothing between the word and the comma. The same week its analyst finds the subscriber's email address in the campaign content dimension of its analytics reports: a template edit had added the address merge field to the catalogue link's tag to "track who clicked". The nursery sets "Hello there" as the fallback, removes the merge field from every link, sends test emails to an empty record and a full one before each campaign, and asks the analytics owner to deal with the data already collected.
Related terms
Merge fields work inside the audience that SegmentationDividing a market or customer list into groups that need different offers or messages. has already chosen: segmentation decides who receives an email, and merge fields change how it addresses each person. The values they insert are usually Personal DataAny information relating to an identified or identifiable living person, such as a name, email address, location data or an online identifier., which is why a field the reader did not give, or would not expect the business to hold, should stay out of an email they might forward or read on a shared screen. And UTMURL tags identifying traffic source. tags on email links should describe the campaign, never the person, so no personal merge field belongs in them.
Common confusions
- A merge field is personalisation. It is the lightest form; a name in a generic message is not tailored content.
- One fallback for the whole account will do. The fallback is written for each sentence the field sits in.
- More fields make an email more personal. A first name repeated in the subject, opening and button reads as automation, not attention.
- Merge fields only affect the email. In links they can carry personal data into analytics.
- Testing with a full record is enough. Empty records and long values break emails just as surely.
