File FTP
Overview
Section titled “Overview”Leads that Signals receives are written as files to an FTP, SFTP or FTPS server you control. Each export drops a timestamped file into the directory you nominate.
It is the destination for consuming systems that were never built to call an API: an on-premise application, a legacy CRM with a file importer, a partner or franchise that accepts a scheduled drop and nothing else.
Use SFTP wherever the server supports it. Plain FTP sends credentials and file contents in clear text, which is not an acceptable way to move personal data across a network.
Supported sources
Section titled “Supported sources”Sources supported by File FTP
| Category | Supported |
|---|---|
| Lead generation |
Prerequisites
Section titled “Prerequisites”- The FTP Server Address, as a hostname.
- The FTP Server Port. The defaults are 22 for SFTP, 21 for FTP and 990 for FTPS.
- The FTP Server Username and FTP Server Password, for an account with read and write access to the target directory.
Authentication
Section titled “Authentication”In Studio, open Destinations, find the Files category, and click the File FTP tile. This connector authenticates with server credentials you add manually, so there is no sign-in screen.
Configuration
Section titled “Configuration”Integration type and connection
Section titled “Integration type and connection”Select the Integration Type, which is the lead generation source the leads come from. The options are Meta Lead Ads, Snapchat Lead Generation Ads, TikTok Lead Ads, LinkedIn Lead Ads and Google Forms. Then select the lead ads connection name you want to deliver from, and give the instance a name. The instance name is yours to choose and does not have to match anything.
File transfer settings
Section titled “File transfer settings”Choose the File Transfer Mode, which can be SFTP, FTP or FTPS, and set the Data Export Frequency, which can be Real-time, 1 hour, 3 hours or 1 day. Then click Next.
Credentials and file location
Section titled “Credentials and file location”Enter the following, then click Next.
| Field | What it is | Where to find it |
|---|---|---|
| Hostname | FTP server address. | From whoever administers the server. |
| Port | FTP port number. | 22 for SFTP, 21 for FTP, 990 for FTPS, unless it has been moved. |
| Username | FTP account username, which must have read and write access. | Created on the server by its administrator. |
| Password | FTP account password. | Set when the account was created. |
| Relative Path to Data Folder | The folder path where files should be stored. If left blank, files are placed in the root directory. | Your own convention. |
Once the credentials are validated, click Finish.
Studio creates the folder structure for you. A folder named Datahash is created inside the path you give, or at the root if you leave the path blank, and inside it a subfolder named after the lead ads connection. Each export is written there with a timestamp in the filename.
Manage instance
Section titled “Manage instance”One connection writes one source to one server and directory. To deliver a second source, or to a second directory, add another instance from Manage Existing Connections. To change an existing one, click the connection name there, click the edit icon in the top right, update the values, click Next and click Finish.
Data & identifiers
Section titled “Data & identifiers”Leads are delivered as submitted. Personal data is not hashed on this destination, because the system receiving it is your own and the point is that people and applications can read it.
Once a file lands on your server, encryption at rest, retention, access control and deletion are governed by that server, not by Signals. On plain FTP the file is also unencrypted in transit, which is the reason to use SFTP.
Which fields arrive is decided by the lead form on the connected source, so a field you need that is not appearing has to be added there.
Best practices
Section titled “Best practices”- Allowlist the Datahash egress addresses rather than opening the port more widely.
- Run a housekeeping job that archives or clears consumed files. An unbounded directory ends as a full disk, and a full disk fails writes quietly.
- Rotate the password on a schedule and update the connection in the same change.
Troubleshooting & FAQ
Section titled “Troubleshooting & FAQ”It authenticates but no files appear. The account lacks write permission on the directory, or the path does not exist. Check permissions on the directory itself, not just the parent.
Plain FTP connects and then hangs. Almost always passive mode and a firewall that is not allowing the data channel. This is one of the reasons to prefer SFTP.
Files appear and then disappear. Expected, if a consumer is collecting them. Confirm with whoever owns that process before treating it as a fault.
The consumer is importing partial records. It is reading files mid-write. Have it wait for a marker instead of acting on first sight.
Writes stopped and nothing changed. Check free disk on the server and whether the password was rotated.