CONNECTIONS / OneDrive / OneDrive to Google Store Sales
From OneDrive files to Google Store Sales matching.
Connect OneDrive and point Signals at your OneDrive files; 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.
- ● onedrive → google.sales :: live
- > read closed_deals rows=24,391
- hash sha256(email,phone) consent=filtered
- route google deliver
- ✓ delivered · 19,269 matched
WHAT THIS ENABLES
OneDrive to Google Store Sales
OneDrive to Google Store Sales: Signals reads your OneDrive files and matches in-person transactions to Google accounts as store-sales conversions, hashed and consent-checked each time a new file lands.
- Offline and in-store sales from your OneDrive files 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 OneDrive files by teams sharing exports via OneDrive.
The click, the conversion, and the credit.
The conversion happens off Google, away from any pixel. Here is how OneDrive closes the loop.
Built for the teams that own the number.
Teams sharing exports via OneDrive activating Google Store Sales matching straight from OneDrive files.
From kickoff to verified events.
-
Connect
Read-only OAuth access to the OneDrive folder you name to feed Google Ads' Store Sales Direct API, sized for the store-sales match rate.
-
Map
Signals picks up your OneDrive files, 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 OneDrive files, 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 OneDrive records the event. |
What Store Sales actually receives.
- ● signals :: store sales upload
- > POST /offline_user_data_jobs source=microsoft-onedrive.closed_deals
- transaction_time 2026-07-18T17:08:29 · transaction_amount_micros 13613000000
- currency_code USD
- hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
- ✓ accepted match=79%
Adjacent moves on the same stack.
from OneDrive
OneDrive to Google OCI
OneDrive to Google Offline Conversions: Signals reads your OneDrive files and reconciles…
Learn morefrom OneDrive
OneDrive to Meta Offline CAPI
OneDrive to Meta Offline CAPI: Signals reads your OneDrive files and credits dealer,…
Learn moresame 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 OneDrive Google Store Sales sync run?
The pace follows your OneDrive files: Signals sends changes from OneDrive 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 teams sharing exports via OneDrive keep the store-sales match rate in view. Delivery needs no export and no manual upload.
What match rate should a OneDrive-sourced Google Store Sales batch expect?
Coverage of hashed identifiers across your OneDrive files decides it, and teams sharing exports via OneDrive own that inside OneDrive. A live email or phone matches into Google Ads; neither, and it will not. First-run feedback flags the store-sales match rate, which teams sharing exports via OneDrive then raise inside your OneDrive files.
NEXT STEP