Send Criteo Ads data to Google Sheets
Load Criteo Ads into your data warehouse first, link its spend and attributed orders to web analytics and deals with SQL keys, then send the answers to Google Sheets on a schedule. The sheet stays tied to your source of truth, not to a reporting API that can break.
The Criteo tab in the team's sheet is a pasted copy, and nobody knows whether its orders are your orders.
Paste this into your AI assistant. It loads Criteo Ads into your data warehouse, links spend and attributed orders to your own sales in a Data Mart, and refreshes the sheet on a schedule.
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-google-sheets.md. The task: send a weekly Google Sheets report of Criteo Ads cost, clicks and CPC by campaign, with how many of Criteo's attributed orders our shop also recorded, refreshed every Monday. 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 does not go straight to Google Sheets
A direct link gives you a copy of the Criteo reporting in a sheet. It does not show whether the orders Criteo attributes to itself are the same orders your shop and CRM count, because ad cost, website visits and deals live in different systems. A sheet is not built to join them reliably, at scale or business-ready, so the join happens in a warehouse first.
- Criteo Ads reports the sales it attributes to itself, not whether another channel claimed the same order
- The data analyst links Criteo cost, web analytics and CRM deals by SQL keys and controls the result
- Stakeholders keep the sheet they like, now tied to your source of truth
Step 1: Load Criteo Ads into your data warehouse first
Create a Data Mart with Criteo Ads as the source and choose where the data lands. It works with any popular data warehouse.
- Four endpoints and 196 fields to choose from, Statistics being the widest
- Transactions carries transactionId, the key that joins Criteo's attributed orders to yours
- Open the Criteo Ads connector for your data warehouse below
Step 2: Link Criteo Ads to web analytics and deals
In your data warehouse the model brings Criteo Ads spend next to your other ad platforms by adding it to the merged spend table, then joins web analytics sessions by a campaign key. Pick an industry to see the shape of its model.
- Criteo spend, added to the merged spend table, sits next to the other platforms
- Sessions and deals join by SQL keys, not VLOOKUP and gut feeling
- The measures, such as platform_cpa, are defined once
Step 3: Send Criteo Ads data to Google Sheets
Connect a Sheets report to the Data Mart. Aliases and field descriptions arrive as notes in the column headers, so everyone reads the same definitions.
- The sheet reads your data warehouse, not the Criteo reporting API
- Hover a header such as AdvertiserCost to see what it measures
Step 4: Refresh your Criteo Ads sheet on a schedule
Set a scheduled refresh once. Daily is the usual choice and hourly is possible when you need it.
- Every refresh is logged in Run History
- Stakeholders open a sheet that is already up to date
Step 5: Reuse Criteo Ads inside OWOX MCP
The same Data Mart works in OWOX MCP, your assistant for data. Request any report, chat with your data, then get the report in Google Sheets or Excel in one click.
- Ask in plain words; the answer comes from your data warehouse
- Define the numbers once and every report reads them
- 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 connector key is one change: Sources share reusable Credentials
- 0.41.0Reuse one Google Sheets or Google Chat key across Destinations
- 0.40.0Warnings when a Count reads a joined Data Mart
Why OWOX for Criteo Ads in Google Sheets
Hand-built API scripts and add-ons that pull straight from a Criteo account get numbers into a sheet. OWOX also keeps the data yours, linked and ready to model.
- You own the data. It lands in your own data warehouse, in tables you control.
- Criteo's orders next to yours. Statistics and Transactions land in your data warehouse, so the orders Criteo attributes to itself can be compared with the orders your shop and CRM count.
- Sheets stay in sync. Notes in the headers, a schedule you set once, no API token to fix in the sheet.
- Maintained for you. No scripts to fix when Criteo changes its API.
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.
