Authenticate to the Criteo API using the client_credentials OAuth 2.0 flow to obtain a bearer token; use the token endpoint at api.criteo.com/oauth2/token.
Create or identify the catalog (dataset) in Criteo's system; for large catalogs (over one million products), use the Product Importer API for faster, more granular ingestion rather than file-based feeds.
Submit the product feed via the appropriate endpoint, including required fields: product ID, title, description, price, image_link, availability, and GTIN/MPN where applicable.
Schedule the feed import to run at least once daily to keep product availability and price data current; stale prices or out-of-stock items in the feed will still be served until the feed is refreshed.
Monitor the import job status and check the error report for rejected products; common rejection reasons include missing required fields and images that fail Criteo's aspect ratio requirements.
Once the catalog is approved and populated, associate it with your retargeting campaign in Campaign Manager or via the API's campaign-catalog linkage endpoint.
Known gotchas
The Product Importer API and the file-based feed ingest are distinct paths with different latency characteristics; the file feed is limited to roughly one ingest per day, while the Importer API supports multiple daily syncs for high-velocity catalogs.
Criteo's current Marketing Solutions API version is versioned in the URL path (e.g., /2025-04/); always pin to a specific version in your integration and review the changelog before upgrading to avoid breaking changes.
Feed products are not immediately available for serving after upload; Criteo processes and validates the catalog before it is eligible for dynamic ad rendering, which can take several hours on the first submission.
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