Bloomreach CDP

Commerce-focused customer data and experience platform combining real-time customer data, AI-driven personalisation, and marketing automation.

Prerequisites

Complete these steps in Bloomreach Engagement before configuring Signal.

Access your Bloomreach Engagement account

Log in to Bloomreach Engagement at app.bloomreach.com. If you do not have an account, contact your Bloomreach representative.

Find your Project Token

Navigate to Project Settings > Access Management > API. Your Project Token is displayed at the top of the page. This uniquely identifies your Bloomreach project.

Create API credentials

On the same Access Management > API page, locate or create an API key pair. You need both the API Key (public) and API Secret (private). Click Create New API Key if one does not exist. Ensure the key has permissions for server-side event tracking and customer data.

Determine your API base URL

The base URL depends on your Bloomreach deployment region:

Region	Base URL
US	`https://api.exponea.com`
EU1	`https://api-eu1.exponea.com`
EU2	`https://api-eu2.exponea.com`

Check your dashboard URL to determine which region your project is hosted in, or ask your Bloomreach account manager.

Configuration

Field	Type	Required	Description
`project_token`	string	Yes	Your Bloomreach Engagement project token. Found in Project Settings > Access Management > API.
`api_key`	secret	Yes	Your Bloomreach public API key for server-side event tracking.
`api_secret`	secret	Yes	Your Bloomreach private API secret, paired with the API key for authentication.
`api_base_url`	string	Yes	The Bloomreach API base URL for your region (e.g. `api.exponea.com`).

Signal Setup

Quick Setup

Navigate to Integrations in the sidebar.
Open the Integration Library tab.
Find Bloomreach CDP or filter by CDP.
Click Install, and fill in the required fields with the credentials gathered above.
Click Install Integration to create the integration with a ready-to-use default configuration.

API Setup

curl -X POST http://localhost:8084/v1/admin/integration-catalog/bloomreach_cdp/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Bloomreach CDP",
    "variant": "default",
    "config": {
      "project_token": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
      "api_key": "xxxxxxxxxxxxxxxxxxxx",
      "api_secret": "xxxxxxxxxxxxxxxxxxxx",
      "api_base_url": "https://api.exponea.com"
    },
    "delivery_mode": "server_side"
  }'

Event Mapping

Signal events are mapped to Bloomreach Engagement API calls as follows:

Signal Event	Bloomreach Concept	Notes
`page`	`page_visit` event	URL, title, and referrer sent as event properties
`track`	Custom event	Event name and properties forwarded as Bloomreach custom events
`identify`	Customer update	Traits merged into the customer profile via the `customer_ids` mapping
`track` (purchase)	`purchase` event	Order and product data sent as structured purchase events for revenue tracking

Bloomreach uses a registered customer ID by default. Ensure your events include a consistent user identifier (email or customer ID) for profile unification.

Delivery

Events are delivered server-side from your Datafly Signal infrastructure directly to the Bloomreach Engagement API. No client-side scripts are loaded for this integration.

Testing

After installing the integration, trigger a test event from your website or via the Signal event API.
In Bloomreach Engagement, navigate to Data & Assets > Events and search for recent events to verify delivery.
Search for the test customer in Customers to verify profile data was created or updated.
In Signal, check the Live Events view to confirm the event was delivered with a 200 response status.

Troubleshooting

Symptom	Possible Cause	Resolution
`401 Unauthorized`	Invalid API key or secret	Verify the API key and secret in Bloomreach Project Settings > Access Management > API
`404 Not Found`	Incorrect project token	Verify the project token in Bloomreach Project Settings
`400 Bad Request`	Malformed event data	Check that event properties match Bloomreach’s expected format. Review the API error response for details
Wrong API base URL	Region mismatch	Ensure the `api_base_url` matches your Bloomreach deployment region
Events delivered but customer not created	Missing customer ID	Include a `registered` or `cookie` customer ID in events for Bloomreach to create a customer profile

Visit Bloomreach documentation for full API reference and event tracking details.

Attentive Blueshift