Release 1.321

TL;DR: Release 1.321 introduces contexts in Data hub, so you can tailor product data to every store, region, or price list, and custom item types for managing business data beyond products. You can now require tracking consent for email opens and clicks separately, and import files with changing names by matching a file name pattern.

Release date: 28.10. - 2.11.2026

Subscribe to release notes

Tailor product data to every store, region, or price list

We're excited to launch contexts in Data hub. With contexts, show each store, region, or business customer the right products, prices, and availability, all from one product item type.

What's new

Contexts for every store and customer: Tailor product data for each store, region, or price list in one product item type, so you manage one catalog instead of many copies.
Overrides for what's different: Change or add only the values that differ, such as a contract price or a pickup time, so shared data stays in one place and updates apply everywhere.
Right assortment in every context: Choose which products and variants are available for each store, so shoppers only see what they can buy.

Business use cases

Business-to-business (B2B) price lists: Show each business customer the products and contract prices they've agreed on.
Buy online, pick up in store: Show shoppers stock levels, pickup times, and promotions for the store they choose.
Location-based pricing: Adjust prices and availability for each region or market from one catalog.

Feature impact

Search: Each store or price list in a context syncs as a view in your Search multi-view catalog.
Marketing: Product and variant catalogs store context data, and you can view a catalog's items for each context value. Other Marketing features use your base product data.
Loomi for Shopify: Contexts aren't available for Loomi for Shopify.
Conversational agent: Contexts aren't available for Conversational agent.
Data imports: Imports don't support override data. Send it through the API.

Access

New integrations: Use contexts in Data hub. Your Search catalog must be set up for multi-view. To enable it, contact your Customer Success Manager (CSM).
Existing multi-view integrations: No changes needed, including when you add a catalog. To move an integration to Data hub, set up a product item type that matches your current catalog.

Marketing

Before you use contexts in Marketing, check with your Customer Success Manager (CSM) whether contexts suit your use case.

Learn more

Model business data with custom item types

We're excited to announce custom item types: a new way to manage business data such as articles, store locations, and hotel properties in a Data hub item collection, right alongside your product data.

What's new

Model data with item types: While product item types organize your ecommerce catalog with variants, custom item types manage other business data, such as hotel properties, articles, and locations.
Several item types in one collection: A single item collection can hold several product item types, several custom item types, or a mixture. For example, you can manage products, bundles, and articles in 1 collection, each with its own schema and destinations.
Add item types: Add new item types to an existing collection as you grow.
Connect to Marketing as a general catalog: Connect custom item types to a Marketing destination, and Data hub publishes it as a general catalog, keeping it in sync as your data changes.

Catalog triggers

Custom item types publish to Marketing as general catalogs, and those catalogs are now eligible for catalog triggers.

All 6 trigger types are available for general catalogs created from custom item types. Each trigger requires suitable catalog attributes and rules for identifying interested customers.

Business use cases

Publishing: Notify readers of new articles matching their interests with a "new arrival" trigger.
Subscriptions: Remind customers before a booking deadline with an Item date trigger.

Feature support

Custom item types don't support variants or a Search destination. Those stay specific to product item types.

Existing general catalogs

There's no impact on existing general catalogs. You can still create general catalogs directly in Marketing.

You can't convert an existing general catalog into a custom item type. To manage that data in Data hub, import it or send it through the API to a custom item type, and connect the item type to a Marketing destination. Data hub creates a new catalog. The existing catalog stays as it is, so update any campaigns and catalog triggers that use it.

Learn more

Track email clicks without open consent

Require tracking consent for email opens, clicks, or both, so recipients who decline open tracking still contribute click data.

What's new

Separate consent for opens and clicks: Bloomreach adds the open pixel only for recipients who consented to open tracking, and tracks clicks only for recipients who consented to click tracking.
Transactional Email API: Use the settings.tracking_consent_categories parameter with open and click.
Events: opened and clicked events keep the consent_category_tracking attribute, which records the category that applied.
Force click tracking: Add the xnpe_force_track parameter to specific links, such as double opt-in confirmations, to track clicks regardless of consent.

Business use cases

Track clicks for recipients who consented to click tracking but not open tracking
Configure tracking consent by purpose to support your privacy compliance
Force click tracking on specific links, such as double opt-in confirmations, with xnpe_force_track.

Feature impact

Open rates drop in campaigns that require open consent. Clicks are tracked as before unless the campaign also requires click consent.

Bloomreach checks tracking consent when it sends an email, so a withdrawal after sending doesn't stop opens and clicks on that email from being recorded. Stopping this is planned for a future release.

Migration

Existing tracking consent categories keep requiring consent for both opens and clicks.
settings.consent_category_tracking still works, and applies one category to both. Use tracking_consent_categories instead, and don't send both.

No action is needed for existing setups.

Access

Tracking consent is disabled by default. To enable it, contact your Customer Success Manager.

Learn more

Import files with changing names into Data hub

Data hub imports into item collections and catalogs can find files by pattern. If your system adds a date or timestamp to each file it exports, enter a regular expression instead of a fixed file name, and Data hub picks the right file on each run.

What's new

Dynamic file matching: Set File matching to Dynamic and enter a regular expression to match file names that change with each export.
Selection rules: When more than one file matches, choose Last modified to import the most recently modified file, or Last alphabetically to import the last one by name.
Selected file in preview: The data preview shows which file the import selected, so you can check your pattern before you save the import.
Supported sources: SFTP, Amazon S3, and Google Cloud Storage.

Business use cases

Daily product feeds: Import a catalog export named with the date, such as catalog_2026-10-14.csv, without changing how your system names files.
Migration to Data hub: Move file-based catalog imports from legacy catalogs to Data hub without reworking file names or upstream exports.
Price and stock updates: Keep item collections current from frequent exports whose file names include a timestamp.

Feature impact

Imports for customers, events, vouchers, and legacy catalogs are unchanged.
Data hub patterns don't use enclosing slashes and follow RE2 syntax. If you're moving a pattern from a legacy catalog import, check it before you reuse it.

Learn more

File name matching

Mobile SDK updates

Build your Android apps on the latest React Native versions with the React Native SDK version 4.2.1 release.