Send Criteo Ads data to Databricks
Move Criteo statistics, placements and attributed transactions into Databricks with OWOX Data Marts: one table per endpoint, a readable schema, a scheduled refresh. Check the sales Criteo credits to itself against your own orders.
Criteo AdsConnectedPlacement Catego…PlacementsStatisticsTransactions
DatabricksClicksAdver…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 in Databricks
Criteo reports the sales and revenue it credits to itself, counted inside post-click and post-view windows. Those are Criteo's claims. Load your own orders and website touch points into the same warehouse and you can check them against what the spend returned.
- Compare the sales Criteo reports with your own orders
- Match each attributed transaction to your order by its id
- Put Criteo cost beside Google and Facebook spend
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 choose what to load
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
Facebook AdsCriteo Ads
Microsoft AdsAuthorizeConnectedEndpointStatisticsPlacement Categor…PlacementsTransactionsStatisticsDayAdvertiserCostDisplaysClicksSalesPc30dRevenueGeneratedPc30dStep 2: Load Criteo Ads into Databricks tables
The catalog defaults to main, and the schema and table are pre-filled; change any of them. Run it and the first load lands in your own Databricks workspace.
- Statistics go to a table such as criteo_ads_statistics
- Rows break down by advertiser, campaign, adset, ad and day
DestinationCatalogmainSchemacriteo_adsTablestatisticsRunTablemain.criteo_ads.statisticsStep 3: Open the output schema in plain words
The first run gives you the output schema: every field with an alias and 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
- Teammates can query the table without the API reference
main.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. In SQL 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: Refresh on a schedule and backfill the history
Set it once. A scheduled refresh keeps the Databricks tables current, and a manual run loads a past period of your choice.
- Each incremental run reloads today plus a lookback window you set
- Backfill a custom start and end date
Step 6: Reuse the Databricks tables in every tool
One set of tables feeds your model, , , assistants like Claude and ChatGPT and 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.40.0Connecting a plan from Google Sheets takes fewer guesses
- 0.39.0Reload a year of history in one backfill, not twelve
- 0.39.0Long Facebook Ads imports no longer fail on a corrupted response
- 0.38.0Shopify connector: more orders fields, including line-item discounts
- 0.37.0Short links resolve only on known short link services and domains you allow
Why OWOX for Criteo Ads in Databricks
Notebooks over the Criteo API and generic ETL tools get statistics in. OWOX also keeps them in your tables, readable and ready to model.
- You own the data. It lands in your own Databricks workspace, in tables you control.
- Criteo's sales beside yours. Attributed transactions, with the click or display behind each, load as a table you match to your orders.
- Windows spelled out. Placement fields state their window, such as 30-day post-click or 1-day post-view.
- Joined by advertiser and adset ids. The tables arrive ready to meet web analytics and your order data.
- Maintained for you. No jobs to repair 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.
Schedule in person meeting at Data Outpost San Francisco
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.