CONNECTIONS / File drops
File drops + Datahash: any file store becomes ad signals.
A POS export, a call-centre extract, or a partner feed can land in a private SFTP server, an S3 or GCS bucket, or any store your systems already use. Signals watches wherever the file lands, hashes the identifiers on arrival, and routes the rows to every ad platform, no matter which store it started in.
- ● file-drops :: signals live
- > file received pos_daily_export.csv
- > source sftp · s3 · gcs
- hash sha256(email,phone)
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 77%
The signal File drops yields, and receives.
Every kind of signal that moves between File drops and the platforms, through one hashed, deduplicated route.
- Offline conversions
- A daily POS export or an in-store transaction file lands wherever your systems already write it, and Signals reads it the same way regardless of which store sits behind that location.
- Lead conversions
- A call-centre platform or a back-office system rarely exports through an API, so its file lands here instead and is picked up on the same schedule as everything else this page covers.
- Custom audiences
- A one-off customer list for an audience build is handled the same way as a recurring feed, hashed on arrival and routed without a separate setup for a single file.
- Lead generation inbound
- A file can be picked up on a fixed schedule or the moment it lands, so a nightly POS batch and an ad hoc partner drop both reach the platforms on the cadence that fits them.
Pick your platform. Every use case for it, in one place.
Every way File drops data moves, grouped by platform and ranked by how many use cases File drops supports.
Google 5 
Meta 4 
Snap 4 
TikTok 4 
LinkedIn 3 
OpenAI 1 - 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 the drop
Point Signals at your SFTP server, S3 bucket, GCS bucket, or other file store.
-
Map and validate
Column mapping and validation rules quarantine bad rows instead of failing the batch.
-
Hash and consent
SHA-256 hashing and consent alignment are applied per record as the file is read.
-
Deliver
Scheduled or event-driven delivery, with match and reject reporting per batch.
File drops questions, answered.
What kinds of files does this cover?
A POS export, a call-centre extract, a partner feed, or any structured file a system produces on a schedule. Signals does not care which store it lands in, only that the file arrives in a location it is watching and that its rows can be mapped to events and identifiers once the format is set up.
When should I use File drops instead of a specific connector?
This page covers the general case: any file store that is not already a dedicated connector, including a private SFTP server, an S3 or GCS bucket you manage yourself, or a one-off export a partner drops somewhere. If a named connector exists for your store, such as AWS S3 or Google Drive, that page has store-specific setup detail; this option is for everything else.
Is customer PII stored by Datahash?
Identifiers are SHA-256 hashed on arrival regardless of which store the file came from, and no PII is stored on host servers in Datahash Cloud. The file is discarded once processed, and a self-hosted Core deployment applies the same hashing inside your own environment when a file cannot leave your perimeter, whichever store it started in.
NEXT STEP
See your File drops data working in every ad platform.
Ready to enable a use case, or still mapping what File drops data could do? Our team helps you find the right place to start.
