Integrations / Personalisation
Monetate
Server-side delivery to the Monetate (Kibo Personalization) Engine API. Sends context and conversion events (page views, product detail/thumbnail views, cart, purchase) to https://engine.monetate.net/api/engine/v1/decide/{retailer_short_name} with the visitor identified by monetateId/deviceId/customerId and the account scoped by the channel string. Powers personalization, experimentation, and recommendations without a client-side tag.
Datafly Signal delivers first-party events to Monetate server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Monetate expects.
Why route Monetate through Datafly Signal
Profiles update from the server, not the browser
Events reach Monetate even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the Monetate rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
Monetate 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_cartpagepurchaseview_cartview_itemview_item_listVertical 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 Monetate documentation.
Frequently asked questions
Does Datafly Signal integrate with Monetate?
Yes. Datafly Signal delivers first-party events to Monetate server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Monetate expects. The integration is included in every deployment at no additional cost.
How is server-side Monetate tracking different from the Monetate tag?
The Monetate 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 Monetate from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Monetate?
The blueprint ships with mappings for add_to_cart, page, purchase, view_cart, view_item, view_item_list. Any event in your schema can be mapped to Monetate through pipeline configuration without a code change.
Do I need to keep the Monetate tag on my site?
No. Signal delivers to Monetate from the server, so no client-side Monetate script is required on your site.
Other personalisation integrations
Ready to move Monetate server-side?
See how Datafly Signal delivers first-party events to Monetate from infrastructure you control, with hashed identity and consent enforcement built in.