Storefront associations

A Storefront association is a configuration that connects your catalog entities with specific tracking IDs and locale in the Coveo Platform. This connection allows the platform to automatically identify the appropriate catalog ID for queries and enrich usage analytics events with product metadata. This means there’s no need to specify the catalog ID when making queries or logging analytics events, as the platform resolves the appropriate catalog entity for both content retrieval and event enrichment.

Consequently, you no longer need to generate API keys through the Catalogs (platform-ca | platform-eu | platform-au) page, which would enforce the catalog ID value in the API keys. A single search token or API key can be used across many catalog entities.

The Storefront associations (platform-ca | platform-eu | platform-au) panel lets you associate catalog entities with the target tracking ID and locale. For an example on how to storefronts are typically represented in Coveo for Commerce, refer to the Coveo for commerce setup guide.

By making these associations through the event protocol, the platform enriches event data with key metadata from the Coveo catalog, such as ec_category, ec_brand, and ec_item_group_id. This reduces the amount of data you need to send, as the platform supplements it automatically behind the scenes. This enriched data also improves the contextual accuracy of event tracking by providing more detailed and relevant information for logged commerce events.

Once you’ve set up the necessary storefront associations, you can use a single search token or API key that grants the Allowed access level on the Execute Queries domain and the Push access level on the Analytics Data domain in the target organization.