commercetools FAQ

This FAQ addresses common technical questions about implementing and configuring the commercetools-Bloomreach integration.

Data mapping

Where is the mapping for products defined?

commercetools product data is pulled and exposed in service/src/services/commercetools-catalog-ingestion.ts. The exposed data is then mapped into Bloomreach in service/src/services/bloomreach-engagement-product-import.ts.

Where is the mapping for product variants defined?

commercetools product data is pulled and exposed in service/src/services/commercetools-catalog-variants-ingestion.ts. The exposed data is then mapped into Bloomreach in service/src/services/bloomreach-engagement-product-import.ts.

Where is the mapping for customers defined?

commercetools customer data is pulled and exposed in service/src/services/commercetools-customer-ingestion.ts. The exposed data is then mapped into Bloomreach in service/src/services/bloomreach-engagement-customer-import.ts.

Where is the mapping for orders defined?

commercetools order data is mapped into Bloomreach in event/src/controllers/event.controller.ts.

Configuration

What is the BASIC_AUTH_SECRET environment variable for?

Bloomreach consumes customer and product data from an endpoint exposed by the connector. This endpoint is secured using basic HTTP authentication, where the username is the CTP_PROJECT_KEY and the password is the BASIC_AUTH_SECRET.

Why is the environment variable needed?

commercetools has built-in i18n support by default. BLOOMREACH_ENGAGEMENT_CATALOG_LOCALE specifies the desired LocalizedString to consume the catalog data.

Customization

How can I modify the import job settings in Bloomreach?

Review the services under service/src/services to modify settings like frequency, time of day, and other configuration options.