Agent context
Criteo (Marketing API) models
2 SQL models that turn the raw Criteo (Marketing API) tables into the reports people ask about. Deploy them in Weld and your agent queries the definitions behind every number.
How the set is built
- 5Raw tables
- 5Staging
- 3Core
- 2Analytics
Staging cleans each raw table once, core holds the logic, and analytics is the table dashboards and agents read.
- Ad performance dailyDaily delivery and sales results per ad, the Criteo Commerce Growth ad report by day.grain: date_day x campaign_id x adset_id x ad_id · 5 raw tables
- Campaign performance dailyDaily campaign performance with the rates the Criteo UI shows: CTR, CPC, CPM, cost per order (CPO), conversion rate and ROAS.grain: date_day x account_id x campaign_id · 5 raw tables
- Weld or dbt
- The same SQL in both dialects. Sync the folder with GitHub Sync, or copy the dbt models into your project.
- Check before you rely on it
- Reconcile a month against Criteo (Marketing API)'s own reports first. Each model's notes say what the synced data can and can't support.
Connect Criteo (Marketing API).
Your agents start with context.
Sync Criteo (Marketing API) to your warehouse, deploy these models, and query them from Claude, Cursor or ChatGPT over MCP. Free for 14 days, no credit card.