Configure schema
Welcome note
Data hub is our new upgraded platform, which we rolled out in August 2025. It offers a single unified integration for passing your data through to your Bloomreach products.
You have access to Data hub if you've implemented with Bloomreach after August 2025.
Customers who have implemented before August 2025 should follow the existing documentation for Engagement, Discovery, and Clarity.
Map your raw record fields to meaningful attributes so the system can create items from them.
Prerequisites
Knowledge
- Understanding of item collection concepts.
- Understanding of which record fields should map to product-level vs. variant-level attributes.
- Knowledge of appropriate data types for your attributes (string, number, boolean, array).
- Knowledge of schema mapping.
Process
-
Created an item collection.
-
Ingested data via full update via API or with Imports.
-
Reviewed the records.
Steps to configure schema
The following steps apply to both product and variant attribute mappings.
-
Go to Data hub > Items in your Bloomreach workspace.
-
Locate and open the existing item collection from the item collections listing page.
-
Click the Schema tab.
-
Set the item identifier. This defaults to record ID, but you can choose a custom record field as item ID. When you choose the custom option:
-
Field name: Enter the name of your custom field.
-
Record level: Select which level (product or variant) of your data hierarchy contains this field.
-
Fallback behavior: Choose what happens when the specified field value is missing:
-
Fallback to record ID (default): Uses the record ID if your custom field is empty.
-
Skip updates for related item: Ignores records without the custom field value.
-
Stop job execution (job failure): Fails the job if any record is missing the field value.
-
-
-
Click + New attribute and select the attribute type.
System attributes
Select and map system attributes to source fields from your records (like title, price, url). Click Apply selection.
Custom attributes
Map custom attributes for any fields unique to your business (like color_family or custom_level). Select the source field, choose a data type, and save changes.
Custom attributes namespacing
When custom attributes have the same name as system attributes, they receive a namespace prefix to prevent collisions when they sync with destinations.
Example
Schema: Custom attribute named color
Engagement catalog: Appears as main.color
Discovery catalog: Appears as main.color
The main namespace ensures your custom color attribute doesn't conflict with any system color attribute. System attributes map directly without the namespace prefix.
- Click Save changes. Repeat the same process for variant attributes by clicking the Variant tab.
Data hub reprocesses your data to generate items based on the new mappings. Wait for the items update job to complete.
Next step
Updated 7 days ago
