Broken merge tags, the fastest way to prove it is mass mail
The short answer
A visible broken token, Hi {firstName} or Hi there when the data was missing, tells the prospect in one glance that your email is automated mass mail. It undoes all the relevance the rest of the email tried to build. Prevention is simple and non-negotiable: clean data, sensible fallbacks, and a test send before every campaign.
Nothing announces this went to a thousand people faster than Hi {firstName}, at the top of an email trying to feel personal. One broken tag erases the whole illusion, and the prospect stops reading right there.

Why a broken token is fatal
Personalization tokens exist to make an email feel written for one person. When one breaks visibly, it does the exact opposite, proving in a single glance that the email is automated and untargeted.
The damage is total and immediate. Everything after Hi {firstName} is read, if at all, by someone who already knows they are on a list. The relevance you worked for is gone before the first sentence.
The common ways they break
Most failures come from data, not the tool.
- Missing data, so the raw token or a blank appears.
- Wrong-case or malformed names, hi JOHN, hi john.smith.
- Mismatched fields, the company in the name slot.
- A default that shows, Hi there or Hi [First Name] as a giveaway.
Clean data is the real fix
Tokens break because the data behind them is dirty. The durable fix is upstream: a verified, well-formatted list where names are present and correct. This is the same discipline as verification and list building, applied to the fields you personalize on, not just the address.
Use fallbacks that pass as human
Set a default for every token that reads naturally when the data is missing. If a first name is absent, the fallback should be a normal greeting, not Hi {firstName} or Hi there in a way that flags the gap. A good fallback is invisible; the reader cannot tell the token did not fire.
Better still, do not personalize on a field you cannot rely on. A token you are unsure of is a risk; a clean generic line is safer than a broken personal one.
Always test before you send
The last line of defence is a test send to yourself and a couple of colleagues before every campaign, checking that tokens resolve and fallbacks read naturally. It takes two minutes and catches the mistake that would otherwise reach hundreds of prospects. Skipping it is how Hi {firstName} goes out at scale.
Frequently asked
Why is a broken personalization token so damaging?
How do I stop merge tags from breaking in cold email?
What should a personalization fallback be?
Rather not build this yourself?
We run the targeting, data, copy and follow-up as a done-for-you service, and send the interested replies straight to your inbox. You bring the close.
Book a strategy call