Send Criteo Ads reports to Google Chat
Load Criteo Ads into your data warehouse first, link it to the rest of your data with SQL keys, then post retargeting cost per campaign where the performance team already talks. The message comes from your source of truth, not from an API call that can break.
The performance team discusses campaigns in Google Chat, but the Criteo Ads figures there come straight from the ad account.
Paste this into your AI assistant. It loads Criteo Ads into your data warehouse with OWOX Data Marts and posts retargeting cost per campaign to Google Chat from that Data Mart 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/criteo-ads-insights-to-google-chat.md. The task: post retargeting cost per campaign from my Criteo Ads Data Mart to the performance team's Google Chat space every Monday, with a short analysis of the week under the report. Tag the links you give me with utm_campaign=ai-task and utm_term=data-foundation. 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 Chat
Criteo Ads reports what retargeting cost and which orders it claims, not what your shop booked. A message built straight from the source puts the source's own numbers in the space and does not tie them to the rest of the business reliably, at scale or business-ready, so the join happens in a warehouse first.
- Criteo Ads counts the orders it takes credit for, and nothing in the report checks them against yours
- The data analyst links the tables by SQL keys and controls what a message may say
- The space reads one scheduled message instead of several tabs and an export
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 reports to Google Chat
Add an incoming webhook in the Chat space (Apps & integrations, Add webhooks), paste its URL into a Google Chat destination in OWOX, and attach a report of the Criteo Ads Data Mart. The message is a Markdown template.
- The message is a card with the subject, the Data Mart name, your text and a link back to the report
- The table carries Day, Campaign, AdvertiserCost and Displays
- Tables arrive as monospace blocks, and a long report is split into numbered parts
Step 4: Add a short analysis under the Criteo Ads report in Chat
Write the reading under the table in the template, or let an Insight on the same Data Mart write it. Then add a trigger on the Triggers tab: OWOX runs the Data Mart first and checks the sending condition.
- Send always, or only when the result is not empty, so a quiet week stays quiet
- The reading comes from the report's fields and adds no cause the data does not show
- One space can receive several reports, each with its own trigger
Step 5: Reuse Criteo Ads inside OWOX MCP
The Data Mart behind your Chat message also 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
- Change the Criteo Ads report once and the next Chat message reads the change
- 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.39.0Reload a year of history in one backfill, not twelve
- 0.37.0Clearer connector errors, and custom connectors that handle more APIs
- 0.36.0Start a connector run without expanding the Input Source card
Why OWOX for Criteo Ads in Google Chat
Hand-built bots and webhook scripts post numbers into a space. OWOX also keeps the data yours, linked and ready to model.
- You own the data. Criteo Ads lands in your own data warehouse, in tables you control.
- Retargeting in the thread. Campaign cost lands in the space beside the other channels, so a Criteo Ads question starts from the same table.
- The webhook stays simple. Paste the space's webhook URL once; it is stored write-only and several destinations can share it.
- Same numbers everywhere. The Criteo Ads Data Mart behind the message also feeds your reports and your AI assistant.
- Maintained for you. No bot code to fix when Criteo Ads changes its API.
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.

