CONNECTIONS / Box
Box + Datahash: folder exports become ad signals.
Finance and RevOps drop conversion and CRM exports into a shared Box folder every day. Signals watches that folder, hashes the identifiers in each file the moment it lands, and delivers matched rows to Meta, Google, TikTok, and Snap before discarding the file.
- ● box :: signals live
- > file arrived /Finance/Exports/subscriptions_2026-07-18.csv
- > parse rows=18,940 schema=subscriptions
- hash sha256(email,phone)
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 78%
The signal Box yields, and receives.
Every kind of signal that moves between Box and the platforms, through one hashed, deduplicated route.
- Offline conversions
- A file dropped into the watched Box folder is picked up on schedule and parsed, so a finance export saved by hand still reaches the platforms without anyone forwarding it.
- Lead conversions
- The column mapper reads whatever header row your Box export uses, so a shared folder used by more than one team does not need a fixed file layout to stay useful.
- Custom audiences
- Hashing runs on read, converting emails and phone numbers to SHA-256 before anything else touches the row, and the source file is thrown away right after the run completes.
- Lead generation inbound
- A rejected row is flagged with its destination immediately, not discovered days later as an unexplained dip in conversions.
Pick your platform. Every use case for it, in one place.
Every way Box data moves, grouped by platform and ranked by how many use cases Box supports.
- Offline conversions Google Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Offline conversions Google Store Sales Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Google Enhanced Conversions for Leads Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Google Customer Match Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Google Forms Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Meta Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Meta Conversions API for CRM Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Meta Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Meta Lead Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Snapchat Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Snapchat Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Snapchat Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Snapchat Lead Generation Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions TikTok Offline Events API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions TikTok CRM Events API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences TikTok Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation TikTok Lead Generation Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions LinkedIn Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions LinkedIn Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Lead generation LinkedIn Lead Generation Forms Campaign lead submissions created as records in real time, deduped before creation.
From authorization to delivered signal.
-
Connect
Connect Box with a scoped, read-only service account.
-
Watch
Point Signals at the folder and file pattern your exports land in.
-
Map
Assign each column to an event field and identifier type in the visual mapper.
-
Go live
Confirm a batch of sample rows in the live debugger before switching on delivery.
Box questions, answered.
Which file formats are supported?
CSV and TSV with a header row cover most exports, and a fixed-width layout can still work through the column mapper's manual field alignment. Once a folder and file pattern in Box are set, anything matching that pattern is parsed the moment it lands, so a recurring export needs no extra step to keep flowing.
Do you need admin access to our Box account?
No. Signals connects with a scoped, read-only service account limited to the folder you choose, not admin rights over your whole Box instance. Folder-level permissions and any retention policy your team already has in place on that folder stay exactly as configured, since Signals only reads files it is explicitly pointed at.
Is customer PII stored by Datahash?
No. Every identifier is SHA-256 hashed at ingestion, and Datahash Cloud does not store PII on its host servers, with the source file discarded as soon as processing finishes. Where data cannot leave your perimeter at all, a self-hosted Core deployment runs the hashing step inside your own environment before any row reaches a platform.
How often are files picked up?
You set the schedule, anywhere from a few minutes apart to once a day, and each file runs through exactly once with row-level results reported back. The watched folder triggers the next run as soon as a new file appears, so cadence tracks whatever pace your export job in Box already runs on.
NEXT STEP
See your Box data working in every ad platform.
Ready to enable a use case, or still mapping what Box data could do? Our team helps you find the right place to start.