Migrate from Bloomreach
Review the steps necessary to migrate from Bloomreach to Constructor
In todayās digital landscape, providing a seamless and personalized shopping experience is crucial for ecommerce success. If you are planning to migrate from Bloomreach to Constructor, you are taking a significant step toward optimizing your websiteās search and discovery functionalities.
Whether youāre a developer, a project manager, or an eCommerce strategist, this guide aims to equip you with the information necessary to ensure a smooth transition.
Step 1: Send Constructor your product catalog
Youāve already built a catalog integration with Bloomreach, so thereās no need to do it again with Constructor.
With Constructor's Bloomreach adaptor, all default product catalog fields are already mapped. You simply need to send the file youād send to Bloomreach to the Omni Connector via SFTP, and the adaptor will transform that data into the format Constructor ingests.
You can send your Bloomreach file at your preferred frequency to keep Constructor up-to-date with new products and updates.
Data mapping
The base data from a Bloomreach product will always be transformed to an item at Constructor, defining the base product:
| Constructor Entity | Constructor Field | Bloomreach Field |
|---|---|---|
items | id | values.attributes.id |
items | active | true |
items | item_name | values.attributes.title |
items | image_url | values.attributes.thumb_image |
items | url | values.attributes.url |
items | description | not mapped |
items | keywords | not mapped |
items | group_ids | inferred from mapped item groups |
items | metadata | see metadata |
Then, every single item variant will be transformed into a Constructor variation:
| Constructor Entity | Constructor Field | Bloomreach Field |
|---|---|---|
variations | variation_id | values.attributes.id |
variations | item_id | mapped from parent item id |
variations | item_name | value.attributes.title |
variations | active | true |
variations | image_url | value.attributes.thumb_image |
variations | url | value.attributes.url |
variations | metadata | see metadata |
Bloomreach category data will map to Constructor item_groups:
| Constructor Entity | Constructor Field | Bloomreach Field |
|---|---|---|
item_groups | id | value.attributes.category_paths.id |
item_groups | name | value.attributes.category_paths.name |
item_groups | parent_id | inferred from the past group in file |
Step 2: Configure your metadata
Constructor's Bloomreach adaptor handles mapping default catalog fields but does not map any specific attributes by default.
Instead, Constructor provides a powerful template ecosystem via the Connect CLI that allows you to map your catalog data to ingest those attributes as metadata. Examples of popular metadata include color, price, brand, and availability.
By mapping these fields, you make the information available to Constructor and your end users. For example, you can configure attributes as facets, allowing shoppers to filter search and browse results by the attribute
Step 3: Install Constructorās beacon
Constructorās beacon collects anonymous data generated by your users' behavioral activity and history. Constructorās algorithms use this data to continually improve results, optimize impact, and increase your critical KPIs.
You will need to load the Constructor beacon directly on your website. You can review instructions for how to do so here.
Step 4: Display results
You have a few options for configuring how results retrieved from Constructor will display on your website.
- Integration approaches. Constructor offers both frontend and backend integration approaches that utilize Constructor's API.
- Client libraries. Constructor offers client libraries, or SDKs, aimed at being wrappers around Constructor's API to ease the integration process drastically.
- UI libraries. Constructor offers modern UI libraries aimed at drastically easing the process of rendering results within the view layer (browser).
Updated 22 days ago