Using our data management platform, Rokt can 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 customers from seeing your offers. If you’re working with Rokt as a partner these lists can be used to determine what customers see the Rokt experience on your site.
One method of delivering custom audience data to Rokt is the Rokt-hosted SFTP.
Connecting to the Rokt SFTP
Reference the instructions for setting up FileZilla and connecting to the Rokt SFTP.
File path and requirements
For the majority of integrations, custom audience files should be placed within the following file path:
|File path using a default list||Purpose|
|/upload/custom-audience/include/AdvertiserDatabase||Add 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 customers you’d like to use in campaign targeting, and a separate list for customers 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||Add 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 are automatically deleted from this folder as soon as they are processed by Rokt.
Required file formats
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
- 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 MD5 or SHA256 hash algorithms
- 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, all MD5, or all SHA256)
Any file not matching the above format will be rejected by Rokt’s system.