Integrations / Marketing Automation

Bluecore

Server-side delivery to the Bluecore Events API (POST /api/track/mobile/v1) for retail email/SMS personalisation. Maps GA4-style events to Bluecore's standard events (viewed_product, search, add_to_cart, purchase, optin, unsubscribe), with plaintext email identity (distinct_id + customer.email) and the products[] catalog array. Bluecore matches on the unhashed email, so PII is sent plaintext (not hashed).

Datafly Signal delivers first-party events to Bluecore server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Bluecore expects.

Why route Bluecore through Datafly Signal

Profiles update from the server, not the browser

Events reach Bluecore even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.

One consent decision governs every destination

Bluecore 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_cartadd_to_wishlistnewsletter_unsubscribedpagepurchaseremove_from_cartsearchsign_upview_item

Vertical presets

Retail. 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 Bluecore documentation.

Frequently asked questions

Does Datafly Signal integrate with Bluecore?

Yes. Datafly Signal delivers first-party events to Bluecore server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Bluecore expects. The integration is included in every deployment at no additional cost.

How is server-side Bluecore tracking different from the Bluecore tag?

The Bluecore 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 Bluecore from your server, so delivery does not depend on browser conditions.

Which events can Signal send to Bluecore?

The blueprint ships with mappings for add_to_cart, add_to_wishlist, newsletter_unsubscribed, page, purchase, remove_from_cart, search, sign_up, and more. Any event in your schema can be mapped to Bluecore through pipeline configuration without a code change.

Do I need to keep the Bluecore tag on my site?

No. Signal delivers to Bluecore from the server, so no client-side Bluecore script is required on your site.

Ready to move Bluecore server-side?

See how Datafly Signal delivers first-party events to Bluecore from infrastructure you control, with hashed identity and consent enforcement built in.