You are here:
Using Localization for Personalization
Deliver language-consistent recommendations to global audiences by using automatic attribute fallbacks and translation schemas.
Maintain a single source of truth across your global data spaces by localizing only the fields that require translation. This approach ensures that non-localizable data in your Root Data Model Object (DMO), like pricing or SKUs, remains consistent while the system dynamically serves translated content where it matters most.
Key Considerations
When setting up localization, keep these considerations in mind:
- Global Control: You can enable or disable localization at any time across all data spaces to manage feature rollout.
- Locale Matching: Personalization uses the locale field you select during item definition to match requests to your customer’s preferred language.
- Reliable Fallbacks: To prevent gaps in the user experience, the system automatically uses customer profile data or item defaults if a specific locale isn't provided.
Localization Benefits
Review the benefits of using localization to maintain a single source of truth across your global data.
| Benefit | Description |
|---|---|
| Ensure Language Consistency | Prevent mixed-language experiences, such as a Spanish title with English body text, by using precise translation schemas. |
| Simplify Data Management | Save time by automatically pulling non-localizable data, such as prices or SKUs, directly from the Root DMO. |
| Respect Localization Intent | Maintain more granular control by ensuring that intentionally blank fields do not trigger an accidental fallback. |
Localization Fallback Logic
To ensure a consistent user experience, Personalization evaluates locale data in two stages: first by determining the overall locale, and then by evaluating specific attribute data within the DMO.
Hierarchy for Determining the Locale
If a decision request doesn't specify a locale, the system follows this order to select the language:
- Profile Attribute: The system uses the locale value from the customer’s profile data graph.
- Default Value: If no profile value is found, the system uses the default value from the recommended DMO item.
Field-Level Fallback Actions
Review these system actions and results to understand field-level fallback behavior:
| Attribute Status | System Action | Result |
|---|---|---|
| Absent from the schema | Returns the value from the default locale in the Root DMO. | The field populates with default data, such as a global inventory count or a default image. |
| Defined but left blank | Treats the blank as an intentional choice. | The field remains blank. No fallback occurs to ensure your intentional formatting is preserved. |
