← Back to Knowledge Base
Affect Performance Team
|News|Nov 17, 2026

Bloomreach Engagement Adds Separate Consent for Email Opens and Clicks

Bloomreach Engagement now lets marketers request separate consent for email open and click tracking. On October 27, 2026, Bloomreach published release notes for Engagement 1.321, rolled out from October 28 through November 2. The main change for email marketers is more granular tracking consent: campaigns can require consent for recording opens, clicks, or both separately. This makes it possible to measure clicks from recipients who did not consent to open tracking. The feature is disabled by default and must be enabled through a Customer Success Manager. The same release also made general catalogs created from custom item types in Data hub available to catalog triggers.

Previously, an email campaign or email node in a journey used a single tracking consent category for both opens and clicks. Now each email campaign and email node can specify two categories. The open tracking category determines what a recipient must consent to before Bloomreach inserts an open-tracking pixel. The click tracking category determines what consent is required before Bloomreach records link clicks.

When recipients can consent to one type of tracking but decline the other, marketers can choose different categories for opens and clicks. If one consent covers both activities, they can use the same category for both. Leaving a field blank allows the corresponding event to be tracked as usual. Existing consent-category settings continue to require consent for both opens and clicks, so no action is required for those configurations.

Bloomreach explains the change in terms of regulatory requirements. According to its documentation, in several EU countries, including France, Germany, and Italy, tracking pixels and tracked email links may be treated as access to a recipient's device and require prior consent unless an exception applies. Bloomreach emphasizes that its documentation is informational and recommends seeking legal advice for the specific circumstances of a business.

Transactional Email API Settings and Event Data

For transactional email, the Transactional Email API settings object supports tracking_consent_categories, with separate open and click categories. The previous consent_category_tracking parameter remains supported and applies a single category to both activities. Bloomreach recommends migrating to the new parameter and avoiding sending both parameters at once. The opened and clicked events retain the consent_category_tracking attribute, which records the category used for that event.

Tracking consent is not limited to email. Once enabled, the wider functionality also applies to in-app messages and journey nodes for browser push, email, mobile push, MMS, and SMS. Separate open and click categories specifically apply to email campaigns and transactional emails: opened is governed by the open category, and clicked by the click category.

Forced Click Tracking and Reporting Impact

If a click must be recorded before consent is obtained, for example during double opt-in, Bloomreach offers the xnpe_force_track parameter. Adding it to a specific link bypasses consent for that link and adds a tracking_forced attribute to the clicked event. The parameter name must be lowercase. A value of true or 1, or including the parameter without a value, enables it. Bloomreach advises using this only as an exception. To measure clicks from a broader group of recipients, marketers should adjust the campaign's or email node's click consent category instead.

Enabling tracking consent affects reported metrics. In campaigns that require consent for opens, the reported open rate decreases. Clicks continue to be tracked as before unless click consent is also required. The documentation warns that open rate and click-through rate in the email evaluation dashboard can be affected, and suggests working with a Customer Success Manager on a custom dashboard that accounts for prior explicit tracking consent.

Availability and Limitations

Tracking consent is disabled by default. To activate it for a project, the customer must contact a Customer Success Manager. Prior explicit consent must be collected before tracking is enabled. Bloomreach suggests using a standard consent-collection journey configured with the Customer Success Manager and informing recipients in advance about the use of tracking pixels and tracked links, as some regulators require prior notice.

There is an important limitation: Bloomreach checks consent when the email is sent. If the recipient withdraws consent after delivery, subsequent opens and clicks on that email may still be recorded. The documentation recommends not using this information for profiling or targeting. Bloomreach plans to stop tracking already-sent emails after consent withdrawal in a future release.

Custom Item Type Catalogs Become Available to Catalog Triggers

A second update in release 1.321 concerns Data hub. Custom item types let businesses store non-product records, such as articles, store locations, or accommodation listings, in item collections alongside product data. When connected to a Marketing destination, a custom item type is published as a general catalog that syncs when the underlying data changes. These catalogs can now be used in catalog triggers.

All six trigger types are available for general catalogs built from custom item types: back in stock, price reduction, low inventory, new arrival, item date, and custom. Each trigger still needs appropriate catalog attributes and audience-matching rules, because a general catalog does not automatically include product attributes such as price or inventory. Bloomreach gives two examples: a publisher can notify interested readers about new articles with a new-arrival trigger, while a subscription business can remind a customer of an approaching booking date using an item-date trigger.

Custom item types do not support variants or Search destinations; those capabilities remain available for product item types. Existing general catalogs are unaffected by the release, but an existing catalog cannot be converted into a custom item type. Businesses must import or send their data through the API into a custom item type and connect it to a Marketing destination. Data hub then creates a new catalog while the old one remains unchanged, so campaigns and catalog triggers referring to the old catalog must be updated.

Release 1.321 also includes unrelated updates: Data hub contexts for information such as stores, regions, and price lists; dynamic file lookup using filename patterns during Data hub imports; and React Native SDK version 4.2.1. The release notes provide further details.

About Bloomreach

Bloomreach describes Engagement, referred to as Marketing in its documentation, as an AI-powered platform for personalized commerce experiences across channels. Its customer data platform stores and analyzes customer information and uses it for website and campaign personalization. A unified customer profile supports audience segmentation and marketing automation.

The product combines marketing automation with a built-in CDP. It supports email, mobile and push messaging, website personalization, and customer data management. Bloomreach positions it for commerce businesses seeking personalized customer experiences. Its documentation also has separate sections for Search, Content, Data hub, and Conversational agent.

Trust Us Transform Your Performance Marketing.

Improve customer data activation, campaign analytics, and cross-channel marketing performance with Affect Group.

Explore Affect Group Services

Sources