Event streams

👍

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.

Summary

Event streams are a forwarding system for passing customer behavior (such as customer IDs, attributes, and events) through to be processed.

To learn more about importing historical data to Engagement, read here: Historical Imports

The normal workflow is for organic traffic (it's not meant to upload historical data in high volumes, where imports should be used instead). Since there is no storage, any data without a connected destination is discarded.

Function

For the normal workflow, you connect your source (website tracking, server-side tracking) to a destination (Bloomreach Engagement and/or Discovery). Once connected, new data will be incoming. If you connect Engagement then all your customer data can be stored there, which impacts Monthly Unique Visitors (MUVs), Monthly Processed Events (MPE), and Maximum Event Storage (MES) allowances.

To learn more about website tracking, read more here: Web tracking - Javascript

To learn more about optimizing your monthly MPE/MES, read more here: Efficient Engagement usage

Usage

The normal workflow includes:

• Bloomreach provisions a Data hub workspace, and Engagement project or Discovery account
• Log in and, in the Data hub app, create an Event stream
• An Event stream represents one data source (usually one website)

The most common integration pattern includes:

• If you have one brand in one locale (this approach offers ease of simplicity):
  • Create one Event stream, and connect it with the Engagement project destination and/or the Discovery account (depending on which was provisioned)
• If you have your website localized and want your data to be separated into locale-specific Engagement projects (this approach offers control of configuration):
  • Create one Event stream per website locale (it is recommended to include the locale in the name of the event stream)
  • Connect each Event stream to a certain locale-specific Engagement project
  • Connect all Event streams to your Discovery account, which is ready to receive multi-locale data (Discovery multi-site integration pattern)

Roles and permissions

Event streams admin

An Event streams admin is a user who possesses comprehensive permissions to create, configure, and manage Event streams within their assigned Workspace. This role allows for full control over the lifecycle and setup of Event streams.

Specific permissions for an Event streams admin would include the ability to:

• Create new Event streams
• Edit the configuration of existing Event streams, such as changing the name
• View the details and credentials of an Event stream, including the Stream ID and API endpoint
• View the list of destinations to which an Event stream is connected
• Connect Event streams to destinations, such as a Bloomreach Engagement project or a Bloomreach Discovery account
• Disconnect Event streams from destinations
• Delete Event streams

Event streams viewer

An Event streams viewer is a user who has read-only access to Event streams within their assigned Workspace. This role allows users to observe the setup and configuration of Event streams and the flow of data without being able to make any modifications.

Specific permissions for an Event streams viewer:

• List all Event streams within the Workspace
• View the configuration and details of existing Event streams, including the name, and credentials
• View the list of destinations to which an Event stream is connected