Verify items

👍

Data hub rollout

Data hub provides new unified API integration methods for sending data to multiple Bloomreach products. Access is being rolled out in phases. For new implementations, we recommend using Data hub where available. Existing product-specific integrations remain fully supported for Engagement, Discovery, and Clarity.

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).

Process

• Created an item collection. 

• Ingested data via full update via API or with Imports.

• Reviewed the records and defined the schema. 

Steps to verify product and variant items

Check that the system successfully transformed your records into structured items.

1. Go to Data hub > Items in your Bloomreach workspace. 

2. Locate and open the existing item collection from the item collections listing page.

3. Click the Products tab.

4. Review the list of product items showing unique item IDs and attribute values.

5. Click the View button next to any item to view its attributes (such as title, price, and color_family).

   

6. For variant items, check the variants list to confirm the variant attributes.

Items reflect the structured data after your schema mapping. They differ from records, which are raw and less structured before schema mapping. 

📘

Note

Only items, not records, are synced to Bloomreach products. Items are built directly from schema definitions and show their linked records.

Troubleshoot missing item attributes

If you expect an attribute, but it's missing from items:

1. Check the schema configuration to confirm you mapped the field correctly.

2. Verify the field exists in your records.

3. Check the jobs tab to see if schema reprocessing completed successfully.

4. Re-save the schema if needed to trigger a new item update job.

Troubleshoot missing items

Missing items are often linked to identifier configuration. 

• If a record identifier is used, a corresponding record with that identifier must exist when items are updated. 

• If a record field value is used, the item identifier should be present in that field within one of the records.

Next step

Create destinations and sync data.