CONNECTIONS / BigQuery / BigQuery to Meta Offline CAPI
From BigQuery datasets to Meta's offline optimization.
Point Signals at the dataset behind a read-only service account, and it credits dealer, branch, and phone sales to the Meta campaigns behind them on the cadence your scheduled query already keeps.
- ● bigquery → meta.capi :: live
- > read sales.pos_transactions rows=64,467
- hash sha256(email,phone) consent=filtered
- route meta deliver
- ✓ delivered · 56,086 matched
WHAT THIS ENABLES
BigQuery to Meta Offline CAPI
BigQuery to Meta Offline CAPI: A scheduled query reads the offline and in-store sales in your BigQuery tables, and Signals credits dealer, branch, and phone sales to the Meta campaigns behind them, hashed and consent-checked whenever the scheduled query reruns.
- Signals credits dealer, branch, and phone sales to the Meta campaigns behind them, reading your BigQuery tables whenever the scheduled query reruns.
- In-store and phone revenue joining Meta's optimization loop, fed by analytics engineers running BigQuery scheduled queries.
The click, the conversion, and the credit.
The conversion happens off Meta, away from any pixel. Here is how BigQuery closes the loop.
Built for the teams that own the number.
Analytics engineers running BigQuery scheduled queries who need in-store and phone revenue joining Meta's optimization loop.
From kickoff to verified events.
-
Connect
A read-only service account with dataViewer on the one dataset you nominate to feed Meta's Offline Conversions API, sized for Meta's 62-day event window.
-
Map
A scheduled query reads your BigQuery tables, and its columns map to Meta's Offline Conversions API in the visual mapper, hashed and checked for Meta's 62-day event window.
-
Deliver
Whenever the scheduled query reruns, Signals credits dealer, branch, and phone sales to the Meta campaigns behind them, scans only the rows the query changed, with Meta's 62-day event window watched in the debugger.
What changes when the CSV goes away.
| Capability | Manual CSV upload | Datahash |
|---|---|---|
| Reporting | Offline sales sit in a separate export, reconciled by hand. | Revenue counted in the same Offline CAPI reporting as web conversions. |
| Deduplication | A re-uploaded file risks counting the same conversion twice. | Deduped delivery, so a resent record never counts as a second conversion. |
| Match visibility | Match quality is a guess until the numbers look off. | Match rate reported per upload, tied to the source event set that produced it. |
| Effort and latency | An analyst exports and uploads on a manual cadence. | Server-side and automatic the moment BigQuery records the event. |
What Offline CAPI actually receives.
- ● signals :: event payload
- > POST /offline_conversions source=bigquery.sales.pos_transactions
- event_name "Purchase" · event_time 2026-07-22T03:35:49
- value 41418.00 · currency USD
- em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-52349"
- ✓ accepted match=87%
Adjacent moves on the same stack.
from BigQuery
BigQuery to Google OCI
BigQuery to Google Offline Conversions: A scheduled query reads the offline and in-store…
Learn morefrom BigQuery
BigQuery to Google Store Sales
BigQuery to Google Store Sales: A scheduled query reads the offline and in-store sales in…
Learn more
same use case
ActiveCampaign to Meta Offline CAPI
ActiveCampaign to Meta Offline CAPI: Signals reads your ActiveCampaign contacts and deal…
Learn moregeneric
Meta Offline CAPI
Datahash ingests offline transactions from your POS, CRM, or warehouse and routes them to…
Learn moreAsked on almost every call.
How often does the BigQuery Meta Offline CAPI sync run?
The scheduled query sets the pace: rebuild the offline and in-store sales nightly and delivery to Meta is nightly, or refresh hourly for an hourly feed. Each run only reads the rows the query changed, so in-store and phone revenue joining Meta's optimization loop stays current for Meta's 62-day event window while BigQuery slot cost barely moves.
What match rate should a BigQuery-sourced Meta Offline CAPI batch expect?
Coverage in your BigQuery tables decides the rate, not BigQuery. A row with a current hashed email or phone matches; one missing both cannot, however the query is tuned. The first run's report from Meta's Offline Conversions API sets a baseline, the number considered-purchase brands closing revenue far from the browser weigh against Meta's 62-day event window.
NEXT STEP