10

Getting started

You can store your audience’s language preferences as an attribute, and then use that attribute to send people messages in their preferred language!

How it works

When you add or update people, you can set an attributeA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc. Use attributes to target people and personalize messages. Attributes are analogous to traits in Data Pipelines. containing their language preference. Then, when you set up messages, you can click Add language to add one or more languages. You’ll set up your Default message, and then add content for each language.

When you send your message, people whose language attribute matches one of your message’s languages will receive the appropriate localization. Everybody else receives the Default message.

Multi-language support

1. Set your language attribute

Before you can send localized messages, you need to go to Workspace Settings > Language settings and tell us what attributeA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc. Use attributes to target people and personalize messages. Attributes are analogous to traits in Data Pipelines. stores your audience’s language preferences. This attribute must store values we support, meaning they’re either:

• a two letter language code, like en for English
• a four-letter language and region code, separated by a dash, like en-US for English speakers in the United States.

Go to Set up your localization attribute for more info.

2. Set up a multi-language message

When you create a message with multiple languages, you should always begin by drafting your Default message. This is the message intended for anybody who doesn’t match another language and should represent your “template” for other languages.

If you plan to send email content to a translation vendor, you’ll want to set up and export your Default message first, and then add languages when you receive them. Check out our best practices for help exporting email messages for your translation vendor and the quickest way to add your multi-language content.

1. Drag a message into your workflow then click it to view settings on the left.
2. Set a Name for your message, and click Add Content.
3. Click Add language then check the languages you want. Click Add.

   

   
4. Draft your Default message. This message should act as a “template” for your other languages. It will be the fallback if your customers do not have a language attribute.
5. Add your content for each language. Use the tabs at the top of the message to switch between languages.

   

   
6. When you’re done, save your changes.

Best practices

Export email to HTML for vendors

When you set up a message with multiple languages, you may need to send content to a translation vendor. To simplify this process, we suggest that you draft, test, and finalize your Default message first.

We recommend you export emails to HTML before you send them to a translation vendor:

• If you created your email with the drag and drop editor, click Actions > Export to HTML.
• If you created your email with the rich text editor, click HTML underneath the email header to copy/paste the source code.
• If you used the code editor, you can copy your email out to a separate file.

Add translations for email from vendors

When you receive your translations from your translator(s):

• If you exported your HTML originally, copy/paste the translated HTML back to the rich text (click HTML first) or code editors. If you used the rich text editor, you may need to reformat text after pasting.
• If you didn’t export your HTML, or you used the drag and drop editor, paste localized text back into the blocks of your message.

Consider liquid values

You might use liquidA syntax that supports variables, letting you personalize messages for your audience. For example, if you want to reference a person’s first name, you might use the variable {{customer.first_name}}. to personalize your message for your audience. Liquid doesn’t account for translations; we use the values stored on people’s profiles. Therefore, you’ll want to store values in native languages or use a set of static values.

If using static values, request your vendor translate these, too. Then you can use if statements to set specific, translated values depending on your audience’s language attribute.

{% if customer.language == 'fr' %}
  Bonjour
{% elsif customer.language == 'es' %}
  Hola
{% else %}
  Hello // Default value
{% endif %}

Multi-language metrics

When you send a message with multiple languages, we show metrics for each language. These metrics can help you make sure that your messages perform well in all of your audience’s languages.

Supported languages and locales

You must format the values of your language attribute as two-letter language codes with an optional two-letter region code separated by a dash, like en or en-US.

Language attributes are not case sensitive, but language-region codes must be separated by a dash. For example, both es-MX and es-mx represent Spanish formatted for speakers in Mexico.

These codes come from the ISO-3166-1 (alpha 2) and IETF standards respectively. If you’re looking for a language or locale that we don’t support, let us know!