CONNECTIONS / GCS / GCS to Google Store Sales
Your GCS objects, wired to Google Store Sales matching.
Connect GCS and point Signals at your GCS objects; it matches in-person transactions to Google accounts as store-sales conversions each time a new file lands, hashed and consent-checked for Google Ads.
- ● gcs → google.sales :: live
- > read closed_deals rows=62,551
- hash sha256(email,phone) consent=filtered
- route google deliver
- ✓ delivered · 49,415 matched
WHAT THIS ENABLES
GCS to Google Store Sales
GCS to Google Store Sales: your GCS objects, hashed and consent-checked, feed Google Ads as Signals matches in-person transactions to Google accounts as store-sales conversions each time a new file lands.
- Offline and in-store sales from your GCS objects 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 GCS objects by data teams landing exports in GCS.
The click, the conversion, and the credit.
The conversion happens off Google, away from any pixel. Here is how GCS closes the loop.
Built for the teams that own the number.
Data teams landing exports in GCS activating Google Store Sales matching straight from GCS objects.
From kickoff to verified events.
-
Connect
A read-only service account scoped to the one GCS bucket you name to feed Google Ads' Store Sales Direct API, sized for the store-sales match rate.
-
Map
Signals picks up your GCS objects, 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 GCS objects, matches in-person transactions to Google accounts as store-sales conversions, and processes only the newly dropped file, 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 GCS records the event. |
What Store Sales actually receives.
- ● signals :: store sales upload
- > POST /offline_user_data_jobs source=google-cloud-storage.closed_deals
- transaction_time 2026-07-23T07:07:53 · transaction_amount_micros 12209000000
- currency_code USD
- hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
- ✓ accepted match=79%
Adjacent moves on the same stack.
from GCS
GCS to Google OCI
GCS to Google Offline Conversions: your GCS objects, hashed and consent-checked, feed…
Learn more
from GCS
GCS to Meta Offline CAPI
GCS to Meta Offline CAPI: your GCS objects, hashed and consent-checked, feed Meta as…
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 GCS Google Store Sales sync run?
The pace follows your GCS objects: Signals sends changes from GCS to Google Ads each time a new file lands. Because it processes only the newly dropped file, counter and showroom revenue inside the same ROAS view as online orders stays current while data teams landing exports in GCS keep the store-sales match rate in view. Delivery needs no export and no manual upload.
What match rate should a GCS-sourced Google Store Sales batch expect?
Coverage of hashed identifiers across your GCS objects decides it, and data teams landing exports in GCS own that inside GCS. A live email or phone matches into Google Ads; neither, and it will not. First-run feedback flags the store-sales match rate, which data teams landing exports in GCS then raise inside your GCS objects.
NEXT STEP