Our data management platform provides the ability for Rokt to receive custom audience data at any frequency you prefer. If you’re working with Rokt as an advertiser, these lists can be used in your campaigns to either target or suppress certain users from seeing your offers. If you’re working with Rokt as a partner these lists can be used to determine exactly which users will see the Rokt UX on your site.
One method of delivering custom audience data to Rokt is through the use of the Rokt-hosted SFTP.
Connecting to the Rokt SFTP
Please reference the instructions found here for setting up FileZilla and connecting to the Rokt Secure FTP.
File Path and Requirements
For the majority of integrations, custom audience files should be placed within the following file path:
|File Path using Default List||Purpose|
|/upload/custom-audience/include/AdvertiserDatabase||Upload a list of customers into the default AdvertiserDatabase file associated with your account.|
|/upload/custom-audience/exclude/AdvertiserDatabase||Remove a list of customers from the default AdvertiserDatabase file associated with your account.|
If you need to upload and maintain several different custom audience lists within a single account (for example, you might have one list for users you’d like to use in campaign targeting, and a separate list for users you’d like to suppress from seeing your campaigns), you can create a specific custom audience list as follows:
|File Path using a Specific List||Purpose|
|/upload/custom-audience/include/MyList||Upload a list of customers into a non-default custom audience list named MyList.|
MyList is a sub-folder you would create within the "include" folder as shown in the file path.
|/upload/custom-audience/exclude/MyList||Remove a list of customers from a non-default custom audience list named MyList.|
MyList is a sub-folder you would create within the "exclude" folder as shown in the file path.
Note: Custom Audience files will be automatically deleted from this folder as soon as they are processed by the Rokt system
Required File Formats
Files uploaded to the secure FTP server must meet the following standards in order to be processed correctly in the Rokt data platform.
- File format must be
- Charset UTF-8 (UTF-16 or UTF-32 with an appropriate byte-order mark).
- Email addresses must be
- in one single column
- without a column head
- Email addresses can either be plain text or hashed
- If you provide hashed email addresses please ensure that they meet the following criteria:
- We accept MD5 or SHA256 hash algorithms
Ensure that all email addresses are lowercased and trimmed (white-space removed) before hashing them.
Do not mix plain and hashed email addresses per file (they must be either all plain, all MD5 or all SHA256).
Any file not matching the above format will be rejected by Rokt’s system and not processed accordingly.