Authenticate to the Criteo API using the client credentials OAuth 2.0 flow against the Criteo identity endpoint to obtain a bearer token
POST to the retail media audiences endpoint to create an audience, specifying the account ID (brand or retailer account), name, description, and audience type (e.g. customer file or behavioral segment)
For customer file audiences, prepare a list of hashed emails (SHA-256, lowercase normalized) and POST them to the audience users endpoint using the returned audience ID, in batches respecting the API's size limits
Alternatively for behavioral segments, define the segment rules (e.g. viewed or purchased specific product categories in the past N days) using the segment query parameters on the audience creation request
Retrieve the audience status and estimated reach using a GET on the audience ID; wait for status to transition from PROCESSING to ACTIVE before targeting
Associate the audience with a retail media line item by including the audience ID in the targeting configuration when creating or updating a campaign line item via the campaigns endpoint
Known gotchas
Criteo retail media audiences are scoped to the specific retailer network; an audience created for Retailer A cannot be reused for targeting on Retailer B without re-creating it in that context
Customer file upload match rates depend on how well the retailer's email list overlaps with Criteo's shopper identity graph; very low match rates do not surface as API errors but will result in small, underperforming audiences
Behavioral segment audiences require sufficient historical event data in the Criteo network for the retailer; newly onboarded retailers with limited event history may see empty or very small segment sizes
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp