Skip to main content

​
Markets

A market typically refers to a specific geographical region. Markets are characterized by product assortment, user behavior, and merchandising support:
  • Each market has its own set of products.
  • User behavior within a market is collected and analyzed to understand trends, power recommendations, and support reporting.
  • Merchandising actions such as boosts and page rules are configured independently per market.
An Elevate market is correctly defined if all of the following are true:
  • Do products have the same variants available market-wide?
  • Do all site visitors expect the same online availability for all items?
  • Should trends and popularity be based on all site visitors’ behavior together?
  • Should merchandising actions apply uniformly across all users?

​
Assortment requirements

Products within a market must be fundamentally the same across the market. This means products cannot have differences in their structure or availability for different site users. Specifically:
  • Each product must have the same variants for all site users.
  • Variants must have the same online availability for all site users.
  • All variants within a product must have the same set of price types, ensuring consistent pricing.

​
Market support

While a market defines a shared product structure, availability, and primarily aggregated behavioral data, it supports a range of assortment- and behavior-level variations, including:
  • Content localized for multiple locales
  • Store-specific availability for physical store stock
  • Multiple currencies and price types specified at request time
  • Personalization and audience-based promotions within the market context

​
Market identifiers

Each market is identified by a unique market identifier, which is required for nearly all types of requests. Product data, content, and behavioral statistics are all linked to one or more markets.
  • Market identifiers must be consistent across all integration points.
  • Market identifiers are case-sensitive.
  • All product data and content keys belonging to a market must be unique.
  • All product data and content keys must be consistent across all markets. For example, a product with the same key on different markets is assumed to be the same product for all intents and purposes.

​
Locales

A locale is a language and country combination that enables correct handling and analysis of text content. Each market supports one or more locales. Locales are used to:
  • Analyze and process text content correctly for search and recommendations
  • Improve classification by providing language context
  • Support multilingual content within a single market

​
Supported locales

The following locales are currently supported: bg-BG, cs-CZ, da-DK, de-AT, de-CH, de-DE, el-GR, en-001, en-150, en-AU, en-CA, en-GB, en-HK, en-IE, en-IN, en-MO, en-MY, en-PH, en-SG, en-TW, en-US, es-ES, es-MX, et-EE, fi-FI, fr-BE, fr-CA, fr-CH, fr-FR, fr-LU, fr-MC, he-IL, hr-HR, hu-HU, it-CH, it-IT, ja-JP, ko-KR, lt-LT, lv-LV, nb-NO, nl-BE, nl-NL, nn-NO, no-NO, pl-PL, pt-BR, pt-PT, ro-RO, ru-RU, sk-SK, sr-RS, sv-FI, sv-SE, tr-TR, uk-UA, vi-VN, zh-CN, zh-HK, zh-MO, zh-TW Locale support is extensible, allowing additional locales to be supported over time.
Last modified on September 3, 2026