Multi-language Support

Dynamic Yield supports multi-language sites by allowing you to:

• Fire events in various currencies on the same site
• Localize variations based on language/country
• Localize recommended products based on language/country

Currency support in events

If your visitors can make purchases using more than one currency, add a currency property to your events (purchase, add to cart, or any event with monetary value). Dynamic Yield converts the amount to the currency that is used in your Dynamic Yield reports.

DY.API("event", {
  name: "Purchase",
  properties: {
    uniqueTransactionId: "123456",
    dyType: "purchase-v1",
    value: 90.55,
    currency: "EUR",
    cart: [{
        productId: "item-34454",
        quantity: 1,
        itemPrice: 65.87
      }
    ]
  }
});

Supported currencies

Dynamic Yield currently supports the following currencies. If you require a currency that is not on this list, speak to your Customer Success Manager.

Note: The exchange rate uses the external service currencylayer and updates once every day at 4 am (UTC). If you require a real-time conversion, you must do the conversion on your end, and fire events using the site's default currency.

Localizing content

You can serve different content to users depending on the user's locale. This is currently available only for API, dynamic content emails, and site personalization campaigns that are not based on a variation feed.

Add language context on every page

If your site supports multiple languages (or versions of the same language in multiple countries), add a locale (lng) parameter to the page context of every page on your site. For example:

DY.recommendationContext = {type: 'HOMEPAGE', lng: 'en_GB'};

Add language context for email

To support multiple languages in Experience Email, see the Configure ESP parameters section in the main Experience Email article.

Supported languages codes

Localizing variations

Site personalization

For campaigns created using either the script-based implementation or API, you can serve a localized version of variations to your site visitors, as follows:

1. Make sure the page context is properly defined as detailed in the previous section.
2. Define your site languages.
3. Define localized values for individual variables in each variation.
   
4. For API campaigns, send the user's locale in the request under the page context (for example, "locale":"fr.*"). Make sure to reference the correct language codes.

Experience Email 

For email campaigns, you can serve a localized version of variations to your email users, at open time, as follows:

1. Define your languages
2. Configure the locale ESP parameter . Use a merge tag that will insert the locale value.
3. Define localized values for individual variables in each variation.

Manage your site languages

1. Go to General Setting › Manage Languages.
2. Click Add Languages and select the relevant languages your site supports.
   • Choose a language (for example, en, es) if you want to localize content per language, regardless of the country.
   • Choose a language and country combination (en_US, es_MX) if you want to localize content for languages in a specific country.
3. The order defines how they will be displayed in variations and templates. Drag and drop languages to adjust the order. You can delete a language by clicking the X next to it.
   
   

Localize variation content

When creating a new template or variation, you will see different language tabs under the Variable tab. These are the languages you chose in the Manage Languages section.

The first tab contains your default values. To localize variables to a different language:

1. Switch to the desired language.
2. Check the variable you want to localize.
3. Enter the localized variable value.

A variation that's served on a page that has this language in its page context, or in an email for which the locale code is received through the ESP merge tag, displays localized content for the selected variables, and the default content for all other variables.

If a variable is checked for a given language but left empty, we will render the empty text.

To see what the variation will look like to the user:

• On your site: Click Preview on Site. The variation is displayed based on the page context defined for that page.
• In an email: See the Preview your email section of the Experience Email article. The variation is displayed based on the ESP locale parameter.

Localizing recommended products

You can adapt your product recommendation campaigns based on the user locale in several ways.

Display localized product properties 

The first way to adapt campaigns to various user locations is to use localized product properties. For example, using different product names for different languages.

To add localized values of any product property (such as price, name, or description), add a column to your Product Feed with the following format

“lng:<language code>:<column name>”: “<value>”

For example, if your default language is English and you want to add a German version of the product name, add a column called "lng:de_DE:name", and set the German value for the name as follows:

"name":"White Pants" 
"lng:de_DE:name":"weiße Hosen"

The language code should match the name you use in the page context. For details, see Page Context. The language code can have up to two (_) or (-) between the values. For example: "lng:en_EN_X".

Because these columns are optional, blank values do not trigger errors or warnings.

You can create a total of up to 300 columns when working with multiple languages (including all mandatory, custom, and translated columns). 

For translations of attributes that have multiple values (such as parent and child categories), the order of the values should match the language order. For LTR languages, the values should be LTR, and for RTL languages the values should be RTL.

Filter products based on user locale 

This feature is available for Experience Email, site personalization campaigns, and API recommendations.

If you have different feed values for each locale, you can create a rule to exclude or include (not pin) products and filter products in the campaign based on the user's location. For example, you can choose to include only items that are in sale their area.

For example, if the feed has the following columns:

sku	discounted	lng:FR:discounted
123	Yes	No
234	No	Yes

You can create a rule that includes only discounted products, but filters out 123 for users with FR locale, and filters out 234 for the rest of the users.

When you create the filter rule, after you choose the property (in this case, "discounted"), choose "By the user's locale":