Integrations / Data Warehouse
Google BigQuery
Structured event delivery to Google BigQuery for analytics and reporting.
Datafly Signal delivers first-party events to Google BigQuery server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Google BigQuery expects.
Why route Google BigQuery through Datafly Signal
The data lands in infrastructure you own
Signal writes to your Google BigQuery directly from your own deployment. Datafly operates no intermediary and never holds a copy of your event data.
Email and phone number 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.
One consent decision governs every destination
Google BigQuery 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_checkoutbooking_cancelledbooking_completedbooking_startedbrochure_downloadedcontent_likedcontent_savedcontent_sharedcontent_vieweddealer_contacteddestination_searchedfeature_usedfinance_quote_requestedinvoice_paidlisting_viewedloginnewsletter_subscribedpagepaywall_viewedpurchaserefundremove_from_cartsearchselect_promotionservice_appointment_bookedsign_upsubscription_cancelledsubscription_startedtest_drive_bookedtrade_in_valuedtrial_startedvehicle_savedvehicle_searchedvehicle_viewedvideo_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, Travel, B2B / SaaS, General, Automotive. 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 Google BigQuery documentation.
Frequently asked questions
Does Datafly Signal integrate with Google BigQuery?
Yes. Datafly Signal delivers first-party events to Google BigQuery server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Google BigQuery expects. The integration is included in every deployment at no additional cost.
How is server-side Google BigQuery tracking different from the Google BigQuery tag?
The Google BigQuery 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 Google BigQuery from your server, so delivery does not depend on browser conditions.
What personal data is sent to Google BigQuery?
Email and phone number are normalised and SHA-256 hashed inside your own deployment before delivery, so Google BigQuery receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to Google BigQuery?
The blueprint ships with mappings for ad_impression, add_to_cart, begin_checkout, booking_cancelled, booking_completed, booking_started, brochure_downloaded, content_liked, and more. Any event in your schema can be mapped to Google BigQuery through pipeline configuration without a code change.
Do I need to keep the Google BigQuery tag on my site?
No. Signal delivers to Google BigQuery from the server, so no client-side Google BigQuery script is required on your site.
Other data warehouse integrations
Ready to move Google BigQuery server-side?
See how Datafly Signal delivers first-party events to Google BigQuery from infrastructure you control, with hashed identity and consent enforcement built in.