A personalisation token is a placeholder in an email, such as {{ first_name }}, that your email platform replaces with each recipient’s own data when the message is sent. It lets one email greet “Priya” in one inbox and “Tom” in the next. You may also see it called a merge tag or merge field.
How personalisation tokens work
Every contact in your email service provider has fields: first name, company, town, last order date, loyalty points and so on. A token points to one of those fields. Each platform has its own syntax, often double curly brackets or a code wrapped in symbols, and most let you insert tokens from a menu rather than typing them.
When the email goes out, the platform looks up each recipient’s field and swaps it in. If the field is empty, it uses a fallback value you set, so “Hi {{ first_name }}” becomes “Hi there” rather than “Hi ,” with a stray comma. Tokens work in subject lines, preheader text, body copy and links, and some platforms allow simple conditions such as “if the town is Manchester, show this line”.
A token inserts a single value. When you want to swap whole blocks, such as different products for different customers, that is dynamic content, which draws on the same data.
Why it matters
Used well, tokens make bulk email feel less like bulk email. A reminder that names the service someone booked, or the branch they use, is more useful than a generic one. Used badly, they announce a mail merge: wrong names, shouting capitals copied straight from a form, or a first name dropped into every sentence.
Personalisation is only as good as your data. Many UK small businesses collect names inconsistently: a full name in one field from checkout, a first name from a newsletter pop-up, and nothing at all from older imports. Before relying on tokens, look at what is actually in those fields. There is a data protection angle too. Only collect fields you have a genuine use for, in line with UK GDPR’s data minimisation principle, and never show anything in an email that a recipient would find intrusive or surprising.
Common mistakes
- No fallback, so blank fields produce “Dear ,” or a visible code in the subject line.
- Raw data appearing exactly as entered: names in capitals, an email address in the name field, or “Test”.
- Over-use: the first name in the subject line, opening line and sign-off of every email until it reads like a sales script.
- Using sensitive or unexpected data, such as a health-related purchase, in a way the person would not anticipate.
- Testing only with your own record, which has every field filled in.
How to act on it
Export a sample of your contacts and check the name and company fields for blanks, capitals and junk. Tidy what you can, and set a sensible fallback for every token you use. Most platforms let you preview an email as a specific contact; preview it as someone with a complete record, someone with blanks and someone with odd data before every send.
Then ask which personal detail would actually help the reader. The order they placed, the course they enrolled on or the date of their next appointment usually does more than their first name. If you want help deciding which data to collect and how to use it in email, I cover this in my digital marketing strategy and consulting work.