What is Bloomreach?

Bloomreach CDP (Customer Data Platform), part of the Bloomreach Engagement suite, enables marketers to unify, segment, and activate customer data across digital channels. It offers advanced capabilities for personalization, experimentation, and campaign automation by combining real-time behavioral tracking with user profile enrichment. With Bloomreach CDP, businesses can create dynamic audiences, orchestrate customer journeys, and deliver targeted experiences based on unified first-party data.

Product Type: Customer Data Platform

Integration Type: Starter Kit & ID Sync

Capabilities

Drops the Bloomreach CDP tag when loadTagFromSync is enabled to initialize real-time tracking and personalization.
Sets Bloomreach cookies for session management and experimentation.
Supports re-firing the tag on identity updates for continuous user resolution.
Enriches server-side events with firing metadata for tracking and diagnostics.

Considerations

The Bloomreach tag must be loaded via MetaRouter or manually before the MetaRouter tag, depending on the loadTagFromSync setting.

Sync Details

IDs:
- This sync does not capture or return any new user identifiers; however, it calls exponea.identify() using MetaRouter’s anonymousId, under the Identify Key you configure.
Description:
- The sync injects the Bloomreach CDP tag if loadTagFromSync is enabled.
- It sets cookies (__exponea_etc__, __exponea_time2__) to manage sessions and enable experiments.
- MetaRouter stores _bloomreach_fired in storage to indicate when the tag was activated.
- The tag re-fires automatically on identity calls if Fire On ReSync is true.
- Event payloads are enriched with firing status and any errors encountered.
Server-side Event Payload:
Upon completion of all vendor's sync, the server-side events will incorporate all resolved identifiers as described above. The following object will be appended to the context.providers property within the event's JSON payload.
```
json
CopyEdit
{
  "bloomreach": {
    "fired": "date string when the tag was fired",
    "error": "Failed to load tag, if for some reason the tag methods returned an error"
  }
}
```
Cookie Name:
- Cookie: _meta_bloomreach_fired
- IndexedDB: [your storage prefix]_bloomreach_fired
- For a general guide on ID Sync validation, see here.

Sync Setup Guide

1. Gather Credentials

To configure the Bloomreach sync, retrieve the following from your Bloomreach Engagement (CDP) configuration:

Target – Your Bloomreach API endpoint (e.g., https://api-demoapp.exponea.com)
Token – The API token assigned to your project (e.g., a08f8344-0dac-11ed-836c-9e9a9b852d9a)

Contact Bloomreach support if these credentials are not available.

2. Add a Bloomreach Sync in MetaRouter

To trigger the Bloomreach CDP tag and enable real-time data collection, you must add a Bloomreach sync.

From the Pipelines page, find the pipeline associated with the web property you’d like to add a sync to. Hover over the three dot dropdown and select “Build AJS File.”
In the Identity Syncs section, select the Bloomreach sync.
Fill out the following fields:
- Token – Your Bloomreach API token (e.g., a08f8344-0dac-11ed-836c-9e9a9b852d9a)
- Target – Your Bloomreach endpoint (e.g., https://api-demoapp.exponea.com)
- Identify Key – Bloomreach’s customer attribute key used in exponea.identify() where MetaRouter will set the anonymousId (e.g., cookie_metarouter)
- Load Bloomreach tag from MetaRouter script – Toggle ON to load the Bloomreach JS snippet via MetaRouter
- Track Sessions – Toggle ON/OFF to enable or disable initial session tracking
- Enable Experiments (sync) – Toggle ON/OFF to control experiment enablement from the sync
- Fire on Re-Sync – Toggle ON to re-fire the tag on subsequent identity events
Scroll down and click the Save and Build File button.
Deploy your AJS file to propagate changes to your web property.