Integrations / Customer Data Platform
RudderStack
Forward first-party events to your RudderStack data plane. If you already have a CDP, Signal can be its first-party collector — Signal handles upstream collection on your own domain, RudderStack handles fan-out to downstream destinations.
Datafly Signal delivers first-party events to RudderStack server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload RudderStack expects.
Why route RudderStack through Datafly Signal
Profiles update from the server, not the browser
Events reach RudderStack even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
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 RudderStack needs to attribute the event to the right session.
One consent decision governs every destination
RudderStack 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
groupidentifypageVertical presets
General. 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 RudderStack documentation.
Frequently asked questions
Does Datafly Signal integrate with RudderStack?
Yes. Datafly Signal delivers first-party events to RudderStack server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload RudderStack expects. The integration is included in every deployment at no additional cost.
How is server-side RudderStack tracking different from the RudderStack tag?
The RudderStack 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 RudderStack from your server, so delivery does not depend on browser conditions.
Which events can Signal send to RudderStack?
The blueprint ships with mappings for group, identify, page. Any event in your schema can be mapped to RudderStack through pipeline configuration without a code change.
Do I need to keep the RudderStack tag on my site?
No. Signal delivers to RudderStack from the server, so no client-side RudderStack script is required on your site.
Other customer data platform integrations
Ready to move RudderStack server-side?
See how Datafly Signal delivers first-party events to RudderStack from infrastructure you control, with hashed identity and consent enforcement built in.