Integrations / Customer Data Platform
Bloomreach
Server-side event tracking into a Bloomreach Data Hub event stream, which fans events out to the connected Bloomreach products (Marketing/Engagement, Search).
Datafly Signal delivers first-party events to Bloomreach server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Bloomreach expects.
Why route Bloomreach through Datafly Signal
Profiles update from the server, not the browser
Events reach Bloomreach even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
Client IP and user agent are preserved
Server-to-server delivery normally loses both, which weakens matching. Signal forwards the genuine visitor values as request headers so Bloomreach attributes the event to the right session.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the Bloomreach rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
Bloomreach is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
add_to_cartconsentidentifypagepurchaseremove_from_cartsearchview_itemview_item_listview_search_resultsVertical presets
Retail, General (all verticals). Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the Bloomreach documentation.
Frequently asked questions
Does Datafly Signal integrate with Bloomreach?
Yes. Datafly Signal delivers first-party events to Bloomreach server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Bloomreach expects. The integration is included in every deployment at no additional cost.
How is server-side Bloomreach tracking different from the Bloomreach tag?
The Bloomreach tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to Bloomreach from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Bloomreach?
The blueprint ships with mappings for add_to_cart, consent, identify, page, purchase, remove_from_cart, search, view_item, and more. Any event in your schema can be mapped to Bloomreach through pipeline configuration without a code change.
Do I need to keep the Bloomreach tag on my site?
No. Signal delivers to Bloomreach from the server, so no client-side Bloomreach script is required on your site.
Ready to move Bloomreach server-side?
See how Datafly Signal delivers first-party events to Bloomreach from infrastructure you control, with hashed identity and consent enforcement built in.