Skip to main content

Translate post-experience emails

Translate the subject lines and bodies of your email sequence, and know which language each learner receives.

Written by Cody Iddings

The emails that go out after a session can be translated along with the rest of the experience. Setting up the sequence itself is covered in Post-experience email sequence.

Which language a learner gets

Emails go out in the language the session ran in. A host running a French session sends French emails to everyone in it. Anything not translated falls back to English, field by field — so an untranslated subject line arrives in English even if the body is in French.

Translate subject lines

  1. Open the experience and click Translation in the experience's sidebar. It starts folded to icons and stays the way you leave it: hover an icon to see its name, or click the logo or drag its edge to open it. It appears once the experience has a second language.

  2. Scroll past the content rows to the Emails section.

  3. In an email's Subject line row, click the cell for your language and type the translation.

The Translation page scrolled to the Emails section, with an email's Subject line row and the cell for a translated language highlighted.
The experience editor with Translation highlighted in the experience's sidebar, below Email and above Settings.

Subject lines behave like any other translation cell. They have the same badges and the same custom marking when you edit by hand. If your organization has auto-translate, they also have the same per-field translate badge.

If your subject line contains a variable such as the experience title, it's preserved when you translate. Type around it rather than trying to retype it.

Translate email bodies

On the Translation page, bodies are a read-only preview. They can contain blocks that pull in session data, and those don't survive being edited as plain text. To write a body in another language:

  1. Click Email in the experience's sidebar.

  2. In the Editing language menu (a globe and the current language's name), choose the language.

  3. Edit the email as normal. Your changes go into that language's version.

The Email page with the Editing language menu open, showing the languages the experience supports.

If your organization has auto-translate, you can still translate a body from its cell in the Translation page. Only hand-editing has to happen on the Email page. See Auto-translate your content.

Send emails to a translator

Email subjects and bodies are included in the XLIFF export and import, so they travel with the rest of the experience's text. See Work in the Translation tab.

Did this answer your question?