What BigQuery is
BigQuery is Google Cloud’s warehouse, and for most commerce teams it is where the analysis that matters actually happens.
Warehouse analysis is only trustworthy if it reconciles with what the ad platforms were told.
Stream resolved events and orders into BigQuery, so your analysts work from the same identity graph the ad platforms receive.
About BigQuery
When a number disagrees with a platform, that becomes a finding rather than an unresolvable argument about whose pipeline is right.
BigQuery is Google Cloud’s warehouse, and for most commerce teams it is where the analysis that matters actually happens.
Warehouse analysis is only trustworthy if it reconciles with what the ad platforms were told.
BigQuery stores whatever you load into it and answers questions at scale. The usual failure is not the warehouse. It is that the orders in it and the conversions sent to Meta were produced by two pipelines with two definitions.
What you can do with it
01
Conversions reach BigQuery through its server-side API with restored click IDs and hashed identifiers attached, so more of what you send is matched on arrival, and the conversions you never saw stop being invisible.
02
Map any order attribute to the conversion BigQuery receives (profit rather than revenue, new customers rather than repeat buyers, high-value orders rather than every checkout), so the platform learns from the buyers worth acquiring.
03
The rows in your warehouse are the rows the ad platforms received, so a discrepancy is a real finding rather than a pipeline difference.
Documentation
Set-up, event schema and field mapping for BigQuery as a destination.
FAQ
Stream resolved events and orders into BigQuery, so your analysts work from the same identity graph the ad platforms receive.
All plans. Upstack has three plans that scale with your order volume, and the same integrations are on every plan.
Upstack’s own pixel loads asynchronously and fails silently, so it doesn’t hold up your pages. What each destination adds depends on its Tracking Method. The default, Browser + Server, loads that platform’s own tag on your store, in place of the copy you would otherwise install yourself, and also sends the same events from Upstack’s servers. Choose Server for any destination that offers it and its tag never loads, while its events still arrive from Upstack’s servers.
Similar integrations
Google Sheets Resolved data where the team already works.
Reddit Conversions API for a community-led audience.
Microsoft Ads UET conversions with restored identifiers.
X Conversions API, deduplicated server-side.
AppLovin Browser delivery through the Axon Pixel.
Outbrain Native conversions with the click restored. A 15-minute walkthrough tailored to your stack and channels.