Secure file transfer

Deprecation Notice

The Secure File Transfer (SFTP) integration documented below is now deprecated and will no longer receive new updates or enhancements. We strongly encourage all clients to migrate to the Event and Audience API Integration Guide, which offers real-time data transmission, improved reliability, and enhanced data structure for conversion tracking and audience management.

Why the change? The Event and Audience API Integration provides a modernized approach to sending conversion and audience data, enabling:

• Real-time data transmission instead of batch file processing
• Enhanced data structure with improved user identity and attribute handling
• Better error handling and immediate feedback on data submission
• Support for device information and mobile advertising IDs
• Unified interface for both conversion events and audience data
• Scalable support for future data types and integration patterns

Migration Support To assist with your migration, please refer to the Event and Audience API Integration Guide, which includes:

• Complete API reference with request/response examples
• Field mapping from SFTP file format to the new API structure
• Authentication and security best practices
• Error handling and rate limiting guidance
• Testing and validation procedures

As an alternative to integrating with the Web SDK, using the Event API, or conducting a manual import, you can automate the uploading of conversion data into the Rokt platform through the Rokt Secure FTP. If you don't have access to the Rokt SFTP yet, reach out to your account manager before following the instructions below.

Connecting to the Rokt SFTP

Establishing a connection from a host computer (e.g., your laptop) to a secure FTP server requires third-party client software. This tutorial suggests the popular and free client FileZilla which is available for Windows, Mac, and Linux operating systems.

1. In your browser, navigate to https://filezilla-project.org/ and click Download FileZilla Client.
2. Install FileZilla on your computer. If you already have FileZilla installed, ensure you are running the latest version.
3. Reach out to your Rokt Account Manager to request access to the Rokt SFTP. Once you've been granted access, you should receive an email from Rokt with the subject "You've been granted access to Rokt's SFTP server."
4. Download the attached file and unzip the encrypted file using the password provided in a second email "Email for password for file with instructions."
5. The encrypted file you have just unzipped contains a .pem file which is your key file to access Rokt's SFTP folder.

note

The following steps are the same for Windows, Mac, and Linux operating systems and are based on the latest version of FileZilla.

6. Open FileZilla and navigate to File > Site Manager

7. On the left, click New Site and fill in the following:

• Protocol: SFTP – SSH File Transfer Protocol

• Host: ftp.rokt.com

• Port: 22

• Key file: Browse to your local key file (.pem) and select it from your local drive (see image below).

  

8. Click Connect. You should be connected and able see your accessible folders to upload files.

File path and requirements

Files containing conversion events should be placed within the following file path:

File path	Purpose
/upload/conversions	Upload conversion data to the Rokt platform

A few additional notes:

• Uploaded files are automatically deleted from the folder once processed by the system.
• We recommend testing your integration using a sample file prepared using the required files format.

Required file format

Files uploaded to the SFTP server must meet the following standards in order to be processed correctly in the Rokt data platform.

• File format must be .csv or .txt
• Charset UTF-8 (UTF-16 or UTF-32 with an appropriate byte-order mark)
• The list of email addresses must be formatted:
  • In a single column
  • Without a column head
• Email addresses can be either plain text or hashed
• If hashing email addresses, please ensure that they:
  • Use SHA256 hash algorithm
  • Are lowercase and trimmed (white-space removed) before hashing takes place
  • Are all hashed in the same format—do not mix plain and hashed email addresses per file (emails must be all plain, or all SHA256)

Any file not matching the above format will be rejected by Rokt’s system.

Temporary Files

Temporary 'staging' files can be uploaded. Any files named with a "." prefix will be treated as temporary files and not be processed until they are renamed with no "." prefix.