CONNECTIONS / FTP / FTP to Google Store Sales
Your FTP drops, wired to Google Store Sales matching.
Signals reads your FTP drops through read-only credentials scoped to the SFTP path you name, then matches in-person transactions to Google accounts as store-sales conversions so Google Ads sees offline conversions without an export.
- ● ftp → google.sales :: live
- > read closed_deals rows=48,460
- hash sha256(email,phone) consent=filtered
- route google deliver
- ✓ delivered · 39,737 matched
WHAT THIS ENABLES
FTP to Google Store Sales
FTP to Google Store Sales: your FTP drops, 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.
- Signals matches in-person transactions to Google accounts as store-sales conversions, reading your FTP drops each time a new file lands.
- Store visits reconciled to campaign spend, with no export step out of your FTP drops.
The click, the conversion, and the credit.
The conversion happens off Google, away from any pixel. Here is how FTP closes the loop.
Built for the teams that own the number.
Teams exporting nightly to SFTP who need counter and showroom revenue inside the same ROAS view as online orders out of FTP drops.
From kickoff to verified events.
-
Connect
Read-only credentials scoped to the SFTP path you name, mapped to Google Ads' Store Sales Direct API and tuned for the store-sales match rate.
-
Map
Columns from your FTP drops align to Google Ads' Store Sales Direct API in the visual mapper, hashed as the file lands and checked for the store-sales match rate.
-
Deliver
Each time a new file lands, Signals reads your FTP drops and matches in-person transactions to Google accounts as store-sales conversions, processes only the newly dropped file, with the store-sales match rate 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 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 FTP records the event. |
What Store Sales actually receives.
- ● signals :: store sales upload
- > POST /offline_user_data_jobs source=ftp.closed_deals
- transaction_time 2026-07-22T20:20:44 · transaction_amount_micros 45943000000
- currency_code AED
- hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
- ✓ accepted match=82%
Adjacent moves on the same stack.
from FTP
FTP to Google OCI
FTP to Google Offline Conversions: your FTP drops, hashed and consent-checked, feed Google…
Learn more
from FTP
FTP to Meta Offline CAPI
FTP to Meta Offline CAPI: your FTP drops, hashed and consent-checked, feed Meta as Signals…
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 FTP Google Store Sales sync run?
You set the cadence, from near-real-time to a nightly FTP sync of your FTP drops into Google Ads. Since Signals processes only the newly dropped file, counter and showroom revenue inside the same ROAS view as online orders keeps pace and teams exporting nightly to SFTP watch the store-sales match rate. One scoped connection sets it up, cadence adjustable later.
What match rate should a FTP-sourced Google Store Sales batch expect?
Match rate follows identifier coverage in your FTP drops, which teams exporting nightly to SFTP control, not FTP itself. A record with a current hashed email or phone matches for Google Ads; one missing both cannot. First-run feedback from Store Sales Direct API pinpoints the store-sales match rate, the number teams exporting nightly to SFTP tune against.
NEXT STEP