Guide
Why merge tags show up in sent emails
A merge tag is an instruction to your email platform: put this contact's first name here. When the platform can't follow it, the instruction itself goes out. The usual reasons:
- The tag was written for another platform. A template copied from Mailchimp into HubSpot still says
*|FNAME|*, and HubSpot doesn't know what that means. - The field name is wrong.
{{ contact.first_name }}instead of{{ contact.firstname }}, or a field that exists in one audience and not another. - The editor broke it. Smart quotes, a line break, or bold applied to half a tag turn it into plain text.
- The test looked fine. Your test contact has a first name, so the test said “Hi Sam”. Thousands of real contacts don't, and they get “Hi ,”. That's what fallbacks are for.
- Placeholder text survived. “£XX”, “TBC” and “[LINK]” are meant to be replaced before sending, and on the fifth read nobody sees them any more.
Fallbacks, platform by platform
A fallback is what the reader sees when the field is empty. Every platform writes it differently:
| Platform | First-name tag | With a fallback |
|---|---|---|
| Mailchimp | *|FNAME|* | *|IF:FNAME|*Hi *|FNAME|*,*|ELSE:|*Hi there,*|END:IF|* |
| HubSpot | {{ contact.firstname }} | {{ personalization_token('contact.firstname', 'there') }} |
| Klaviyo | {{ first_name }} | {{ first_name|default:'there' }} |
| Braze | {{${first_name}}} | {{${first_name} | default: 'there'}} |
| Salesforce Marketing Cloud | %%FirstName%% | %%[ SET @name = AttributeValue("FirstName") IF Empty(@name) THEN SET @name = "there" ENDIF ]%%Hi %%=v(@name)=%%, |
| Iterable | {{firstName}} | {{defaultIfEmpty firstName "there"}} |
| Customer.io | {{customer.first_name}} | {{customer.first_name | default: "there"}} |
| Brevo | {{ contact.FIRSTNAME }} | {{ contact.FIRSTNAME | default : "there" }} |
| ActiveCampaign | %FIRSTNAME% | No inline fallback: use conditional content, or a greeting that reads well without a name |
| Constant Contact | [[FIRSTNAME]] | [[FIRSTNAME OR "there"]] |
| Campaign Monitor | [firstname] | [firstname,fallback=there] |
Pick a fallback that reads well in the sentence: “Hi there,” works; “Hi Customer,” doesn't. Read the greeting both ways before you send.
Template or test send: what to check where
In the template, merge tags are expected. Check that each one is written for your platform and has a fallback. Choose “Template” above.
In the test send, no merge tag should be left. Send the test to a contact with some fields empty (no first name, no company), then paste what arrived and choose “Test send”. Any tag still visible, and any “Hi ,”, is a mistake readers will see.
If a broken tag has already gone out, our guide to writing a correction email covers when one is worth sending and what to say.