Integrations / Data Warehouse
Databricks (Zerobus Ingest)
Real-time event streaming to Databricks Delta Lake via Zerobus Ingest API.
Datafly Signal delivers first-party events to Databricks (Zerobus Ingest) server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Databricks (Zerobus Ingest) expects.
Why route Databricks (Zerobus Ingest) through Datafly Signal
The data lands in infrastructure you own
Signal writes to your Databricks (Zerobus Ingest) directly from your own deployment. Datafly operates no intermediary and never holds a copy of your event data.
Email hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so the table holds hashed identifiers rather than raw personal 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.
Token lifecycle is handled for you
Signal obtains and refreshes the OAuth credentials Databricks (Zerobus Ingest) requires, so nothing expires quietly in the middle of a campaign.
One consent decision governs every destination
Databricks (Zerobus Ingest) 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
ad_impressionadd_to_cartbegin_checkoutcontent_likedcontent_savedcontent_sharedcontent_viewedfeature_usedinvoice_paidloginnewsletter_subscribedpagepaywall_viewedpurchaserefundremove_from_cartsearchselect_promotionsign_upsubscription_cancelledsubscription_startedtrial_startedvideo_ad_completedvideo_ad_skippedvideo_ad_startedvideo_content_completedvideo_content_startedvideo_playback_completedvideo_playback_pausedvideo_playback_resumedvideo_playback_startedview_cartview_itemview_item_listVertical presets
Retail, Media & Publishing, B2B / SaaS, 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 Databricks (Zerobus Ingest) documentation.
Frequently asked questions
Does Datafly Signal integrate with Databricks (Zerobus Ingest)?
Yes. Datafly Signal delivers first-party events to Databricks (Zerobus Ingest) server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Databricks (Zerobus Ingest) expects. The integration is included in every deployment at no additional cost.
How is server-side Databricks (Zerobus Ingest) tracking different from the Databricks (Zerobus Ingest) tag?
The Databricks (Zerobus Ingest) 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 Databricks (Zerobus Ingest) from your server, so delivery does not depend on browser conditions.
What personal data is sent to Databricks (Zerobus Ingest)?
Email are normalised and SHA-256 hashed inside your own deployment before delivery, so Databricks (Zerobus Ingest) receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to Databricks (Zerobus Ingest)?
The blueprint ships with mappings for ad_impression, add_to_cart, begin_checkout, content_liked, content_saved, content_shared, content_viewed, feature_used, and more. Any event in your schema can be mapped to Databricks (Zerobus Ingest) through pipeline configuration without a code change.
Do I need to keep the Databricks (Zerobus Ingest) tag on my site?
No. Signal delivers to Databricks (Zerobus Ingest) from the server, so no client-side Databricks (Zerobus Ingest) script is required on your site.
Other data warehouse integrations
Ready to move Databricks (Zerobus Ingest) server-side?
See how Datafly Signal delivers first-party events to Databricks (Zerobus Ingest) from infrastructure you control, with hashed identity and consent enforcement built in.