CONNECTIONS / FTP
FTP + Datahash: file drops become ad signals.
A partner or a legacy system pushes a file to your SFTP or FTP server the way it always has, with no new integration required on their end. Signals watches the directory, picks up each file once the transfer completes, hashes the identifiers, and routes the rows to every ad platform.
- ● ftp :: signals live
- > file received /incoming/partner_orders.csv
- > transfer complete size=2.4mb rows=18340
- hash sha256(email,phone)
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 76%
The signal FTP yields, and receives.
Every kind of signal that moves between FTP and the platforms, through one hashed, deduplicated route.
- Offline conversions
- Signals connects to the server and lists the watched directory on a schedule, so a partner system that only knows how to push a file to an FTP address does not need to integrate with anything new.
- Lead conversions
- Whatever header layout the partner's export uses is mapped once, so a legacy system nobody wants to touch can keep writing files exactly as it always has.
- Custom audiences
- Identifiers are hashed as soon as a completed file is parsed, and the file is cleared from processing once hashed, so raw partner data is not held longer than the run takes.
- Lead generation inbound
- Each file gets a per-destination delivery report, so a partner feed with a malformed row is flagged without blocking the rest of that day's file.
Pick your platform. Every use case for it, in one place.
Every way FTP data moves, grouped by platform and ranked by how many use cases FTP 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
Connect your SFTP or FTP server with scoped credentials.
-
Watch
Choose the directory and file pattern Signals should watch.
-
Map
Map columns to events and identifiers in the visual mapper.
-
Go live
Verify sample rows in the live debugger and go live.
FTP questions, answered.
How does Signals know a partner's file has finished uploading?
Signals connects to your SFTP or FTP server as a client and lists the watched directory on a schedule, so a partner or legacy system that only knows how to push a file to a server does not need to change anything. A file is picked up once it stops changing size, which avoids reading a partial upload mid-transfer.
Is customer PII stored by Datahash?
Identifiers are SHA-256 hashed as each file is parsed after transfer, and no PII is stored on host servers in Datahash Cloud. The file is removed from local processing storage once hashed and routed, though it can be left in place or archived on your server depending on how the watched directory is configured. A self-hosted Core deployment keeps hashing inside your perimeter when required.
Does Signals support plain FTP or only SFTP?
Both are supported. SFTP is the default recommendation since it encrypts the transfer, while plain FTP and FTPS remain available for legacy partners and systems that were never upgraded. Credentials are stored encrypted, and a connection is scoped to a single directory rather than the whole server, so a partner feed cannot see or reach anything else on that host.
NEXT STEP
See your FTP data working in every ad platform.
Ready to enable a use case, or still mapping what FTP data could do? Our team helps you find the right place to start.
