Merge Tag
A merge tag is a coded placeholder, such as *|FNAME|* or {{first_name}}, that an email platform replaces with a subscriber's specific data when the email is sent.
Key takeaways
- The tag name is the contract between an import column and every template using it.
- Field type governs formatting: a date stored as text renders differently for each row.
- System tags such as the unsubscribe URL come from the platform, not your data.
- Merge tags read a single row and cannot compute or look up related values.
- Conditional merge syntax lets one field switch a whole sentence, not just a word.
In depth
Every audience in an email platform carries a set of named merge fields, each with a tag name and a declared type such as text, number, date or address. At send time the compiler walks the message, replaces each recognised tag with the value from that subscriber's row, and leaves anything it does not recognise untouched. Alongside your own fields sit system tags supplied by the platform itself, including the unsubscribe URL, the web archive link and the current date, which resolve without any column behind them.
The tag name is the contract between an import file and every template that references it. Rename a column and the mapping silently changes; the old tag then points at an empty field and renders nothing for every contact imported afterwards. Field type is the second lever, because a date stored as text formats however each row happens to be written, while a typed date field renders consistently. Adding fields makes personalisation richer and imports more fragile at the same time.
In practice, keep a short dictionary that lists each tag, its type, and the form or file that populates it, and map columns explicitly on every import rather than trusting automatic matching. Conditional merge syntax extends the idea, letting one field switch a whole sentence instead of a single word. Where a scorecard funnel feeds the audience, mapping the tier and the captured answers to fixed tag names once means every later campaign can reference them without touching the import again.
A merge tag reads one row and nothing else. It cannot compute a value, look up a related record, or combine two fields, so anything derived has to be calculated before the data reaches the list. Tags also resolve into the plain-text part, where formatting differs and a carefully styled value can look wrong. And because the resolved message is what gets forwarded, a value merged for one recipient travels to whoever they pass the email on to.
Example in practice
How to measure it
Before measuring performance, verify resolution. Send seeds to test rows that cover a filled value, an empty value, and an awkward one such as a name with an apostrophe or an accented character, then read the result in both the styled and the plain-text parts. After launch, the number worth reporting is how many recipients had no value for each tag the campaign used.
Then check whether the merged field changed behaviour, by comparing click rate among recipients whose value resolved against those who fell back to the default. If both groups behave identically, the tag is decoration and can go. Where tags feed link parameters, confirm the click reports carry the expected values, since a malformed URL surfaces as missing attribution rather than as an error.
Common mistakes
The most damaging mistake happens at import. A column renamed from Company to Company Name is mapped as a new field, the tag in your templates keeps pointing at the original and now-empty one, and every contact loaded after that day renders a blank. Freeze the tag names and map columns to them explicitly each time you upload a file. A short field dictionary, reviewed whenever the form changes, prevents almost all of this.
The second is pasting copy between platforms with different conventions, so a tag written in one syntax arrives as literal text in another. Search the finished template for both bracket styles before scheduling. Merging a value into a link is a related trap: a company name containing a space or an ampersand breaks the URL unless the value is encoded, and the result looks to the recipient like a broken link rather than a merge fault.
Frequently asked questions
How do I get reliable data for merge tags?
Capture fields through structured forms or quizzes and keep your list clean so values are consistent. A quiz funnel records names, company, and score tiers as tidy fields you can merge into nurture emails.
What is the difference between a merge tag and a personalisation token?
They describe the same mechanism from different vocabularies. Merge tag is the term used by email service providers built around audience lists and columns, while personalisation token is more common in marketing automation platforms built around contact records and properties. Practically, merge tags tend to be list-scoped and token names tend to be account-wide, which matters when you move between tools.
What syntax do merge tags use?
It varies by platform. One family uses pipe-and-asterisk delimiters around an uppercase field name, another uses double curly braces around a lowercase property, and some support both. The syntax is not interchangeable, so copy moved between tools has to be rewritten. Check your platform's field settings page, which lists the exact tag for each field.
How do I set a default value for a merge tag?
Most platforms accept a fallback inside the tag itself, written after a separator such as a colon or pipe, and some also let you set a default on the field definition so it applies everywhere. Prefer the field-level default when the value is the same across campaigns, and the inline fallback when the sentence needs different wording.
Can merge tags be used in links and subject lines?
Yes to both, with care. In a link the value must be URL-encoded, otherwise spaces and symbols break the destination. In a subject line, long values push the rest of the text past the truncation point on mobile, and an unresolved tag is highly visible there. Test both cases with a seed before scheduling anything.
Why is my merge tag showing as raw text in the delivered email?
The platform did not recognise it. Common causes are a syntax mismatch after copying from another tool, a field that was renamed or deleted, a typo in the tag name, or a tag placed somewhere the compiler does not process, such as inside an image attribute. A seed test to your own address catches every one of these.
Can merge tags handle conditional logic?
Many platforms support conditional merge blocks, which show or hide a section depending on a field value. That covers simple branching such as one sentence for a high tier and another for a low one. Anything more complex, particularly conditions across several fields, is usually easier to build as a dynamic content block or as separate campaigns.