Integrations / Personalisation
Dynamic Yield
Server-side event delivery to the Dynamic Yield (Mastercard) Experience API. Sends purchase, add-to-cart, sync-cart, add-to-wishlist, identify, newsletter, search, filter, and sort events with server-side identity (dyid_server), IP/User-Agent forwarding, and consent gating so Dynamic Yield personalisation, recommendations, and affinity modelling run without a client-side pixel.
Datafly Signal delivers first-party events to Dynamic Yield server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Dynamic Yield expects.
Why route Dynamic Yield through Datafly Signal
Profiles update from the server, not the browser
Events reach Dynamic Yield even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
Email hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so Dynamic Yield receives match keys rather than raw personal data.
Client IP and user agent are carried in the payload
Both are taken from the original visitor request rather than your server, which is what Dynamic Yield needs to attribute the event to the right session.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the Dynamic Yield rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
Dynamic Yield 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_wishlistidentifyloginnewsletter_subscribedpageproducts_filteredproducts_sortedpurchaseremove_from_cartsearchsign_upview_cartview_itemVertical presets
Retail / Ecommerce. 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 Dynamic Yield documentation.
Frequently asked questions
Does Datafly Signal integrate with Dynamic Yield?
Yes. Datafly Signal delivers first-party events to Dynamic Yield server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Dynamic Yield expects. The integration is included in every deployment at no additional cost.
How is server-side Dynamic Yield tracking different from the Dynamic Yield tag?
The Dynamic Yield 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 Dynamic Yield from your server, so delivery does not depend on browser conditions.
What personal data is sent to Dynamic Yield?
Email are normalised and SHA-256 hashed inside your own deployment before delivery, so Dynamic Yield receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to Dynamic Yield?
The blueprint ships with mappings for add_to_cart, add_to_wishlist, identify, login, newsletter_subscribed, page, products_filtered, products_sorted, and more. Any event in your schema can be mapped to Dynamic Yield through pipeline configuration without a code change.
Do I need to keep the Dynamic Yield tag on my site?
No. Signal delivers to Dynamic Yield from the server, so no client-side Dynamic Yield script is required on your site.
Other personalisation integrations
Ready to move Dynamic Yield server-side?
See how Datafly Signal delivers first-party events to Dynamic Yield from infrastructure you control, with hashed identity and consent enforcement built in.