Integrations / Data Warehouse
Azure Data Explorer
Event delivery to Azure Data Explorer (Kusto).
Datafly Signal delivers first-party events to Azure Data Explorer server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Azure Data Explorer expects.
Why route Azure Data Explorer through Datafly Signal
The data lands in infrastructure you own
Signal writes to your Azure Data Explorer directly from your own deployment. Datafly operates no intermediary and never holds a copy of your event data.
Client IP and user agent are recorded as event context
Both come from the original visitor request rather than from your server, so geography and device analysis reflects the actual visitor.
One consent decision governs every destination
Azure Data Explorer 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_checkoutpagepurchaserefundremove_from_cartsearchselect_promotionview_cartview_itemview_item_listVertical presets
Retail, 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 Azure Data Explorer documentation.
Frequently asked questions
Does Datafly Signal integrate with Azure Data Explorer?
Yes. Datafly Signal delivers first-party events to Azure Data Explorer server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Azure Data Explorer expects. The integration is included in every deployment at no additional cost.
How is server-side Azure Data Explorer tracking different from the Azure Data Explorer tag?
The Azure Data Explorer 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 Azure Data Explorer from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Azure Data Explorer?
The blueprint ships with mappings for add_to_cart, begin_checkout, page, purchase, refund, remove_from_cart, search, select_promotion, and more. Any event in your schema can be mapped to Azure Data Explorer through pipeline configuration without a code change.
Do I need to keep the Azure Data Explorer tag on my site?
No. Signal delivers to Azure Data Explorer from the server, so no client-side Azure Data Explorer script is required on your site.
Other data warehouse integrations
Ready to move Azure Data Explorer server-side?
See how Datafly Signal delivers first-party events to Azure Data Explorer from infrastructure you control, with hashed identity and consent enforcement built in.