SDK usage and limitations

👍

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.

Before implementing the Unified tracking JS SDK, review these considerations to ensure proper setup and avoid common issues.

Installation and compatibility

Install only one Unified tracking JS SDK snippet per page. Multiple running instances aren't supported.

You can't run both the Engagement JS SDK and Unified tracking JS SDK at the same time. Switch from one to the other. Running both simultaneously causes unexpected cookie collisions. This leads to loss of visitor identification and tracking data.

Data schema and event tracking

Pay close attention to the data schema provided by Bloomreach or your integration partner. Events and event properties shared between Engagement and Discovery must follow the prescribed schema. Events that don't follow this schema can't be shared with Discovery.

You can always track any data to Engagement. However, only events following the prescribed schema will be shared with Discovery. Custom events for Engagement are allowed but won't be forwarded to Discovery. The full list of event names and properties depends on your selected use cases and data requirements.

Engagement and Discovery currently use different visitor IDs (cookies). The tracker uses two distinct cookie values. After you connect a new destination, visitors aren't immediately recognized as returning visitors by that destination app.

Performance and browser support

If script size affects your website performance, consider these sizes: the JS snippet is 3KB while the JS SDK is approximately 170KB (60KB transferred size). This could potentially impact loading speed.

Browser support is limited to the latest two versions of Chrome, Mozilla Firefox, and Safari, and the latest version of Opera. Users on older browser versions may experience limited functionality.

Privacy and security

Don't run Bloomreach scripts on pages containing sensitive information like credit card or payment details. For sensitive data such as costs and margins, use server-side tracking instead of the JS SDK.

Other considerations

• When implementing Discovery SEO, you may need to install additional standalone Discovery trackers. Consult your Bloomreach representative for help.
• Imports for customer properties and events are out of scope for the Data hub solution. These will continue to be handled separately within Engagement. This may be a limitation if you expect unified data import capabilities.
• Actual cookie retention may vary depending on the visitor's browser cookie policy. This happens even if the SDK sets a maximum expiration.
• Web personalization works the same way as with the existing Engagement JS SDK. Other limitations of Engagement JS SDK also apply.