Integrations / Other
Webhook
Forward events to your HTTP endpoint. The default blueprint sends the native event shape; edit the mappings to fully control the payload.
Datafly Signal delivers first-party events to Webhook server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Webhook expects.
Why route Webhook through Datafly Signal
Delivery happens server-to-server
Signal sends events to Webhook from your own infrastructure rather than from the visitor's browser, so delivery does not depend on client-side conditions.
One consent decision governs every destination
Webhook 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
Vertical 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 Webhook documentation.
Frequently asked questions
Does Datafly Signal integrate with Webhook?
Yes. Datafly Signal delivers first-party events to Webhook server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Webhook expects. The integration is included in every deployment at no additional cost.
How is server-side Webhook tracking different from the Webhook tag?
The Webhook 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 Webhook from your server, so delivery does not depend on browser conditions.
Do I need to keep the Webhook tag on my site?
No. Signal delivers to Webhook from the server, so no client-side Webhook script is required on your site.
Ready to move Webhook server-side?
See how Datafly Signal delivers first-party events to Webhook from infrastructure you control, with hashed identity and consent enforcement built in.