CONNECTIONS / BigQuery
BigQuery + Datahash: activate the warehouse you already report from.
Your GA4 exports, CRM replicas, and transaction tables live in BigQuery. Signals turns them into conversions and audiences on every ad platform.
- ● bigquery :: signals live
- > scheduled query ga4_events → conversions rows=61,240
- > table read customer_ltv_segments
- hash sha256(email,phone) role=dataViewer
- route meta · google · tiktok · snap · linkedin
- ✓ 5 destinations synced · match 87%
The signal BigQuery yields, and receives.
Every kind of signal that moves between BigQuery and the platforms, through one hashed, deduplicated route.
- Offline conversions
- Closed-won and point-of-sale tables leave BigQuery hashed and matched to the campaign that drove the sale.
- Lead conversions
- Lead-stage tables refresh on the scheduled query's cadence and arrive as conversion events, no export job.
- Custom audiences
- An LTV segment written once in SQL becomes a hashed, scheduled audience with no CSV on anyone's laptop.
- Lead generation inbound
- Renewal and subscription events post as they land, so recurring revenue reaches bidding the day it books.
Pick your platform. Every use case for it, in one place.
Every way BigQuery data moves, grouped by platform and ranked by how many use cases BigQuery supports.
Google 5 
Meta 4 
Snap 4 
TikTok 4 
LinkedIn 3 
OpenAI 1 - Offline conversions Google Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Offline conversions Google Store Sales Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Google Enhanced Conversions for Leads Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Google Customer Match Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Google Forms Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Meta Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Meta Conversions API for CRM Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Meta Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Meta Lead Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Snapchat Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Snapchat Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Snapchat Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Snapchat Lead Generation Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions TikTok Offline Events API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions TikTok CRM Events API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences TikTok Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation TikTok Lead Generation Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions LinkedIn Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions LinkedIn Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Lead generation LinkedIn Lead Generation Forms Campaign lead submissions created as records in real time, deduped before creation.
From authorization to delivered signal.
-
Connect
Connect with a scoped read-only role.
-
Map
Map columns to event fields and match keys in the visual mapper.
-
Hash and consent
Hashing and consent flags applied at read.
-
Deliver
Scheduled or incremental delivery, with per-destination match feedback.
BigQuery questions, answered.
Can we use our GA4 BigQuery export as a source?
Yes, and it is the most common BigQuery pattern we deploy. The GA4 export lands in a dataset as daily and streaming tables, and Signals reads it with a scoped service account, so the web and app events you already collect in Analytics become server-side conversions on Meta, Google, and the other platforms without a second tag on the site.
Does Datahash copy our warehouse?
No. Reads are query-scoped and delivery is event-level, so nothing from your warehouse is copied or warehoused on our side. Identifiers are SHA-256 hashed before anything leaves BigQuery, and a self-hosted Core deployment is available when data cannot leave your own environment, in which case the hashing happens inside your perimeter.
How fresh is the sync?
On a schedule you set, from every 15 minutes to weekly, with incremental runs that read only the rows a query changed. The cadence follows whatever your scheduled query already keeps, so a table rebuilt nightly delivers nightly and one refreshed every few minutes delivers close to real time, without a full re-scan on each run.
NEXT STEP
See your BigQuery data working in every ad platform.
Ready to enable a use case, or still mapping what BigQuery data could do? Our team helps you find the right place to start.
