Skip to main content
A multilingual campaign uses the same four-step builder as any other campaign: Compose → Audience → Schedule → Review & Send. This page walks through what changes in each step once the campaign links a template with more than one language.

​
Compose

Choose Use template and pick a template that carries a language badge. The campaign reads the template’s languages immediately, so there is no need to save the draft first. The linked-template header confirms the choice. The template name is followed by the language badge, such as EN · DE. Hover the badge to see every language with the primary one marked: English (EN) · primary, then German (DE).

​
Subject and sender

The Subject, From email, From name and Reply-to fields at the top of the step belong to the primary language. They are also the values every other language inherits unless you override them.

​
Per-language subject and sender

Below the sender fields, a Per-language subject and sender section appears with one collapsible row per secondary language. Each row shows the language code, the language name, and, once you have filled something in, a count such as 2 custom fields. Click Edit to expand a row and Hide to collapse it. The Per-language subject and sender section in the Compose step with the German row expanded, showing subject, from email, from name and reply-to fields Every field in a row is optional: The most common setup is a translated subject and nothing else. Fill in the subject, leave the rest empty, and the language sends from the same address as the primary. The From email field works like the primary one: a local part plus a domain chosen from your verified sending domains. A language version can never go out from a domain your team does not own. Lettr checks this when the campaign is saved and shows a problem on the field itself. It checks again when you click Send or Schedule: if a per-language domain is no longer verified, the campaign is not started and a message tells you why. Fix or clear that row’s From email and try again. Per-language values are stored by language code and belong to the draft, not the template:
  • If a language is removed from the template, its row disappears from the campaign. Its values are kept and come back if the language is added again.
  • If the template’s primary language changes, the main fields at the top now belong to the new primary. The old primary becomes an ordinary row with no values of its own, and anything you had entered for the new primary is no longer used. Rewrite the main subject in the new primary language and give the old primary its own subject.
Use a per-language from name when your brand is spelled differently by market, and a per-language reply-to when replies should reach a team that reads that language. Both are cheap to set and recipients notice them.

​
Merge tags in every language

Merge tags such as {{first_name}} work in every language version, filled from the recipient’s own contact properties. In the template editor, the merge-tag menu for marketing templates has an Audience group listing the recipient’s email and every property your team has defined, so translators can insert the right tag without knowing its exact name.

​
Audience

Choose recipients the way you always do. Two things help specifically with languages:
  • An early warning. If no contact property holds a language, an amber notice appears under the audience selector as soon as an audience is selected and the recipient estimate loads. It says that every recipient will get the primary language, and its Set a language property button opens Audience → Properties so you can fix it before reaching the review step. See Contact language.
  • Segments with is empty and is not empty. Build a segment on your language property to find contacts with no value before sending, or to exclude them. See Finding contacts without a language.

​
Schedule

Nothing changes in this step. The moment you schedule or send, Lettr saves a copy of the template in every language and uses that copy for the send. See Content is locked when you schedule.

​
Review & Send

​
The review panel

The Multi-language send panel is the place to confirm who gets what before anything goes out. The Multi-language send panel listing English as primary with 101 recipients, German with 40 and French with 39, each with subject, from and reply-to, and a fallback block below From top to bottom: Language taken from. The property Lettr reads the language from, with a tag saying how it was chosen:
  • designated language property: you ticked Use as communication language on this property.
  • matched by property name: no property is designated, so Lettr took the first defined property named communication_language, communication_lang, language, lang or locale.
One row per language. The primary language is first and marked Primary. Each row shows:
  • how many recipients will get this language,
  • the Subject, From and Reply-to that language will actually use. Values you overrode in the Compose step carry a Custom tag. Values without the tag are inherited from the primary language. From is tagged when either the from name or the from email is overridden.
Fallback. Shown when at least one recipient will get the primary language for lack of a match, for example 85 of 97 recipients will get English (EN), the primary language, broken down into:
  • how many contacts have no language value at all,
  • how many have a value that matches no template language, listed as chips with counts such as it ×6 or nl ×3. The five most frequent values are listed. The count in front of them covers all of them.
If every recipient matches a template language, the panel says so instead.
If the panel shows an amber box titled Every recipient will get English (EN), the primary language, Lettr could not find a contact property that stores languages. The campaign will still send, but nobody will receive a secondary language. Click Set a language property to open Audience → Properties, designate the property, and come back. The panel updates on its own.
Recipient counts in the panel are computed from your current audience selection and current contact values. They are recalculated when the campaign starts, so a contact whose language changes between review and send gets the language they have at send time.

​
Sending a test email

The Send a test email box gains a language picker when the template is multilingual. Choose Primary or any secondary language, enter an address, and send. Secondary languages are listed by their code, such as de. The test uses that language’s content, subject, from address and from name, as a matching recipient would receive them. Test emails are sent without a reply-to, so check each language’s reply-to in the review panel instead. You can send one test every 10 seconds. The Send a test email box with the language picker open, listing Primary (en), de and fr, next to the recipient address field Test emails use sample contact details for merge tags. Send one test per language before a real send. A translated subject with a typo is much easier to catch in your own inbox.
Need to see the email as a specific person would receive it? Open the campaign’s detail page and click the email thumbnail. The preview dialog lets you choose Audience contact, search the campaign’s audience by email, and render the exact language and merge values that contact would get.

​
Abuse screening

Lettr screens campaign content before release. When a multilingual campaign is screened, every language version that has at least one recipient is checked, not only the primary. If any version is flagged, the campaign goes into review and the report shows the version with the highest risk score. See The “In Review” state.

​
Next Steps

Sending and results

What each recipient gets, content locking, and per-language results after the send

Sending and scheduling

The campaign lifecycle from Draft to Sent