Collect Criteo Ads data in Snowflake
Load Criteo statistics, placements and attributed transactions into Snowflake with OWOX Data Marts: a table per endpoint, a readable schema, a refresh on your schedule. Check the sales Criteo claims against your own orders.
SnowflakeClicksAdver…Categ…Daily 09:00Criteo's sales figures never get tested in Snowflake, because the retargeting data stays in the ad account.
Paste this into your AI assistant. It sets up a Criteo Ads Data Mart on your Snowflake storage, loading statistics and attributed transactions into tables on your schedule, ready to join with your orders.
The prompt
Read https://www.owox.com/ai-agent-setup.md and follow it to set up OWOX Data Marts for me, starting from /connectors/free-criteo-ads-connector-to-snowflake.md. The task: load Criteo Ads statistics and attributed transactions into Snowflake every day and give me a query that compares the revenue Criteo claims with our own order revenue, by week and campaign. Tag the links you give me with utm_campaign=ai-task and utm_term=m4. Use what you know about my context and goals
Criteo Ads Endpoints
4 Criteo Ads endpoints you can import. Each lands in its own table in your data warehouse.
Placement Categories
Performance metrics broken down by content category.
8 fieldsTime seriesPlacements
Performance metrics broken down by publisher placement.
21 fieldsTime seriesStatistics
Statistics and metrics for Criteo advertising campaigns.
156 fieldsTime seriesTransactions
Transaction-level data with individual order details attributed to Criteo ads.
11 fieldsTime series
Why Criteo Ads belongs next to your orders in Snowflake
Criteo reports sales and revenue it credits to itself, inside post-click and post-view windows. Those are Criteo's claims. With your own orders and website touch points as tables in the same warehouse, a query can test them against what the spend returned.
- Compare Criteo's reported sales with the orders in your tables
- Match each attributed transaction to your orders by transactionId
- Put Criteo cost beside Google and Facebook spend
Your data warehouseAdVisitOrderJoined by idAd displayed or clickedOrder laterA SQL join sets Criteo's sale beside yours.Step 1: Connect Criteo Ads and choose the fields
Create a Data Mart on Snowflake and pick Criteo Ads as the source. Enter the Advertiser ID, Client ID and Client Secret, then tick the fields.
- 4 endpoints and 196 fields are available
- Statistics has 156 fields: cost, displays, clicks, and sales and revenue per attribution window
Step 2: Load Criteo Ads into a Snowflake table
Pick the Snowflake database, schema and table, pre-filled and editable. Run it and statistics land in your own account.
- Statistics get their own table
- Rows split by advertiser, campaign, adset, ad and day
DestinationDatabaseSchemacriteo_adsTablestatisticsRun
Tablecriteo_ads.statisticsStep 3: Read the output schema in plain words
Every column in the output schema carries a description in ordinary language. Your quality checks can read it too.
- Placements fields name their window, such as 30-day post-click or 1-day post-view
- A colleague can read it without the API docs
criteo_ads.statisticsOutput schemaFieldDescriptionDayThe day of the statistics data…AdvertiserCostTotal money spent on Criteo…DisplaysThe number of ad impressions…ClicksThe number of clicks driven by…SalesPc30dThe number of transactions or…RevenueGeneratedPc30dThe amount of money generated…Step 4: Join the Criteo Ads tables in SQL
Statistics, placements and transactions are separate Snowflake tables that share advertiser and adset ids, so you can summarise each by advertiser, adset and day inside one Criteo Ads model.
- Transactions hold transactionId and amount, ready to match your orders
- Transactions load only for periods that have attributed conversions
Step 5: Schedule the load and backfill history
Set the cadence once and a scheduled refresh reloads the tables in Snowflake. Manual runs load past periods.
- Each incremental run reloads today plus a lookback you set
- Backfill a custom date range
Step 6: Use the same Snowflake tables in every report
, , assistants such as Claude and ChatGPT, AI insights and your model read the same tables.
- Settle Criteo's sales against your orders in one place
- The same numbers in every report
- 0.44.0Connector Data Marts set up through MCP no longer fail their first run because of the table path
- 0.44.0Backfill a catalog for any period in one run, and follow a long backfill as parts of one operation
- 0.41.0Rotating a warehouse key is one change: Storages share reusable Credentials
- 0.41.0Shared SQL logic stays in one place: build a Data Mart on top of another
- 0.41.0Rotating a connector key is one change: Sources share reusable Credentials
Why OWOX for Criteo Ads in Snowflake
API scripts and manual exports get Criteo numbers out. OWOX stores them as Snowflake tables you own, so they can sit beside your orders.
- Yours in Snowflake. The tables live in your account under your roles.
- Criteo's sales beside yours. Attributed transactions load as a table you can match to your orders, with the click or display behind each.
- Ready to model. Transactions match your orders by transactionId; statistics and placements summarise by advertiser and adset.
- Looked after for you. When Criteo changes its API, no script of yours needs fixing.
- Free when self-hosted. The open-source OWOX Data Marts runs on your own infrastructure at no licence cost.
The Data Partner You Can Trust
users
166K Source: Internal OWOX data as of 2026-11-15
Executives and data analysts across 20+ industries
Customers
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.