Integrations / Personalisation
Userpilot
Server-side event tracking via Userpilot's real-time HTTP Track API (/v1/track). Delivers page views and product-engagement events with the Userpilot user_id and flattened scalar metadata for segmentation and in-app flow targeting. Metadata is primitives-only, so nested product arrays are summarised to scalar fields.
Datafly Signal delivers first-party events to Userpilot server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Userpilot expects.
Why route Userpilot through Datafly Signal
Profiles update from the server, not the browser
Events reach Userpilot 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
Userpilot 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
feature_usedgenerate_leadloginpageplan_viewedsearchsign_upsubscription_cancelledsubscription_startedtrial_startedview_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 Userpilot documentation.
Frequently asked questions
Does Datafly Signal integrate with Userpilot?
Yes. Datafly Signal delivers first-party events to Userpilot server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Userpilot expects. The integration is included in every deployment at no additional cost.
How is server-side Userpilot tracking different from the Userpilot tag?
The Userpilot 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 Userpilot from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Userpilot?
The blueprint ships with mappings for feature_used, generate_lead, login, page, plan_viewed, search, sign_up, subscription_cancelled, and more. Any event in your schema can be mapped to Userpilot through pipeline configuration without a code change.
Do I need to keep the Userpilot tag on my site?
No. Signal delivers to Userpilot from the server, so no client-side Userpilot script is required on your site.
Other personalisation integrations
Ready to move Userpilot server-side?
See how Datafly Signal delivers first-party events to Userpilot from infrastructure you control, with hashed identity and consent enforcement built in.