Email Marketing

Personalization Token

Also called Merge tag, merge field

A placeholder replaced at send time with a contact's own data, such as their first name, city or last order.

Quick facts: Personalization Token

Category
Email Marketing
Also called
Merge tag, merge field
Level
Beginner
Affects
Open decisions, perceived relevance, trust in the sender
Where to see it
Merge tag or personalisation menus in Mailchimp, Klaviyo, HubSpot; contact field settings in your CRM
In this article4
  1. How a personalization token works
  2. Why personalization tokens matter
  3. Common mistakes with personalization tokens
  4. How to act on it

How a personalization token works

A token is a marker you type into a subject line or an email body where a value should appear. When the message is queued for a particular contact, the platform looks up that contact’s record, finds the matching field and swaps the marker for whatever it holds. The recipient never sees the marker, only the result.

Two things decide whether that works. The first is the field itself: a token can only print data the contact record actually stores, so a token for company name on a list collected by an email-only signup form has nothing to print. The second is the fallback, a default value you set for exactly that case. Most platforms let you define one per token, and the ones that do not will simply print a gap.

Why personalization tokens matter

Used well, a token turns a broadcast into something that reads as though it was written for the person holding the phone. That earns attention in an inbox where most messages are visibly mass-produced, and it makes the rest of the email feel more relevant even when the body text is identical for everyone.

Used badly, the same mechanism does the opposite. A visible broken token is the clearest possible signal that a message was machine-generated and unchecked, and a reader who sees one stops trusting the rest of the email. The stakes are therefore asymmetric: the upside of a working token is modest, the downside of a broken one is large.

Common mistakes with personalization tokens

The most common is having no fallback, so contacts with a blank field receive a greeting that trails off or shows raw markup. Close behind is dirty data: names entered in capitals, full names typed into a first-name field, or a field holding a placeholder someone typed at import. Tokens print faithfully whatever is stored, including nonsense.

A third mistake is using a token because the field exists rather than because it helps. Repeating someone’s name several times in one email reads as pressure, not familiarity, and referencing data a customer did not knowingly give you feels intrusive. Personalisation that is not relevant is just decoration with a failure mode.

How to act on it

Set a fallback on every token before you use it, and make the fallback read naturally on its own, so the sentence works whether or not the field is filled. Then send test emails to records that are deliberately incomplete, not just to your own tidy contact — a token only fails on the records you did not think about.

Clean the data at the point of collection rather than after. Ask for the pieces you will actually use, keep the field labels obvious on your forms, and tidy imported lists before the first send. Once the basic fields are reliable you can move beyond names to genuinely useful references, which is where segmentation and dynamic content take over from single tokens.

Do and do not

Do

  • Set a natural fallback value on every token
  • Test sends against records with missing or messy fields
  • Collect clean first names separately on your forms

Do not

  • Repeat a contact's name several times in one email
  • Use a token just because the field exists
  • Import a list without checking capitalisation and stray placeholders

Questions people ask about this

What happens if the field is empty?

The platform prints whatever fallback you defined for that token. If you defined none, the result depends on the platform: some print nothing and leave an awkward gap in the sentence, others print the raw marker so the recipient sees the code. Always set a fallback that reads naturally, then test with an empty record.

Is using someone's first name still worth doing?

It is worth doing when the data is clean and used once, in a natural place. It is not a substitute for relevance. An email addressed to the right person about something they do not care about still fails. Fix what you are sending and to whom first, then add the name.

How do I stop names printing in capitals or with odd spelling?

Clean the source. Most bad values come from imports and from forms that ask for a single full name, then map it into a first-name field. Standardise capitalisation in your list before sending, ask for first name separately on forms, and spot-check the records that came from older sources.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.