okaytosendStart free
Free tools

Merge tag and placeholder checker

Paste your email and we'll find merge tags that didn't fill in, tags with no fallback, and placeholder text left from the draft: the “Hi *|FNAME|*” and “£XX” that slip through. Works with Mailchimp, HubSpot, Klaviyo, Braze, Salesforce and more. Nothing you paste leaves your browser.

Up to 200,000 characters: a whole HTML email fits.
Choose one to catch tags written for a different platform.
Is this the template or the test send?
Merge tags are expected; tags without a fallback are flagged.
Nothing you paste leaves your browser.

Guide

By The Okaytosend team · Updated
GreetingThe email said Hi *|FNAME|*,, the source says Hi Sam,

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:

First-name tags and their fallbacks. Check your platform's help for other fields.
PlatformFirst-name tagWith 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.

Questions

Why does my email say *|FNAME|*?

Mailchimp didn't replace the tag. Usually the email was sent through something that doesn't read Mailchimp's tags, the tag doesn't match a field in that audience, or the editor split it with formatting. Paste the email above and choose Mailchimp: tags in the wrong syntax and broken tags are flagged.

What's a good fallback for a first name?

A word that makes the sentence read well without a name: “Hi there,” or just “Hello,”. Avoid stand-ins like “Customer” or “Valued member”, which read worse than no name at all.

Can I recall an email with a broken merge tag?

No. Once it's sent, it's in the inbox. If the broken tag is only in the greeting, a correction usually isn't worth it. If it hides a price, a code or a link, send a short correction with the right fact in the subject line.

Which platforms does it understand?

Mailchimp, HubSpot, Klaviyo, Braze, Salesforce Marketing Cloud, Iterable, Customer.io, Brevo, ActiveCampaign, Constant Contact and Campaign Monitor, plus common forms such as {first_name}, ${first_name} and «First Name».

Is the email I paste sent anywhere?

No. The check runs entirely in your browser. Nothing you paste is sent to us or stored, and there's no sign-up.

More free tools

  1. Date and weekday checker

    Check every date in an email against its weekday, or find the day of the week for any date.

  2. Time zone converter for event emails

    One line with every time zone right for your event's date, EST or EDT included. Or check a line you've written.

  3. From the blog

    How to write a correction email

Cookie settings