Collect Criteo Ads data in Google BigQuery
Load Criteo statistics, placements and attributed transactions into your own BigQuery tables with OWOX Data Marts: one table per endpoint, a business-friendly schema, refreshed on a schedule. Set the sales Criteo claims beside your own orders.
Criteo AdsConnectedPlacement Catego…PlacementsStatisticsTransactions
Google BigQueryClicksAdver…Categ…Daily 09:00Criteo 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 join Criteo Ads with your orders and web analytics
Criteo reports the sales and revenue it credits to itself, counted within post-click and post-view windows. Those are Criteo's claims. Beside your own orders and website touch points in one warehouse, you can check them and see what the spend really returned.
- Compare the sales Criteo reports with the orders in your own tables
- Match each attributed transaction to your order by its id
- Put Criteo cost next to Google and Facebook spend in one table
Criteo AdsRetargeting spendYour data warehouseAdTouch pointOrderJoined by idAd displayed or clickedOrder laterOne query sets Criteo's sale beside yours.Step 1: Connect Criteo Ads and pick the fields
Create a Data Mart, choose Criteo Ads as the source, enter your Advertiser ID, Client ID and Client Secret, and tick only the fields you need.
- 4 endpoints and 196 fields to choose from
- Statistics alone has 156 fields: cost, displays, clicks, sales and revenue by attribution window
Google AdsCriteo Ads
Facebook AdsAuthorizeConnectedEndpointStatisticsPlacement Categor…PlacementsTransactionsStatisticsDayAdvertiserCostDisplaysClicksSalesPc30dRevenueGeneratedPc30dStep 2: Load Criteo Ads into a BigQuery table
The dataset and table in your storage are pre-filled, and you can change them. Run it and the first load lands in your own BigQuery project.
- Statistics go to a table such as criteo_ads_statistics
- Rows break down by advertiser, campaign, adset, ad and day
DestinationDatasetcriteo_adsTablestatisticsRunTablecriteo_ads.statisticsStep 3: Get a business-friendly output schema
After the first run you get the output schema: every field with a readable description, not an API identifier. Your quality checks can read it too.
- Placements fields state their window, such as 30-day post-click or 1-day post-view
- Anyone on the team can read the table
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: Keep the Criteo Ads tables linked
Statistics, placements and transactions stay separate tables, joined by advertiser and adset ids. Together they become one Criteo Ads model.
- Transactions carry transactionId and amount, ready to match to your own orders
- Transactions load only for periods with attributed conversions
StatisticsAdvertiserIdAdsetIdAdvertiserCostPlacementsadsetIdplacementcostTransactionsadvertiserIdtransactionIdamountStep 5: Schedule the refresh and backfill history
Set it once. A scheduled refresh keeps the tables current, and a manual backfill loads any past period.
- Each incremental run reloads today plus a lookback window you set
- Backfill a custom start and end date
Step 6: Reuse the same table everywhere
One table feeds your model, , , assistants like Claude and ChatGPT, and scheduled AI insights in Slack or email.
- Reconcile Criteo's sales with your orders once
- Every report reads the same table
Criteo AdsData MartPublished
Google Sheets
Data Studio dashboards
Claude, ChatGPT
Slack, email
- 0.43.0Parallel reads of a SQL Data Mart on Google BigQuery no longer fail with a rate limit error
- 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
- 0.39.0Reload a year of history in one backfill, not twelve
Why OWOX for Criteo Ads in BigQuery
Hand-built API scripts, a generic ETL tool or manual exports each get Criteo data out. OWOX also keeps it yours, readable and ready to model.
- You own the data. It lands in your own BigQuery project, in tables you control.
- Criteo's sales next to yours. Attributed transactions, with the click or display behind each, load as a table you can match to your orders.
- Ready for a data model. Separate tables joined by advertiser and adset ids, built to connect to web analytics and your order data.
- Maintained for you. No scripts to fix when Criteo changes its API.
- Free to self-host. The open-source OWOX Data Marts runs in your own infrastructure.
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.