Important Notice: for optimal security and privacy, Adikteev recommends that customers use the Audiences API service rather than Amazon S3 to share their audiences.

This guide explains how to format your audience lists and organize your files in Amazon S3 for seamless integration with Adikteev DSP. By following these steps, your lists will be processed correctly and will always remain up-to-date for effective targeting.

To qualify for this feature, customers must meet a minimum budget threshold.

Credentials

First, ask your Adikteev Account Manager to provide you credentials to upload audiences to Adikteev using Amazon S3. These credentials are made of an access key and a secret key.

To ensure secure and efficient management of audience lists, all audiences must be stored within Adikteev’s Amazon S3 buckets rather than client-owned cloud storage. This centralized approach simplifies access permissions and ensures a streamlined workflow.

How to organize your audiences in Amazon S3

All audience lists must be stored in Adikteev’s designated Amazon S3 folder:

Base S3 Path

s3://ak-audiences/your-company-name/

Within your company folder, organize audience lists by app and platform.

Recommended Folder Structure

Each app has its own folder, using the app name as the identifier. Inside each app folder, upload the audiences for both Android and iOS platforms in a dedicated subfolder.

Example of recommended structure:

s3://ak-audiences/your-company-name/

── app-name-1/

──── android/

──── ios/

── app-name-2/

──── android/

──── ios/

Audience files format

All audience lists must meet the following format requirements:

File Type: CSV format only (.csv extension mandatory).

Column Structure: Each file must contain only one column with raw device IDs (no header).

Supported device ID Types:

• IDFA (must be UPPERCASE)
• IDFV (must be UPPERCASE)
• GAID (must be lowercase)

🚫 Do not mix different device ID types in the same file

🚫 Do not hash device IDs

🚫 Do not wrap device IDs in simple or double quotes

Audience files naming convention

To ensure your audiences are correctly identified, please use the following convention for filenames:

appName_platform_audienceName_deviceIdType.csv

• appName is the name of your app
• platform is either "android" or "ios"
• audienceName is a self-explanatory audience identifier (e.g. payers, NPU, excluded-users,...)
• deviceIdType is the type of device ID in the file (IDFA, IDFV or GAID)

Examples:

• my-awesome-game_android_lapsed-payers_gaid.csv
• my-awesome-game_ios_excluded-users_idfa.csv

🚫 Don't add filename suffixes like timestamps or version numbers (e.g., _20240210.csv, _v1.csv)

✅ Always overwrite the existing file with latest content when refreshing an audience list, so that Adikteev can automatically process your list refresh

Best practices for sharing audiences by Amazon S3

✅ Always include app name, platform, audience name and device ID type in the filename

✅ Always update the same file when updating an audience

✅ Only create new files when sharing completely new audiences

✅ Regularly update audience files to reflect recent user activity and campaign needs

🚫 Placing all files in the base company folder or without following naming convention

🚫 Putting timestamps or dates in filenames to notify an update

🚫 Uploading files with formatting issues: missing ".csv" extension, multiple columns, empty rows,...

🚫 Uploading audiences with very generic filenames like "device_list.csv" or "audience.csv"