Catalog Localization ETL Data Feed

About Ingesting Catalog Localization Data

Personalization supports the localization of catalog items, which allows unique data for specific fields to be stored based on the language and country codes. The locale-specific data can then be leveraged on site (provided you are tracking users' locale information on your website using the sitemap) to display catalog object information with the locale-specific data for the catalog item.

The Catalog Object Locale ETL allows for the ingestion of locale-specific catalog object information for Articles, Blogs, and any user-created catalog object. Promotions do not support localized attributes. The Catalog Object Locale ETL should be used in conjunction with a Catalog Object ETL or another method of populating catalog object items in the catalog.

Ingestion Considerations

• The Catalog object localization setting on the Catalog and Profile Objects settings screen must be turned on for the Catalog Object Locale ETL to function.
• Only certain catalog object attributes support localized values (Name, Description, URL).
• Localization is not supported for custom attributes or related catalog objects.
• If an item is included in the Catalog Object Locale ETL, but does not exist in the Personalization catalog before ingesting the file, an item with the source ID will be created. However, that item will only have the data in locales which are included in the file. For example, if a dataset is in the default configuration (en_US) and a new item with only a locale of fr_FR is included, the item will only load data to the fr_FR locale – there will not be any data in the en_US locale.
• Multiple catalog object types can be included in a single file.
• Datasets have a default language in Personalization - this is configured in the Catalog Object Setup screen (see Catalog Objects). This information is considered the default locale of the catalog and should be updated by the standard Catalog Object ETL.

Requirements

• Each row requires a catalog object item ID and a locale in the format of "2-letter lower-cased language code", "underscore", "2-letter upper-cased country code". Examples: en_US, fr_FR, de_DE, en_AU, and so on.
• Each catalog object item should have a single locale per row of the file. Every locale instance of a catalog object item should appear consecutively in the file.
• The Catalog Object Locale ETL file needs to be sorted by catalog object type so that all catalog objects of the same type appear in consecutive rows. Sorting can be achieved by the client prior to loading the file into the system.
• Supported locales are visible in the platform via the locale drop-down on the Catalog and Profile Objects Settings screen (Settings > Catalog and Profile Objects).

Filename Format

locale-catalog-object-YYYY-MM-DD_HH-MM-SS.csv

Schema

Sample File