CONNECTIONS / Dropbox

Dropbox + Datahash: team folder exports become ad signals.

Growth and ops teams keep conversion and CRM exports in a shared Dropbox team folder. Signals watches that folder, hashes the identifiers in each file on arrival, and routes matched rows to Meta, Google, TikTok, and Snap, then discards the file.

Talk to our team Explore use cases

dropbox :: live

● dropbox :: signals live
> file arrived /Team Folders/Ecommerce/conversions_2026-07-18.csv
> parse rows=27,318 schema=conversions
hash sha256(email,phone)
route meta · google · tiktok · snap
✓ 4 destinations synced · match 81%

WHAT FLOWS THROUGH DROPBOX

The signal Dropbox yields, and receives.

Every kind of signal that moves between Dropbox and the platforms, through one hashed, deduplicated route.

Offline conversions: A file saved into the watched Dropbox team folder is picked up on schedule and parsed, so an export a teammate drops in from a laptop still reaches the platforms.
Lead conversions: The column mapper reads whatever header row that team folder's export uses, so a shared workspace with more than one contributor does not need one fixed file layout.
Custom audiences: As soon as the file opens, its emails and phone numbers are turned into SHA-256 hashes, and the file itself never survives past that processing run.
Lead generation inbound: Status comes back for each row and destination together, so a rejection surfaces the moment it happens instead of hiding inside a campaign's aggregate numbers.

USE-CASE LISTING

Pick your platform. Every use case for it, in one place.

Every way Dropbox data moves, grouped by platform and ranked by how many use cases Dropbox supports.

Google 5

Meta 4

Snap 4

TikTok 4

LinkedIn 3

OpenAI 1

Offline conversions OpenAI Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.

HOW IT CONNECTS

From authorization to delivered signal.

Connect

Connect Dropbox with a scoped, read-only app connection.
Watch

Point Signals at the team folder and file pattern your exports use.
Map

Line up each column with an event and identifier type in the visual mapper.
Go live

Review a batch of sample rows in the live debugger, then switch delivery on.

FAQ

Dropbox questions, answered.

Which file formats are supported?

Most exports arrive as CSV or TSV with a header row, though a fixed-width file can be aligned manually in the column mapper. Signals watches one Dropbox folder and file pattern you specify, parsing every matching file on arrival, which means a scheduled export job keeps working without further setup.

Does this work with Dropbox Business team folders?

Yes. Signals connects to a specific team folder inside a Dropbox Business account through a scoped, read-only app connection, not through an individual member's personal account. Whatever team folder permissions your admin console already enforces stay in place, since Signals only reads the folder it has been explicitly granted access to.

Is customer PII stored by Datahash?

Identifiers never reach a platform unhashed. SHA-256 hashing happens at ingestion, host servers in Datahash Cloud hold no PII, and the source file is deleted the moment processing completes. For teams that cannot let data leave their perimeter, self-hosted Core performs that same hashing inside their own environment first.

How often are files picked up?

The schedule is yours to set, whether that means checking every few minutes or once daily, and every file is processed a single time with row-by-row reporting. A new arrival in the team folder kicks off the next run automatically, so the pace matches however often your Dropbox export job writes.

NEXT STEP