CONNECTIONS / Box / Box to Google OCI
Your Box files, wired to Google Ads offline conversion import.
Connect Box and point Signals at your Box files; it reconciles closed-won revenue to the Google Ads click through GCLID each time a new file lands, hashed and consent-checked for Google Ads.
- ● box → google.oci :: live
- > read closed_deals rows=37,939
- hash sha256(email,phone) consent=filtered
- route google deliver
- ✓ delivered · 31,110 matched
WHAT THIS ENABLES
Box to Google Offline Conversions
Box to Google Offline Conversions: Signals reads your Box files and reconciles closed-won revenue to the Google Ads click through GCLID, 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 reconciles closed-won revenue to the Google Ads click through GCLID.
- Smart Bidding trained on booked revenue instead of a mid-funnel proxy, 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 Ads offline conversion import straight from Box files.
From kickoff to verified events.
-
Connect
Read-only OAuth access to the Box folder you name to feed Google Ads' Offline Conversion Import (Google Ads API), sized for GCLID coverage.
-
Map
Signals picks up your Box files, and its columns map to Google Ads' Offline Conversion Import (Google Ads API) in the visual mapper, hashed and checked for GCLID coverage.
-
Deliver
On each run, Signals pulls your Box files, reconciles closed-won revenue to the Google Ads click through GCLID, and processes only the newly dropped file, with GCLID coverage 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 OCI 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 OCI actually receives.
- ● signals :: event payload
- > POST /offline_conversion_import source=box.closed_deals
- gclid "Cj0KCQjw…" · conversion_action "closed_won"
- conversion_date_time "2026-07-13T01:20:32"
- conversion_value 40904 · currency_code AED
- ✓ accepted · batch=hourly
Adjacent moves on the same stack.
from Box
Box to Google Store Sales
Box to Google Store Sales: Signals reads your Box files and matches in-person transactions…
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 OCI
ActiveCampaign to Google Offline Conversions: Signals reads your ActiveCampaign contacts…
Learn moregeneric
Google Offline Conversion Import
Datahash automates GCLID-based OCI uploads to Google Ads so click-based offline conversions…
Learn moreAsked on almost every call.
How often does the Box Google OCI 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 a clean line from click to closed revenue holds up on GCLID coverage. The live debugger confirms every delivery inline.
What match rate should a Box-sourced Google OCI 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 Offline Conversion Import (Google Ads API) pinpoints GCLID coverage, the number ops teams sharing exports in Box tune against.
NEXT STEP