Criteo Marketing Solutions

Criteo Marketing Solutions is a performance marketing platform that specializes in retargeting and personalized advertising, helping businesses re-engage website visitors, optimize ad spend, and drive conversions through advanced machine learning and cross-device targeting capabilities.

Power end-to-end data operations for your Criteo Marketing Solutions API with Nexla. Our bi-directional Criteo Marketing Solutions connector is purpose-built for Criteo Marketing Solutions, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Criteo Marketing Solutions or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Criteo Marketing Solutions workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Criteo Marketing Solutions credential, you need to create a Criteo application in your Developer Dashboard and obtain a Client ID and Client Secret. The Client ID and Client Secret are required to authenticate with the Criteo Marketing Solutions API using OAuth2.

To obtain your Client ID and Client Secret, you need to have a Criteo Marketing Solutions account with API access enabled. Once you have access to your account, you can create a Criteo application from your Developer Dashboard. Criteo Marketing Solutions uses OAuth2 2-legged authentication (client credentials flow) to authenticate API requests. The Client ID and Client Secret are used to obtain an access token from the OAuth2 token endpoint, which is then used to authenticate all API requests to the Criteo Marketing Solutions API. For detailed information about creating applications and OAuth2 authentication, refer to the Criteo Marketing Solutions API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Criteo App Client ID	Yes	No	Client ID for the Criteo application you created from your Developer Dashboard.
Criteo App Client Secret	Yes	Yes	Client Secret for the Criteo application you created from your Developer Dashboard.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Criteo Marketing Solutions

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Criteo App Client ID in the Criteo App Client ID field. This is the Client ID for the Criteo application you created from your Developer Dashboard. The Client ID is used along with the Client Secret to obtain an OAuth2 access token for authenticating API requests.

   The Client ID is obtained when you create a Criteo application from your Developer Dashboard. The Client ID is used along with the Client Secret to obtain an OAuth2 access token. For detailed information about creating applications and obtaining the Client ID, see the Criteo Marketing Solutions API documentation.

4. Enter your Criteo App Client Secret in the Criteo App Client Secret field. This is the Client Secret for the Criteo application you created from your Developer Dashboard. The Client Secret is used along with the Client ID to obtain an OAuth2 access token for authenticating API requests.

   Keep your Client Secret secure and do not share it publicly. The Client Secret provides access to your Criteo Marketing Solutions account and should be treated as sensitive information. The Client Secret is obtained when you create a Criteo application from your Developer Dashboard. Criteo Marketing Solutions uses OAuth2 2-legged authentication (client credentials flow) to authenticate API requests. The Client ID and Client Secret are used to obtain an access token from the OAuth2 token endpoint (https://api.criteo.com/oauth2/token), which is then used to authenticate all API requests to the Criteo Marketing Solutions API. For detailed information about creating applications and OAuth2 authentication, see the Criteo Marketing Solutions API documentation.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Criteo Marketing Solutions connector tile, then select the credential that will be used to connect to the Criteo Marketing Solutions instance, and click Next; or, create a new Criteo Marketing Solutions credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Criteo Marketing Solutions endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Fetch Advertisers

This endpoint fetches the portfolio of Advertisers for this account. Use this endpoint when you need to access advertiser information, portfolio data, or advertiser details from your Criteo Marketing Solutions account.

• Enter the API version of Criteo API you wish to use in the API Version field. This should be the API version string (e.g., 2022-10). The default value is 2022-10 if not specified.

• The endpoint uses GET requests to https://api.criteo.com/{'{api_version}'}/advertisers/me where {api_version} is the API version you provide. The endpoint URL is automatically constructed based on the Criteo Marketing Solutions API base URL and the API version.
• The endpoint does not use pagination and returns all advertisers in the portfolio in a single request.
• The endpoint will return the portfolio of advertisers for this account. The response data is extracted from the data array in the API response ($.data[*]), with each advertiser record processed individually.

API versions should match the Criteo Marketing Solutions API specification. The endpoint uses a static URL (iteration.type: static.url) and does not require pagination. The response data path is $.data[*], which extracts all items from the data array in the API response. For detailed information about fetching advertisers, see the Criteo Marketing Solutions API documentation.

Fetch Audiences

This endpoint gets a list of all the audiences for the user. Use this endpoint when you need to access audience information, audience lists, or audience data from your Criteo Marketing Solutions account.

• Enter the API version of Criteo API you wish to use in the API Version field. This should be the API version string (e.g., 2022-10). The default value is 2022-10 if not specified.

• The endpoint uses GET requests to https://api.criteo.com/{'{api_version}'}/audiences where {api_version} is the API version you provide. The endpoint URL is automatically constructed based on the Criteo Marketing Solutions API base URL and the API version.
• The endpoint does not use pagination and returns all audiences for the user in a single request.
• The endpoint will return all audiences for the user. The response data is extracted from the data array in the API response ($.data[*]), with each audience record processed individually.

API versions should match the Criteo Marketing Solutions API specification. The endpoint uses a static URL (iteration.type: static.url) and does not require pagination. The response data path is $.data[*], which extracts all items from the data array in the API response. For detailed information about fetching audiences, see the Criteo Marketing Solutions API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Criteo Marketing Solutions data sources can also be manually configured to ingest data from any valid Criteo Marketing Solutions API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Criteo Marketing Solutions API endpoints typically follow the pattern https://api.criteo.com/{api_version}/{endpoint_path} and require OAuth2 authentication, which is handled automatically by your credential configuration. Responses typically nest the relevant records under a data array, so the Path to Data field is commonly set to $.data[*]. For a complete list of available endpoints, see the Criteo Marketing Solutions API documentation.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Criteo Marketing Solutions data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Criteo Marketing Solutions destination, and select the Send to Destination option from the menu. Select the Criteo Marketing Solutions connector from the list of available destination connectors, then select the credential that will be used to connect to the Criteo Marketing Solutions organization, and click Next; or, create a new Criteo Marketing Solutions credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Criteo Marketing Solutions endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Create Audiences

This endpoint creates audiences from Nexset Record. Use this endpoint when you need to create new audiences in your Criteo Marketing Solutions account from your data sources.

• Enter the API version of Criteo API you wish to use in the API Version field. This should be the API version string (e.g., 2022-10). The default value is 2022-10 if not specified.

• The endpoint uses POST requests to https://api.criteo.com/{'{api_version}'}/audiences where {api_version} is the API version you provide. The endpoint URL is automatically constructed based on the Criteo Marketing Solutions API base URL and the API version.
• The endpoint sends data from your Nexset as the request body in JSON format. Each record in your Nexset will be sent as a JSON object containing the audience data to create. The request body should follow the Criteo Marketing Solutions API specification for creating audiences, including required fields and field names.
• Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to create an audience. If you need to create multiple audiences, you can send multiple records, but each will be processed as a separate request.

API versions should match the Criteo Marketing Solutions API specification. The request body must be properly formatted JSON that matches the Criteo Marketing Solutions API specification for creating audiences. The endpoint requires OAuth2 authentication, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For detailed information about creating audiences, including required fields, field names, and request formats, see the Criteo Marketing Solutions API documentation.

Manual configuration

Criteo Marketing Solutions destinations can also be manually configured to send data to any valid Criteo Marketing Solutions API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Criteo Marketing Solutions API endpoints typically follow the pattern https://api.criteo.com/{api_version}/{endpoint_path} and expect JSON format for request bodies. The endpoint requires OAuth2 authentication, which is handled automatically by your credential configuration, and the Content-Type: application/json header is set automatically for JSON request bodies.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Criteo Marketing Solutions endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Criteo Marketing Solutions endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.