Why merge tags show a blank or raw code
A merge tag (also called a personalisation token, merge field or Liquid tag) is filled in by your email platform for each person. When the data is missing, the platform shows nothing, so “Hi {{ first_name }},” becomes “Hi ,”. When the code is written for another platform, or broken by a curly quote pasted from a document, the platform can show the raw code instead. A fallback (default value) fixes the first; checking the syntax fixes the second.
How to add a first name fallback in each platform
Klaviyo
Use the default filter: {{ first_name|default:'there' }}. It works the same in the subject line and preview text.
Braze
Braze uses Liquid: {{${first_name} | default: 'there'}}.
Customer.io and Brevo
Customer.io: {{customer.first_name | default: "there"}}. Brevo: {{ contact.FIRSTNAME | default : "there" }}.
Mailchimp
Mailchimp fills an empty *|FNAME|* from the default value set on the audience field (Audience, Settings, Audience fields and merge tags). To choose the wording in the email itself, use a conditional merge tag: *|IF:FNAME|*Hi *|FNAME|*,*|ELSE:|*Hi there,*|END:IF|*. If merge tags aren’t working, check the tag matches the field’s merge tag exactly and that the email is sent to the audience that has the field.
HubSpot
Set a default value when you insert the personalization token, or in HubL: {{ contact.firstname|default("there") }}.
Iterable
Iterable uses Handlebars: {{defaultIfEmpty firstName "there"}}.
Salesforce Marketing Cloud
Set a variable with AMPscript, then show it: %%[ SET @first = IIF(Empty(FirstName), "there", FirstName) ]%% then %%=v(@first)=%%.
ActiveCampaign and Dotdigital
ActiveCampaign’s %FIRSTNAME% has no built-in fallback, so use conditional content to show the greeting only when the field isn’t empty. In Dotdigital, set a default value on the data field.
What the checker looks for
- No fallback: tags for personal data (names, city, company, loyalty points) with no default, and stricter in the subject line and preview text, where a gap shows in the inbox.
- Broken code: unbalanced
{{ }}or{% %}, anifwith noendif, curly quotes from a document, and a default written without its colon. - Mixed platforms: tags copied from an email built in another platform, which show as raw text.
- Placeholders: [First name], {FirstName}, XXX, TBC and Lorem ipsum left in.
System values the platform always fills, such as the unsubscribe link and view-in-browser link, don’t need a fallback and aren’t flagged.
Frequently asked questions
What is a merge tag fallback?
The value an email platform uses when the data for a merge tag is missing, such as “there” in “Hi there,” when someone has no first name saved. Without one, people see a blank or the raw tag.
How do I add a default first name in Klaviyo?
Use {{ first_name|default:'there' }}. The same code works in the subject line and preview text.
Why are my Mailchimp merge tags not working?
Check the tag matches the audience field’s merge tag exactly (such as *|FNAME|*), that the email goes to the audience with that field, and that there are no spaces or curly quotes inside the tag. Set a default value on the field so empty ones aren’t blank.
Can I use merge tags in the subject line?
Yes, in every major platform, but always with a fallback: a gap in the subject line is the first thing people see.
Is my email uploaded?
No. The check runs in your browser and nothing is sent anywhere.