Skip to content
Book a demoStart free
Connectors

Criteo connector

Set up the Criteo connector in Kaivo: authentication, configuration, the 2 BigQuery tables it syncs, and answers to common questions.

Criteo connector pricing, tier and credits on kaivo.io

Kaivo is a fully managed data platform that syncs your Criteo data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your marketing and sales data instead of moving it.

Sync your Criteo advertising data into BigQuery with Kaivo to track ad spend and performance alongside your other channels.

CategoryMarketing & Sales
AuthenticationAPI key
SetupSelf-service
  1. Sign up for Kaivo and create a workspace.
  2. Connect your Criteo account.
  3. Choose which tables to sync.
  4. Wait for the initial sync to finish.
  5. Query your data in BigQuery or your favourite AI or BI tool.

Authenticate with your Criteo credentials. You provide:

Field Description
OAuth Client ID
OAuth Client Secret

Prerequisites

Criteo uses OAuth with client credentials, so you need your own Criteo Marketing Solutions developer application:

  1. Sign in to the Criteo Developer Portal and create an app.
  2. Note the Client ID and Client Secret from the app settings.

Then enter those values below.

Need help? Reach our team via the chat in the bottom-right corner.

When you set up the connector, you provide:

Field Description
Currency
Currency to be used on the report (e.g. EUR, USD).

| | Start Date |

Any data before this date will not be fetched.

|

Kaivo syncs 2 tables from Criteo into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.

ad_spend_daily (9 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
day STRING
campaign STRING
currency STRING
advertiser STRING
campaign_id STRING
advertiser_id STRING
advertiser_cost STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
adsets (26 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
type STRING
id STRING
attributes__name STRING
attributes__advertiser_id STRING
attributes__dataset_id STRING
attributes__campaign_id STRING
attributes__destination_environment STRING
attributes__objective STRING
attributes__schedule__start_date__value STRING
attributes__schedule__activation_status STRING
attributes__schedule__delivery_status STRING
attributes__bidding__bid_amount FLOAT64
attributes__bidding__cost_controller STRING
attributes__targeting__geo_location__countries__value__operand STRING
attributes__targeting__geo_location__subdivisions__value__operand STRING
attributes__targeting__frequency_capping__value__frequency STRING
attributes__targeting__frequency_capping__value__maximum_impressions FLOAT64
attributes__budget__budget_strategy STRING
attributes__budget__budget_renewal STRING
attributes__budget__budget_delivery_smoothing STRING
attributes__budget__budget_delivery_week STRING
attributes__budget__budget_amount FLOAT64
attributes__media_type STRING
attributes__attribution_configuration__attribution_method STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: adsets__attributes__targeting__delivery_limitations__environments

Section titled “Subtable: adsets__attributes__targeting__delivery_limitations__environments”
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
value STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: adsets__attributes__targeting__delivery_limitations__devices

Section titled “Subtable: adsets__attributes__targeting__delivery_limitations__devices”
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
value STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: adsets__attributes__targeting__delivery_limitations__operating_systems

Section titled “Subtable: adsets__attributes__targeting__delivery_limitations__operating_systems”
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
value STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: adsets__attributes__targeting__geo_location__countries__value__values

Section titled “Subtable: adsets__attributes__targeting__geo_location__countries__value__values”
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
value STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: adsets__attributes__targeting__geo_location__subdivisions__value__values

Section titled “Subtable: adsets__attributes__targeting__geo_location__subdivisions__value__values”
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
value STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Criteo supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won’t get duplicate rows.

How long does the initial sync take for Criteo?

Section titled “How long does the initial sync take for Criteo?”

It depends on how much history is in your Criteo account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they’re much faster.

Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don’t select are never copied to your warehouse.

What happens when Criteo’s schema changes?

Section titled “What happens when Criteo’s schema changes?”

New fields are never added automatically. You choose which fields to sync, so data you haven’t selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table’s sync mode: full-refresh tables always match what’s currently in Criteo, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.

How do I handle GDPR or data deletion requests?

Section titled “How do I handle GDPR or data deletion requests?”

Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in Criteo instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the Criteo connector in Kaivo and all of its synced data is deleted with it.

Use ad_spend_daily to compare Criteo cost and results with your other ad platforms.

Join adsets with spend to see which ad sets drive the best return.

Use ad_spend_daily to catch overspend or underspend early.

Once Criteo data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here’s how the most common destinations work with Criteo data.

Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →

Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →

Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →

The premium analytics standard, with native BigQuery integration. Setup guide →

Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →

Connect via Power Query’s BigQuery connector. Setup guide →

Open-source BI tool with strong BigQuery support. Setup guide →

See our pricing page for Criteo connector pricing and plan details.