Properties

Name

Name of the preference.

Priority

Priority relative to other preferences. Lower values have higher priority and are tested first. The first preference whose Condition is true is the one used.

Group

Identifies the preference as belonging to a common group of preferences. By default, all preferences belong to a group named default.

Only one Language Preference set of languages is used from each group: the first preference found, in Priority order, whose Condition matches the record. When all preferences belong to the same group, only the languages from the first preference are used.

Companies often define two groups of preferences: CustomerCountry is invitee's preferred local, and UnitCountry is the local where the Unit is located. This allows the Distribution setting to create an Invitation email that includes both the customer's and the Unit's languages. So, for example, an invitee from Japan interacting with a Unit in Montreal Canada might get an invitation in Japanese, French, and English. However, when the language preferences are all in the same Group (default), the same Invitation email might be in Japanese only (assuming the Priority and Condition for Japanese came first).

Stop if match

Whether or not to evaluate subsequent Groups after a match is found on an earlier Group. For example, when using CustomerCountry and UnitCountry, you can use this option to skip the UnitCountry group after finding a preferred language for the customer. If no preference was found, then use the Unit preference.

No English

Whether or not to automatically append English to the list. When selected, English is added to the list . So, for example, when the limit is 4, English id not added when there are already four languages in the list.

Condition

Identifies the record the Language preference applies to. The first preference (in Priority order) whose Condition is true is the one used. The Condition expression should reference at least one field in the record, such as Country (e_country) or a Unit group field such as Orion country (orion_property_country).

When using a field based on the Country Alt Set, such as e_country, use the ISO-3166-1 two-character identifiers, such as US, CA, and MX.

When using a field based on a Unit Data Field or Group Data Field, the value must match the values in the field's Alt Set.

When using a custom data field, always use sequence numbers as values, even if the field's Alt Set contains string values. For example, if the field Customer country (e_customer_country) contains 2-character country identifiers as values, refer to the countries by sequence number in the condition.

Member languages

Language(s) to add when the Condition is met. Select the target language(s) from the list of all known to Experience Cloud languages.

The selected languages should also be in the set of languages available for Surveys as noted on the Locales screen.

Example setup

A multi-national European company has customers that speak several languages, and the company locations are in several countries. This setup allows an Invitation email to include the invitee's country language (when known), the language(s) of the country the Unit is in, and English (if there is room).

The key here is the two different Group settings allows one preference from each group:

For more information, see Survey emails.

Multi-language emails

When the final list has more than one preferred language for a record, Experience Cloud attempts use a special Multi-language email. This template allows the invitee to choose their language (for HTML formatted emails) from the preferred list. Additionally:

• When there is only one language in the list, or when there is no multi-language template, Experience Cloud selects the template matching the first language in the list.

• There can be one multi-language template for each Invitation, Reminder, and Auto-reply emails.

Test a multi-language setup

Multi-language setups can be complex and testing is challenging, especially on a production environment where you want to restrain live changes until they are tested. One easy way to test the translations is to use the survey's email field and set it to a known value.

To test email translations:

• Make a Language preference with all the languages you want to test:

  • Set the Condition to e_email = 'test_user@medallia.com (choosing your email address).

• Create a Distribution setting with the same condition, with low Priority value.

• Create a record matching the Email field (e_email) value.

To test language preferences:

• Include the Email field (e_email) test in each preference's Condition, such as e_country in {'SE'} and e_email = 'test_user@medallia.com'.

• Mapping to Preferred language (e_contact_pref_language) overrides the contact preferences.