Skip to main content
Criteo is a global technology company that specializes in digital performance marketing. Their platform enables advertisers to run personalized retargeting campaigns across the web, driving conversions and maximizing return on ad spend (ROAS). Criteo’s AI-powered solutions help businesses reach customers at the right moment with relevant product recommendations.

​
Configuring Criteo as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Criteo option from the list of connectors. Click Next and you’ll be prompted to add your access.

​
1. Add account access

You’ll need to provide your Criteo API credentials to authenticate.
To connect Criteo to Nekt, you’ll need to create an API application in the Criteo Developer Portal and obtain your Client ID and Client Secret. Follow these steps:

​
Prerequisites

Before you begin, ensure you have:
  • A Criteo account with advertiser access
  • Access to the Criteo Developer Portal
  • A Partner Account and Organization set up in Criteo

​
Step-by-Step Guide

1

Access the Criteo Developer Portal

Go to developers.criteo.com and sign in with your Criteo account credentials. If you don’t have access yet, you’ll need to request it from your Criteo account manager.
2

Navigate to My Apps

Once logged in, navigate to the My Apps page. This is where you’ll create and manage your Criteo API applications.
3

Create a New Application

Click the Create a New App button in the top right corner of the page. This will start the application creation wizard.
4

Configure App Details

Provide the following information for your application:
  • App Name: Give your application a clear, identifiable name (e.g., “Nekt Data Integration”)
  • Description: (Optional) Add a description of the application’s purpose
  • App Image: (Optional) Upload an image for your application
API applications cannot be deleted once created. Make sure to use a clear and identifiable name, as this helps Criteo support teams assist you more effectively.
5

Select Authentication Method

Choose Client Credentials as the authentication method. This is the recommended method for server-to-server integrations like Nekt.
Client Credentials authentication is ideal for automated data pipelines because it doesn’t require user interaction for each API call. It uses your Client ID and Client Secret to generate access tokens automatically.
6

Select the Service

Choose the Criteo service your application will interact with:
  • Select C-Growth and Marketing Solutions for accessing campaign statistics and marketing data
7

Configure Domain Permissions

Select the domains (permissions) your application needs. For Nekt integration, you’ll need at minimum:
  • Analytics: Set to Read - Required to generate campaign statistics reports
You may also enable:
  • Campaigns: Set to Read if you want to access campaign configuration data
  • Audiences: Set to Read if you want to access audience data
After selecting the appropriate domains, click Activate App.
Once activated, you cannot change the app name, description, image, or domain scopes. Review your selections carefully before activating.
8

Retrieve Your Credentials

After activation, you’ll be redirected to your application details page. Here you’ll find:
  • Client ID: Copy this value for the Nekt configuration
  • Client Secret: Click to reveal and copy this value
Store your Client Secret securely. You won’t be able to view it again after leaving this page. If you lose it, you’ll need to generate a new one.

​
Authorization Request (If Required)

If you’re integrating on behalf of other advertisers (as an agency or partner), you may need to send authorization requests to your clients. They will need to approve access before you can pull their data.
For more detailed information about Criteo’s API setup, visit the official Criteo API Documentation.
The following configurations are required:
  • Client ID: The client ID from your Criteo API application. See the Obtaining Your Criteo API Credentials section above for detailed instructions.
  • Client Secret: The client secret from your Criteo API application. See the Obtaining Your Criteo API Credentials section above for detailed instructions.
  • Currency: The currency code for reporting (e.g., USD, EUR, BRL). This determines how monetary values are displayed in your reports.
  • Timezone: The timezone for organizing your data. This affects how daily aggregations are calculated.
  • Start Date: The earliest date from which records will be synced. Records from this date onward will be extracted.
Once you’re done, click Next.

​
2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

​
3. Configure data streams

Customize how you want your data to appear in your catalog. Select a name for each table (which will contain the fetched data) and the type of sync.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix and make this process faster!
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
    • Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.
Once you are done configuring, click Next.

​
4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can determine when to execute a full sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while. Once you are ready, click Next to finalize the setup.

​
5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

​
Streams and Fields

Below you’ll find all available data streams from Criteo and their corresponding fields:
Daily performance report for campaigns, including impressions, clicks, conversions, revenue, and ROAS metrics with various attribution windows.Dimensions:
  • Day - Date of the statistics
  • AdvertiserId - Unique identifier of the advertiser
  • Advertiser - Name of the advertiser
  • AdsetId - Unique identifier of the ad set
  • Adset - Name of the ad set
  • CategoryId - Unique identifier of the category
  • Category - Name of the category
  • Device - Device type (Desktop, Mobile, Tablet)
  • Os - Operating system
  • Currency - Currency code for monetary values
Basic Performance Metrics:
  • Clicks - Number of clicks
  • Displays - Number of ad impressions
  • ViewableDisplays - Number of viewable ad impressions
  • NonViewableDisplays - Number of non-viewable ad impressions
  • UntrackableDisplays - Number of untrackable displays
  • AdvertiserCost - Total advertising spend
  • QualifiedVisits - Number of qualified visits
  • Visits - Total number of visits
  • CostPerVisit - Cost per visit
  • BounceRate - Bounce rate (0-1)
  • PotentialDisplays - Number of potential display opportunities
  • OverallCompetitionWin - Auction win rate
Sales Metrics (by Attribution Window):
  • SalesClientAttribution - Sales with client-defined attribution
  • SalesAllClientAttribution - All sales with client attribution
  • SalesPc30d - Sales post-click 30 days
  • SalesAllPc30d - All sales post-click 30 days
  • SalesPv24h - Sales post-view 24 hours
  • SalesAllPv24h - All sales post-view 24 hours
  • SalesPc30dPv24h - Sales post-click 30 days / post-view 24 hours
  • SalesAllPc30dPv24h - All sales PC 30d / PV 24h
  • SalesPc1d - Sales post-click 1 day
  • SalesAllPc1d - All sales post-click 1 day
  • SalesPc7d - Sales post-click 7 days
  • SalesAllPc7d - All sales post-click 7 days
Revenue Metrics (by Attribution Window):
  • RevenueGeneratedClientAttribution - Revenue with client attribution
  • RevenueGeneratedAllClientAttribution - All revenue with client attribution
  • RevenueGeneratedPc30d - Revenue post-click 30 days
  • RevenueGeneratedAllPc30d - All revenue post-click 30 days
  • RevenueGeneratedPv24h - Revenue post-view 24 hours
  • RevenueGeneratedAllPv24h - All revenue post-view 24 hours
  • RevenueGeneratedPc30dPv24h - Revenue PC 30d / PV 24h
  • RevenueGeneratedAllPc30dPv24h - All revenue PC 30d / PV 24h
  • RevenueGeneratedPc1d - Revenue post-click 1 day
  • RevenueGeneratedAllPc1d - All revenue post-click 1 day
  • RevenueGeneratedPc7d - Revenue post-click 7 days
  • RevenueGeneratedAllPc7d - All revenue post-click 7 days
User & Reach Metrics:
  • ExposedUsers - Number of users served an ad
  • Audience - Potential users who could be served an ad
  • Reach - Share of potential users served an ad
Average Cart Metrics (by Attribution Window):
  • AverageCartClientAttribution - Average cart with client attribution
  • AverageCartAllClientAttribution - All average cart with client attribution
  • AverageCartPc30d - Average cart post-click 30 days
  • AverageCartAllPc30d - All average cart PC 30 days
  • AverageCartPv24h - Average cart post-view 24 hours
  • AverageCartAllPv24h - All average cart PV 24 hours
  • AverageCartPc30dPv24h - Average cart PC 30d / PV 24h
  • AverageCartAllPc30dPv24h - All average cart PC 30d / PV 24h
  • AverageCartPc1d - Average cart post-click 1 day
  • AverageCartAllPc1d - All average cart PC 1 day
  • AverageCartPc7d - Average cart post-click 7 days
  • AverageCartAllPc7d - All average cart PC 7 days
Rate Metrics:
  • ClickThroughRate - Click-through rate (CTR)
  • ConversionRateClientAttribution - Conversion rate with client attribution
  • ConversionRateAllClientAttribution - All conversion rate with client attribution
  • ConversionRatePc30d - Conversion rate post-click 30 days
  • ConversionRateAllPc30d - All conversion rate PC 30 days
  • ConversionRatePv24h - Conversion rate post-view 24 hours
  • ConversionRateAllPv24h - All conversion rate PV 24 hours
  • ConversionRatePc30dPv24h - Conversion rate PC 30d / PV 24h
  • ConversionRateAllPc30dPv24h - All conversion rate PC 30d / PV 24h
  • ConversionRatePc1d - Conversion rate post-click 1 day
  • ConversionRateAllPc1d - All conversion rate PC 1 day
  • ConversionRatePc7d - Conversion rate post-click 7 days
  • ConversionRateAllPc7d - All conversion rate PC 7 days
Cost of Sale (eCOS) Metrics:
  • ECosClientAttribution - Cost of sale with client attribution
  • ECosAllClientAttribution - All cost of sale with client attribution
  • ECosPc30d - Cost of sale post-click 30 days
  • ECosAllPc30d - All cost of sale PC 30 days
  • ECosPv24h - Cost of sale post-view 24 hours
  • ECosAllPv24h - All cost of sale PV 24 hours
  • ECosPc30dPv24h - Cost of sale PC 30d / PV 24h
  • ECosAllPc30dPv24h - All cost of sale PC 30d / PV 24h
  • ECosPc1d - Cost of sale post-click 1 day
  • ECosAllPc1d - All cost of sale PC 1 day
  • ECosPc7d - Cost of sale post-click 7 days
  • ECosAllPc7d - All cost of sale PC 7 days
Cost Per Order Metrics:
  • CostPerOrderClientAttribution - Cost per order with client attribution
  • CostPerOrderAllClientAttribution - All cost per order with client attribution
  • CostPerOrderPc30d - Cost per order post-click 30 days
  • CostPerOrderAllPc30d - All cost per order PC 30 days
  • CostPerOrderPv24h - Cost per order post-view 24 hours
  • CostPerOrderAllPv24h - All cost per order PV 24 hours
  • CostPerOrderPc30dPv24h - Cost per order PC 30d / PV 24h
  • CostPerOrderAllPc30dPv24h - All cost per order PC 30d / PV 24h
  • CostPerOrderPc1d - Cost per order post-click 1 day
  • CostPerOrderAllPc1d - All cost per order PC 1 day
  • CostPerOrderPc7d - Cost per order post-click 7 days
  • CostPerOrderAllPc7d - All cost per order PC 7 days
  • Cpc - Cost per click
  • ECpm - Effective cost per 1,000 impressions
ROAS Metrics (by Attribution Window):
  • RoasClientAttribution - ROAS with client attribution
  • RoasAllClientAttribution - All ROAS with client attribution
  • RoasPc30d - ROAS post-click 30 days
  • RoasAllPc30d - All ROAS post-click 30 days
  • RoasPv24h - ROAS post-view 24 hours
  • RoasAllPv24h - All ROAS post-view 24 hours
  • RoasPc30dPv24h - ROAS PC 30d / PV 24h
  • RoasAllPc30dPv24h - All ROAS PC 30d / PV 24h
  • RoasPc1d - ROAS post-click 1 day
  • RoasAllPc1d - All ROAS post-click 1 day
  • RoasPc7d - ROAS post-click 7 days
  • RoasAllPc7d - All ROAS post-click 7 days
Advertiser Value Metrics:
  • AdvertiserValue - Advertiser-defined value
  • AdvertiserAllValue - All advertiser value
  • CostOfAdvertiserValue - Cost of advertiser value
  • CostOfAdvertiserValueAll - All cost of advertiser value
App Install Metrics:
  • PostInstallSales - Sales after app install
  • AppInstalls - Number of app installs
  • PostInstallConversionRate - Post-install conversion rate
  • PostInstallCostOfSale - Post-install cost of sale
  • PostInstallOrderValue - Post-install order value
  • CostPerInstall - Cost per app install
  • InstallRate - App install rate
  • PostInstallCostPerOrder - Post-install cost per order
  • PostInstallRoas - Post-install ROAS
Omnichannel Metrics:
  • OmnichannelRoasClientAttribution - Omnichannel ROAS with client attribution
  • OmnichannelRoasPc30d - Omnichannel ROAS post-click 30 days
  • OmnichannelRoasAllPc30d - All omnichannel ROAS PC 30 days
  • OmnichannelRoasPv24h - Omnichannel ROAS post-view 24 hours
  • OmnichannelRoasAllPv24h - All omnichannel ROAS PV 24 hours
  • OmnichannelRevenueClientAttribution - Omnichannel revenue with client attribution
  • OmnichannelRevenuePc30d - Omnichannel revenue post-click 30 days
  • OmnichannelRevenueAllPc30d - All omnichannel revenue PC 30 days
  • OmnichannelRevenuePv24h - Omnichannel revenue post-view 24 hours
  • OmnichannelRevenueAllPv24h - All omnichannel revenue PV 24 hours
  • OmnichannelsalesClientAttribution - Omnichannel sales with client attribution
  • OmnichannelSalesPc30d - Omnichannel sales post-click 30 days
  • OmnichannelSalesAllPc30d - All omnichannel sales PC 30 days
  • OmnichannelSalesPv24h - Omnichannel sales post-view 24 hours
  • OmnichannelSalesAllPv24h - All omnichannel sales PV 24 hours
Offline/Store Metrics:
  • RoasOfflinePc30d - Offline ROAS post-click 30 days
  • RoasOfflinePv24h - Offline ROAS post-view 24 hours
  • SalesOfflinePc30d - Offline sales post-click 30 days
  • SalesOfflinePv24h - Offline sales post-view 24 hours
  • RevenueGeneratedOfflinePc30d - Offline revenue post-click 30 days
  • RevenueGeneratedOfflinePv24h - Offline revenue post-view 24 hours

​
Implementation Notes

​
Attribution Windows Explained

Criteo provides metrics with different attribution windows to help you understand how ads influence conversions:
SuffixMeaning
Pc1dPost-click 1 day - Conversions within 1 day of a click
Pc7dPost-click 7 days - Conversions within 7 days of a click
Pc30dPost-click 30 days - Conversions within 30 days of a click
Pv24hPost-view 24 hours - Conversions within 24 hours of viewing an ad
Pc30dPv24hCombined post-click 30 days and post-view 24 hours
ClientAttributionUsing your custom attribution model configured in Criteo

​
Data Granularity

The Campaign Statistics stream provides daily aggregated data broken down by:
  • Day
  • Advertiser
  • Ad Set
  • Category
  • Device type
  • Operating System
This allows for detailed analysis of campaign performance across different dimensions.

​
Currency and Timezone

  • Currency: All monetary values (spend, revenue, ROAS, etc.) are reported in the currency you configure. Make sure to select the same currency used in your Criteo account for accurate reporting.
  • Timezone: Affects how daily data is aggregated. Choose the timezone that matches your reporting needs.