CONNECTIONS / BigCommerce / BigCommerce to Google Store Sales
Your BigCommerce orders, wired to Google Store Sales matching.
Connect BigCommerce and point Signals at your BigCommerce orders; it matches in-person transactions to Google accounts as store-sales conversions as orders complete, hashed and consent-checked for Google Ads.
- ● bigcommerce → google.sales :: live
- > read closed_deals rows=9,805
- hash sha256(email,phone) consent=filtered
- route google deliver
- ✓ delivered · 7,746 matched
WHAT THIS ENABLES
BigCommerce to Google Store Sales
Google Store Sales for BigCommerce: Signals matches in-person transactions to Google accounts as store-sales conversions straight from your BigCommerce orders, hashed and consent-screened as orders complete.
- Offline and in-store sales from your BigCommerce orders activated for Google Ads, as Signals matches in-person transactions to Google accounts as store-sales conversions.
- Counter and showroom revenue inside the same ROAS view as online orders, drawn from your BigCommerce orders by merchants running BigCommerce.
The click, the conversion, and the credit.
The conversion happens off Google, away from any pixel. Here is how BigCommerce closes the loop.
Built for the teams that own the number.
Merchants running BigCommerce activating Google Store Sales matching straight from BigCommerce orders.
From kickoff to verified events.
-
Connect
Scoped API access to BigCommerce, reading only your BigCommerce orders to feed Google Ads' Store Sales Direct API, sized for the store-sales match rate.
-
Map
Signals reads your BigCommerce orders, and its columns map to Google Ads' Store Sales Direct API in the visual mapper, hashed and checked for the store-sales match rate.
-
Deliver
On each run, Signals pulls your BigCommerce orders, matches in-person transactions to Google accounts as store-sales conversions, and sends only the orders that changed, with the store-sales match rate 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 Store Sales 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 BigCommerce records the event. |
What Store Sales actually receives.
- ● signals :: store sales upload
- > POST /offline_user_data_jobs source=bigcommerce.closed_deals
- transaction_time 2026-07-19T19:26:17 · transaction_amount_micros 20847000000
- currency_code USD
- hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
- ✓ accepted match=79%
Adjacent moves on the same stack.
from BigCommerce
BigCommerce to Google OCI
Google Offline Conversions for BigCommerce: Signals reconciles closed-won revenue to the…
Learn more
from BigCommerce
BigCommerce to Meta Offline CAPI
Meta Offline CAPI for BigCommerce: Signals credits dealer, branch, and phone sales to the…
Learn more
same use case
ActiveCampaign to Google Store Sales
ActiveCampaign to Google Store Sales: Signals reads your ActiveCampaign contacts and deal…
Learn moregeneric
Google Store Sales
Datahash automates Store Sales Direct and Store Sales Customer Match uploads from your POS…
Learn moreAsked on almost every call.
How often does the BigCommerce Google Store Sales sync run?
The pace follows your BigCommerce orders: Signals sends changes from BigCommerce to Google Ads as orders complete. Because it sends only the orders that changed, counter and showroom revenue inside the same ROAS view as online orders stays current while merchants running BigCommerce keep the store-sales match rate in view. Delivery needs no export and no manual upload.
What match rate should a BigCommerce-sourced Google Store Sales batch expect?
Coverage of hashed identifiers across your BigCommerce orders decides it, and merchants running BigCommerce own that inside BigCommerce. A live email or phone matches into Google Ads; neither, and it will not. First-run feedback flags the store-sales match rate, which merchants running BigCommerce then raise inside your BigCommerce orders.
NEXT STEP