Last updated

Import conversions via file transfer

import SFTPSnippet from '../../../../snippets/_rokt-sftp-setup.md';

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

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, for example, from HighTouch's SFTP integration.

Any files named with a "." prefix will be treated as temporary files and not be processed.