CONNECTIONS / Box / Box to Google Store Sales
Your Box files, wired to Google Store Sales matching.
Connect Box and point Signals at your Box 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.
- ● box → google.sales :: live
- > read closed_deals rows=46,793
- hash sha256(email,phone) consent=filtered
- route google deliver
- ✓ delivered · 38,838 matched
WHAT THIS ENABLES
Box to Google Store Sales
Box to Google Store Sales: Signals reads your Box 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 Box 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 Box files by ops teams sharing exports in Box.
The click, the conversion, and the credit.
The conversion happens off Google, away from any pixel. Here is how Box closes the loop.
Built for the teams that own the number.
Ops teams sharing exports in Box activating Google Store Sales matching straight from Box files.
From kickoff to verified events.
-
Connect
Read-only OAuth access to the Box folder you name to feed Google Ads' Store Sales Direct API, sized for the store-sales match rate.
-
Map
Signals picks up your Box 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 Box 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 Box records the event. |
What Store Sales actually receives.
- ● signals :: store sales upload
- > POST /offline_user_data_jobs source=box.closed_deals
- transaction_time 2026-07-15T16:13:57 · transaction_amount_micros 38092000000
- currency_code USD
- hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
- ✓ accepted match=83%
Adjacent moves on the same stack.
from Box
Box to Google OCI
Box to Google Offline Conversions: Signals reads your Box files and reconciles closed-won…
Learn more
from Box
Box to Meta Offline CAPI
Box to Meta Offline CAPI: Signals reads your Box files and credits dealer, branch, and…
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 Box Google Store Sales sync run?
Delivery tracks Box, run by ops teams sharing exports in Box: a near-real-time or scheduled sync of your Box files feeds Google Ads on that cadence. Each run processes only the newly dropped file, so store visits reconciled to campaign spend holds up on the store-sales match rate. The live debugger confirms every delivery inline.
What match rate should a Box-sourced Google Store Sales batch expect?
Match rate follows identifier coverage in your Box files, which ops teams sharing exports in Box control, not Box 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 ops teams sharing exports in Box tune against.
NEXT STEP