Manage campaigns via Criteo Marketing Solutions API
domain: developers.criteo.com/marketing-solutions · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate via Criteo's OAuth 2.0 client credentials flow: POST to https://api.criteo.com/oauth2/token with client_id and client_secret to obtain an access token.
Include Authorization: Bearer YOUR_TOKEN and Content-Type: application/json headers on all API requests; also include the API version in the URL path.
POST to https://api.criteo.com/2024-01/advertisers/{ADVERTISER_ID}/campaigns (using the current API version date in the path) with name, budget type, and spend limit settings.
Create an ad set under the campaign by POSTing to the adsets endpoint with campaignId, scheduling, budget, targeting (geo, device, audience), and bid strategy.
Create ads by associating product catalog data or banners with the ad set via the ads endpoint.
Use GET on the respective resources to verify creation and retrieve IDs for downstream operations.
Known gotchas
The Criteo API uses a date-based versioning scheme in the URL path (e.g. /2024-01/); check the developer portal for the current supported version, as old versions are periodically sunset.
Criteo's ad serving is catalog-driven for retargeting; ad sets must be linked to a valid product catalog or dynamic audience — missing this linkage results in no delivery.
OAuth tokens have a short expiry (typically 1 hour); implement token refresh logic using the client credentials flow before each batch of API calls rather than caching tokens long-term.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?