Updating Audiences via S3
In this article, you learn how to update audiences you onboarded or activated through digitalAudience.
Prerequisites
You have onboarded your data through Audience API. Onboarding your data this way generates an audience id, which will be used within the folder name.

Update Audience Data with S3
First, you need to receive access to a storage:
If the storage is from digitalAudience:
If it is a digitalAudience S3 bucket, request an access key, secret key, bucket name and a region name
If it is a digitalAudience SFTP, request a server name, port number, and a user name
If the storage is from the Advertiser:
If it is a S3 bucket from the Advertiser, provide digitalAudience with an access key, secret key, bucket name and a region name
If it is an Azure Blob Storage from the Advertiser, provide digitalAudience with an accountname and an accountKey or a Shared Access (SAS) token

Then follow these steps:
Prepare a CSV file with hashed records according to the requirements outlined in the formatting guidelines.
From the Audience page in the Portal, retrieve the audience ID that needs to be updated

Specify which audience update mode you intend to use.
Create the necessary folders in your S3 bucket or SFTP. Create the root folder called 'onboard', if it doesn't exist yet.
Create the audience folder inside the onboard folder with the following format;
Create the audience update mode folder, opt-in, opt-out and/or replace.
An example of the resulting path would be;

Send the file to S3 or SFTP into the intended folder
In digitalAudience Portal, the audience is updated the next day. On a platform, the time needed for a segment to update varies per platform. The average time is two days.
We recommend to limit updates for one audience to one file per day.
Last updated