Creating Multilingual Campaigns

Using multilingual workflows, you can send one message that dynamically displays different language versions to your subscribers.

📘

Important

The system automatically determines the language for a campaign based on one of the algorithms:

1. If the event doesn’t determine the language, the message will be sent in the language specified in the user profile. This is convenient for the existing base.
2. If the event determines the language, the message will be sent in this language. The language specified in the user profile will be ignored.
3. If the language isn’t determined by the event and isn’t specified in the user profile, the message will be sent in the default language.

Creating Bulk Campaign

The process of scheduling/launching a bulk multilingual campaign is standard:

• select a multilingual message,
• move to Campaigns,
• select a segment,
• schedule or send a message.

The system will automatically send the necessary content to the corresponding contact. You don't need to build segments based on the language.

Creating Triggered Workflow

Place a single message or Obligatory email block in the workflow.

1. If you are going to use multilingual email:

• Copy the name of the variable responsible for the language code from the event you link to the workflow.
• Wrap the variable in a dollar sign and curly braces in the languageParam field of the workflow block.

2. If you use one of the single message blocks except for email, there is no languageParam field. This means the message will be sent in the language specified in the user profile. The message will be sent in the default language if the language isn’t specified in the user profile. If you need to determine language by the event, use conditional workflow blocks.

Using workflow condition blocks for multilingual campaigns

1. Create separate messages for every language you want to use.

2. Add the condition blocks with such settings to the workflow:

• Task name — Variable matches regular expression,
• name — variable name (eg, Language),
• pattern — regular language code value checked for compliance.

Each condition block should check if the event variable matches the specified pattern.

• If it does — the workflow goes by Yes brunch, which should be connected with the message in the corresponding language;
• If it doesn't — the workflow goes by No brunch, which should be connected with the following condition block.

The last condition block should be connected with the message on the default language by both branches. This way, if the event variable doesn’t match any specified pattern, such users will receive this last message.