CONNECTIONS / Box / Box to OpenAI Offline CAPI
Your Box files, wired to OpenAI's Offline Conversions API.
Connect Box and point Signals at your Box files; it reports downstream revenue as OpenAI's conversion measurement comes online each time a new file lands, hashed and consent-checked for OpenAI.
- ● box → openai.capi :: live
- > read closed_deals rows=19,649
- hash sha256(email,phone) consent=filtered
- route openai deliver
- ✓ delivered · 16,309 matched
WHAT THIS ENABLES
Box to OpenAI Offline CAPI
Box to OpenAI Offline CAPI: Signals reads your Box files and reports downstream revenue as OpenAI's conversion measurement comes online, hashed and consent-checked each time a new file lands.
- Offline and in-store sales from your Box files activated for OpenAI, as Signals reports downstream revenue as OpenAI's conversion measurement comes online.
- A revenue feed ready the moment OpenAI's offline measurement expands, drawn from your Box files by ops teams sharing exports in Box.
The click, the conversion, and the credit.
The conversion happens off OpenAI, 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 OpenAI's Offline Conversions API straight from Box files.
From kickoff to verified events.
-
Connect
Read-only OAuth access to the Box folder you name to feed OpenAI's Offline Conversions API, sized for the emerging OpenAI ad surface.
-
Map
Signals picks up your Box files, and its columns map to OpenAI's Offline Conversions API in the visual mapper, hashed and checked for the emerging OpenAI ad surface.
-
Deliver
On each run, Signals pulls your Box files, reports downstream revenue as OpenAI's conversion measurement comes online, and processes only the newly dropped file, with the emerging OpenAI ad surface 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 Offline CAPI 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 Offline CAPI actually receives.
- ● signals :: event payload
- > POST /offline_conversions source=box.closed_deals
- event_name "Purchase" · event_time 1784679045
- em sha256 "2b9d64…" · value 24480 · currency USD
- ✓ accepted · row_status delivered
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 morefrom Box
Box to Google Store Sales
Box to Google Store Sales: Signals reads your Box files and matches in-person transactions…
Learn more
same use case
ActiveCampaign to OpenAI Offline CAPI
ActiveCampaign to OpenAI Offline CAPI: Signals reads your ActiveCampaign contacts and deal…
Learn moregeneric
OpenAI Offline Conversions API
Datahash uploads offline and in-store conversions to OpenAI with hashed identifiers, so…
Learn moreAsked on almost every call.
How often does the Box OpenAI Offline CAPI 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 OpenAI on that cadence. Each run processes only the newly dropped file, so measurement in place before the surface scales holds up on the emerging OpenAI ad surface. The live debugger confirms every delivery inline.
What match rate should a Box-sourced OpenAI Offline CAPI 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 OpenAI; one missing both cannot. First-run feedback from Offline Conversions API pinpoints the emerging OpenAI ad surface, the number ops teams sharing exports in Box tune against.
NEXT STEP