Integrations / Personalisation
LaunchDarkly
Import server-side custom metric events into LaunchDarkly Experimentation via the metric event import API (events.launchdarkly.com/v2/event-data-import). Maps Signal events to LaunchDarkly custom metric event keys with the canonical identifier as the user context key, so conversions tracked through Signal drive experiment metrics without the LaunchDarkly SDK.
Datafly Signal delivers first-party events to LaunchDarkly server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload LaunchDarkly expects.
Why route LaunchDarkly through Datafly Signal
Profiles update from the server, not the browser
Events reach LaunchDarkly 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
LaunchDarkly 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_cartbegin_checkoutpagepurchasesign_upview_itemVertical presets
Default. 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 LaunchDarkly documentation.
Frequently asked questions
Does Datafly Signal integrate with LaunchDarkly?
Yes. Datafly Signal delivers first-party events to LaunchDarkly server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload LaunchDarkly expects. The integration is included in every deployment at no additional cost.
How is server-side LaunchDarkly tracking different from the LaunchDarkly tag?
The LaunchDarkly 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 LaunchDarkly from your server, so delivery does not depend on browser conditions.
Which events can Signal send to LaunchDarkly?
The blueprint ships with mappings for add_to_cart, begin_checkout, page, purchase, sign_up, view_item. Any event in your schema can be mapped to LaunchDarkly through pipeline configuration without a code change.
Do I need to keep the LaunchDarkly tag on my site?
No. Signal delivers to LaunchDarkly from the server, so no client-side LaunchDarkly script is required on your site.
Other personalisation integrations
Ready to move LaunchDarkly server-side?
See how Datafly Signal delivers first-party events to LaunchDarkly from infrastructure you control, with hashed identity and consent enforcement built in.