Mailfois
Guides / Translating emails without breaking merge tags
Guide

How to translate marketing emails without breaking merge tags

Why translation breaks merge tags (translated variable names, curly quotes, moved tags, untranslated fallbacks) and a process that stops it: protect the tags, translate the fallbacks, check every tag survived, and test with an empty field.

In short: merge tags break in translation because a person or a machine changes something inside them: the variable name gets translated ({{ first_name }} becomes {{ prénom }}), straight quotes become curly ones, spaces appear, or the tag is dropped while a sentence is rewritten. Protect every tag before translation so translators can see it but not edit it, translate the fallback text (the "there" in "Hi there") separately, then check that every tag in the original is in the translation character for character, and send a test to an address with the fields empty.

A broken merge tag is one of the most visible mistakes an email can make: a German customer reads *"Hallo {{ prénom }},"* or *"Hallo *|FNAME|*"* in the first line. And it's nearly always introduced during translation, by someone who was trying to help.

How translation breaks merge tags

  • The variable name gets translated. {{ first_name }} becomes {{ prénom }} or {{ nombre }}. The email platform has no field with that name, so it prints nothing, or the raw tag.
  • Quotes change. Word processors and some translation tools turn straight quotes into curly ones ('there' into ‘there’), which breaks Liquid, Django and AMPscript.
  • Spaces or punctuation are added inside the tag: *| FNAME |*, {{first_name }}., or a French non-breaking space before a colon that ends up inside the code.
  • The tag is lost when the translator rewrites the sentence and the tag doesn't fit the new word order.
  • The fallback isn't translated. {{ first_name | default: "there" }} sends "Hallo there" to every German subscriber without a first name.
  • Conditional blocks are split. An if/else block wraps two sentences in English, but the translation merges them, leaving an opening tag without its closing one.
  • Grammar around the name changes. Some languages need a different greeting or word ending depending on the name or gender, which a single "Hi {name}" pattern can't do.

The process that stops it

  1. Pull the copy out with the tags protected. Give translators each piece of text with the tags shown as fixed placeholders (for example, highlighted and locked), not inside an editable HTML file. Many machine translation services can also be set to leave tags untouched.
  2. Tell translators what each tag is. "This is the customer's first name" lets them build a sentence around it correctly, or tell you the greeting needs a different pattern.
  3. Translate the fallbacks as copy. List each fallback ("there", "friend", "your order") as its own line to translate, then put the translated fallback back into the tag yourself.
  4. Keep conditional blocks as whole units. Send each if and else branch as a separate piece of text, so the code around them never passes through translation.
  5. Check every tag survived. For each line, every tag in the original must appear in the translation exactly, character for character. Count them, then compare them.
  6. Check the numbers too. Prices, dates, percentages and codes should match the original (or be correctly localised, such as 10,00 € for €10.00).
  7. Test with an empty field. Send one test to a profile with a first name and one without, in each language, and read the first line of each.

Fallbacks, language by language

The fallback is the text shown when the field is empty, and it needs translating like any other copy:

LanguageGreeting with a nameFallback greeting
EnglishHi Anna,Hi there,
FrenchBonjour Anna,Bonjour,
GermanHallo Anna,Hallo,
SpanishHola, Anna:Hola:
DutchHoi Anna,Hoi,

Notice that the natural fallback in most languages is the greeting on its own, not a translation of "there". That's why fallbacks should be translated by a person who sees the whole sentence, not swapped word for word.

The syntax for fallbacks differs by email platform: Klaviyo, Mailchimp, HubSpot, Braze and the rest each have their own. The ESP cheat sheets show each platform's first name tag with a fallback.

Lines that grow in translation

German and French text is often longer than English, which breaks short fields before it breaks tags:

  • Subject lines over about 60 characters get cut off in many inboxes.
  • Preview text has room for roughly 90 to 100 characters.
  • Buttons look best under about 25 characters, or they wrap onto two lines.

Ask translators for a shorter version where a line runs long, rather than shrinking the font.

Questions

Why do merge tags break when emails are translated?

Because something inside the tag is changed: the variable name is translated, straight quotes become curly, spaces are added, or the tag is lost when the sentence is rewritten. The email platform then prints nothing or the raw tag.

Should merge tag fallbacks be translated?

Yes. The fallback is copy that customers read when the field is empty, so "Hi there" needs a natural equivalent in each language, which is often just the greeting on its own ("Hallo," or "Bonjour,").

How do I check translated merge tags?

Compare each translated line with the original: every tag in the original must appear in the translation exactly, character for character. Then send tests in each language to a profile with a first name and one without.

Can machine translation handle merge tags?

Many machine translation services can be told to leave tags untouched, but it's safer to protect the tags before translation and check them afterwards, because a single changed character breaks the tag.

*Checked on 9 November 2026.*

Written by Mailfois. Mailfois is built by someone who works in email marketing and also builds apps. About Mailfois.

Translate every market's email without a broken tag.

Try Mailfois free