Azure Data Explorer

Datafly Signal writes events directly into an Azure Data Explorer (Kusto) table so you can query first-party behaviour using KQL.

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 done in the warehouse reflects the actual visitor.
• Presets for eight verticals. General (the default: page, identify and the key cross-vertical events), Retail, Insurance, Travel, Media & Streaming, Publishing, B2B / SaaS and Automotive, each writing one named field per documented event property. Email, phone and names are written only as SHA-256 digests unless you deliberately change the installed blueprint.
• 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.

Prerequisites

Before configuring Azure Data Explorer in Signal, you need an Azure account with an ADX cluster, a database and table, and an Azure AD app registration for authentication.

.create table SignalEvents (
  message_id: string,
  event_id: string,
  event: string,
  type: string,
  anonymous_id: string,
  user_id: string,
  device_id: string,
  timestamp: datetime,
  sent_at: datetime,
  received_at: datetime,
  org_id: string,
  pipeline_id: string,
  vendor_type: string,
  properties: dynamic,
  context: dynamic,
  click_ids: dynamic,
  collected_ids: dynamic
)

.create table SignalEvents ingestion json mapping 'SignalEventsMapping' '[{"column":"message_id","Properties":{"Path":"$.message_id"}},{"column":"event_id","Properties":{"Path":"$.event_id"}},{"column":"event","Properties":{"Path":"$.event"}},{"column":"type","Properties":{"Path":"$.type"}},{"column":"anonymous_id","Properties":{"Path":"$.anonymous_id"}},{"column":"user_id","Properties":{"Path":"$.user_id"}},{"column":"device_id","Properties":{"Path":"$.device_id"}},{"column":"timestamp","Properties":{"Path":"$.timestamp"}},{"column":"sent_at","Properties":{"Path":"$.sent_at"}},{"column":"received_at","Properties":{"Path":"$.received_at"}},{"column":"org_id","Properties":{"Path":"$.org_id"}},{"column":"pipeline_id","Properties":{"Path":"$.pipeline_id"}},{"column":"vendor_type","Properties":{"Path":"$.vendor_type"}},{"column":"properties","Properties":{"Path":"$.properties"}},{"column":"context","Properties":{"Path":"$.context"}},{"column":"click_ids","Properties":{"Path":"$.click_ids"}},{"column":"collected_ids","Properties":{"Path":"$.collected_ids"}}]'

.alter table SignalEvents policy streamingingestion enable

Configuration

Signal Setup

Quick Setup

1. Navigate to Integrations in the sidebar.
2. Open the Integration Library tab.
3. Find Azure Data Explorer or filter by Warehouse.
4. Click Install, select a variant if available, and fill in the required fields.
5. Click Install Integration to create the integration with a ready-to-use default blueprint.

API Setup

curl -X POST http://localhost:8084/v1/admin/integration-catalog/azure_data_explorer/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Azure Data Explorer",
    "variant": "default",
    "config": {
      "cluster_url": "https://datafly-adx.westeurope.kusto.windows.net",
      "database": "analytics",
      "table_name": "SignalEvents",
      "ingestion_mapping": "SignalEventsMapping",
      "client_id": "00000000-0000-0000-0000-000000000000",
      "client_secret": "YOUR_CLIENT_SECRET",
      "tenant_id": "00000000-0000-0000-0000-000000000000"
    },
    "delivery_mode": "server_side"
  }'

What Signal writes

Each event is one streaming ingestion request: POST <cluster>/v1/rest/ingest/<database>/<table>?streamFormat=Json&mappingName=<ingestion_mapping>, gzip-compressed, with a bearer token for the Entra application. The body is the Signal event as one JSON record (the same document the streaming destinations send):

A streaming ingestion request is limited to 4 MB. Query mapped fields with dot notation, for example SignalEvents | where event == "purchase" | project transaction_id = tostring(properties.transaction_id), value = todouble(properties.value), email_sha256 = tostring(properties["@root"].email_sha256).

Stored event context

Alongside the fields your blueprint maps (where email, phone, names and address are stored as normalised SHA-256 by default), each message carries the event’s collected context exactly as Signal received it. The blueprint does not filter or hash the context: this is deliberate (decision 2026-09-23), so the context is complete for attribution, fraud and debugging queries, and it is listed here so you can decide what to keep.

Each message is the event JSON: context, click_ids and collected_ids, and the anonymous_id, user_id, device_id, message_id and event_id identifiers, sit beside the mapped properties.

The IP address, device and advertising IDs, and cookie and click identifiers are personal data under UK and EU GDPR. To keep any of them out of storage, strip, mask or hash the field for every integration with the organisation data layer, apply URL redaction to page URLs, or remove it in the installed blueprint; and set the storage’s retention to match your privacy notice. See Personal data by integration.

Consent

The integration’s consent category in Signal decides which events reach Azure Data Explorer; events that fail it are never written. Every row also carries the visitor’s consent state (context.consent / context_json, and consent_analytics / consent_marketing in @root) so downstream queries can apply their own rules.

Testing

1. Enable the integration in Signal and trigger a test event on your website.
2. In the ADX cluster, go to Query and select your database.
3. Run a query to check for events:

SignalEvents
| order by timestamp desc
| take 10

4. Verify that event rows are appearing with correct data.
5. In Signal, check the Live Events view to confirm delivery status shows as successful.

Troubleshooting

See also

• Data Warehouses overview
• Azure Synapse Analytics
• Azure SQL
• Azure Event Hubs