Rokt Documentation
  • Documentation
  • User Guide
  • SDK
  • API
  • Third-Party Integrations
  • Help

›Custom audiences

Overview

  • Introduction

Getting started

  • Glossary

Administration

  • Account settings
  • User management
  • Billing - Rokt Acquire

    • Billing & payment for campaigns
    • Invoicing & payment for monetization
    • Financial responsibility assignment
    • Agency commission setup

    Billing - Rokt Commerce

    • Billing & payment for campaigns
    • Invoicing & Payment for monetization

Campaigns

  • Creating campaigns
  • Editing campaigns
  • Pausing campaigns
  • Campaign status guide
  • Campaigns best practices
  • Audiences

    • Creating audiences
    • Editing audiences
    • Pausing audiences
    • Bid price
    • Attribute targeting

    Creatives

    • Building creatives
    • Editing creatives
    • Pausing creatives
    • Linking creatives to audiences
    • Effective creative copywriting

    Nurture

    • Creating Nurture Journeys
    • Creating emails

    Coupons

    • Sending coupon codes
    • Adding coupon codes
    • Replacing coupon codes

    Campaign policies

    • Policy overview
    • Quality consent
    • Transparency accuracy
    • Editorial requirements
    • Prohibited content
    • Social & ethical appropriateness
    • Compliance industry codes & regulations
    • Target audiences & restricted campaign content

Transaction

    Pages

    • Pages

    Placements

    • Placements

    Controls

    • Campaign & marketplace controls
    • Brand & vertical block rules
    • Minimum Quality Score setup
    • Advertiser vertical & sub-vertical breakdown

    Audiences

    • Audience targeting

Rokt Calendar

  • Overview
  • Integration guide
  • UTM tracking

Reporting & measurement

    Performance - Rokt Acquire

    • Conversion attribution
    • Campaign performance graphs

    Performance - Rokt Commerce

    • Transactions Dashboard

Data integrations

    Events

    • Import via Rokt SFTP
    • Import via measurement providers
    • Manual import

    Referrals

    • Overview
    • Export via API
    • Export via Rokt SFTP
    • Export via client SFTP
    • Export via email
    • Export via Mailchimp
    • Export via Sailthru
    • Export via Zapier
    • Manual export

    Transactions

    • Overview
    • Export via API
    • Export via Rokt SFTP
    • Export via client SFTP
    • Export via email
    • Manual export

    Custom audiences

    • Overview
    • Import via Rokt SFTP
    • Import via CSV (email)
    • Import via CSV (ZIP code)
    • Import via Mailchimp
    • Import via Zapier

    Unsubscribes

    • Export via API

    Advanced guides

    • Rokt SFTP setup
    • Rokt Tracking ID for attribution
    • Tracking application installs
    • Rokt IP addresses
    • Hashing sensitive data
    • Custom field management
    • Managing templates
    • Google Tag Manager integration
Edit

Custom audience import via Rokt SFTP

Using our data management platform, Rokt can receive custom audience data at any frequency you prefer. If you’re working with Rokt as a brand, 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 listPurpose
/upload/custom-audience/include/AdvertiserDatabaseAdd a list of customers into the default AdvertiserDatabase file associated with your account.
/upload/custom-audience/exclude/AdvertiserDatabaseRemove 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 listPurpose
/upload/custom-audience/include/MyListAdd 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/MyListRemove 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 .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 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.

← OverviewImport via CSV (email) →
  • Connecting to the Rokt SFTP
  • File path and requirements
  • Required file formats
RESOURCES
DocumentationUser GuideSDKAPIIntegration PartnersHelp
COMPANY
About UsContact UsCareersEngineering Blog
Rokt Documentation
Copyright © Rokt 2021 - All Rights Reserved