Audiences give the ability to advertisers to define subsets of retailers visitors to be targeted in their campaigns.Audiences are built of one or multiple audience segments that can be combined using logical Algebra Nodes to define target campaigns’ audiences.
Note on Audience ComputationAudience updates are processed daily at 0h UTC and 12h UTC and can take around 5 hours to reflect on a live campaign. This is important for audiences that are frequently updated as changes should be ready for processing prior to these two times.
Partial ApprovalsBulk operations (create, update, delete) use a partial approval model. Even if some items in the request fail, the response will return 200 OK. Any failed items will be listed in the warnings section of the response with an error code and details.Examples of possible warning codes:
audience-not-found → Audience is not found.
name-must-be-unique → Audience name must be unique.
name-must-not-be-empty → Audience name property must not be empty.
This list is not exhaustive. Additional warnings may be returned depending on the request context.
AccountID associated with the Audience, generated internally by Criteo
Accepted values: string of int64
Writeable? N / Nullable? N
retailerId*
string
RetailerID, associated with the Audience Segment, generated internally by Criteo
Accepted values: string of int64
Writeable? N / Nullable? N
algebra
object
Algebra node with the definition of how the different audience segments are combined together to create the audience, using logical operatorsand,orandnot
Writeable (Y/N): Indicates if the field can be modified in requests.
Nullable (Y/N): Indicates if the field can accept null/empty values.
Primary Key: A unique, immutable identifier of the entity, generated internally by Criteo. Primary keys are typically ID fields (e.g., retailerId, campaignId, lineItemId) and are usually required in the URL path.
This endpoint returns a list of audiences that match the provided filters. If present, the filters are AND’ed together when applied. You can search audiences by audience IDs, retailer IDs and/or segment IDs.Results are paginated using offset and limit query parameters; if omitted, defaults to 0 and 500, respectively. See API Response.Sample Request: searching by Retailer ID only