CONNECTIONS / Box / Box to LinkedIn Offline CAPI
Your Box files, wired to LinkedIn account-revenue reporting.
Connect Box and point Signals at your Box files; it reports closed B2B deals so LinkedIn optimizes on account revenue each time a new file lands, hashed and consent-checked for LinkedIn.
- ● box → linkedin.capi :: live
- > read closed_deals rows=12,654
- hash sha256(email,phone) consent=filtered
- route linkedin deliver
- ✓ delivered · 11,009 matched
WHAT THIS ENABLES
Box to LinkedIn Offline CAPI
Box to LinkedIn Offline CAPI: Signals reads your Box files and reports closed B2B deals so LinkedIn optimizes on account revenue, hashed and consent-checked each time a new file lands.
- Offline and in-store sales from your Box files activated for LinkedIn, as Signals reports closed B2B deals so LinkedIn optimizes on account revenue.
- Pipeline revenue tied to the LinkedIn campaigns that sourced it, drawn from your Box files by ops teams sharing exports in Box.
The click, the conversion, and the credit.
The conversion happens off LinkedIn, 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 LinkedIn account-revenue reporting straight from Box files.
From kickoff to verified events.
-
Connect
Read-only OAuth access to the Box folder you name to feed LinkedIn's Conversions API, sized for long B2B attribution windows.
-
Map
Signals picks up your Box files, and its columns map to LinkedIn's Conversions API in the visual mapper, hashed and checked for long B2B attribution windows.
-
Deliver
On each run, Signals pulls your Box files, reports closed B2B deals so LinkedIn optimizes on account revenue, and processes only the newly dropped file, with long B2B attribution windows 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 /conversionEvents source=box.closed_deals
- conversion "urn:lla:llaPartnerConversion:43397"
- conversionHappenedAt 1784001397000
- user.userIds [{ idType: "SHA256_EMAIL", idValue: "9c41af…" }]
- ✓ accepted · conversionValue 36874 USD
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 LinkedIn Offline CAPI
ActiveCampaign to LinkedIn Offline CAPI: Signals reads your ActiveCampaign contacts and…
Learn moregeneric
LinkedIn Offline CAPI
Datahash routes offline outcomes, like closed deals from your CRM, to LinkedIn with hashed…
Learn moreAsked on almost every call.
How often does the Box LinkedIn 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 LinkedIn on that cadence. Each run processes only the newly dropped file, so account revenue attached to the sourcing campaign holds up on long B2B attribution windows. The live debugger confirms every delivery inline.
What match rate should a Box-sourced LinkedIn 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 LinkedIn; one missing both cannot. First-run feedback from Conversions API pinpoints long B2B attribution windows, the number ops teams sharing exports in Box tune against.
NEXT STEP