Configure destination for Criteo Retail Media

Note

This topic contains information about configuring a destination that sends query results to Criteo Retail Media using orchestrations. To configure a destination that sends audiences to Criteo Retail Media using campaigns see this topic .

Criteo Retail Media allows marketers to build audiences in Criteo using their own first-party data, and then monetize those audiences by allowing others to use those audiences for their own marketing campaigns.

Important

Criteo Retail Media supports offsite and onsite display campaigns. These audiences must be sent independently and require specific configurations. Review the requirements for offline and online campaigns, and then configure a destination for each use case. A minimum match rate of 0.1% is required, calculated as (number of matches / total lines) before the audience is usable in Criteo Retail Media.

Note

Changes to offline or onsite display audiences are not immediately available in Criteo Retail Media. Allow for up to 24 hours after the point at which Amperity has finished sending audience updates for them to be available.

Get details

Review the following details before configuring credentials for Criteo Retail Media and before configuring Amperity to send audiences to Criteo Retail Media.

Detail 1.

Use OAuth to connect Amperity to Criteo Retail Media

A refresh token that is generated by the OAuth process that authorizes Amperity to send data to Criteo Retail Media.

Detail 2.

Required configuration settings

Account ID

The account ID for the account in Criteo Retail Media to which Amperity will send audience segments.

Retailer ID

The retailer ID that is associated with the account in Criteo Retail Media to which Amperity will send audience segments.

Identifier type

The identifier type. The correct value depends on the type of campaign.

For offsite campaigns must be one of the following identifiers:

  • Use “Email” to build audience segments using email addresses.

  • Use “IdentityLink” to build audience segments using LiveRamp identity graph data.

  • Use “UserIdentifier” to build audience segments using a unique identifier provided by your brand. The user identifier may be one of the following: “IDFA”, “AAID”, “LiveRamp ID”, or “Criteo Cookie ID”.

For onsite display campaigns choose the “CustomerID” identifier.

Detail 3.

Offsite campaigns only

Offsite campaigns inspire purchases and boost brand awareness with eye-catching display formats and engaging video ads. They aim to reach the advertisers’ target audiences wherever they are, outside of the retailers’ websites.

To configure offsite campaigns use one of “Email” or “UserIdentifier” for the identifier type. If “UserIdentifier”, the value may be one of the following: “IDFA”, “AAID”, “LiveRamp ID”, or “Criteo Cookie ID”.

Detail 4.

Onsite display campaigns only

Onsite display campaigns try to reach, influence, and engage shoppers at the point of purchase with custom display ad formats. Advertisers can choose which shoppers to target based on real-time browsing and searching behavior, and analyze engagement and conversions via enhanced reporting capabilities.

To configure onsite display campaigns use the “CustomerID” identifier type.

Configure credentials

OAuth is an open standard for access delegation, commonly used to grant websites or applications access to information on other websites.

Use OAuth to configure Amperity to send audiences to Criteo Retail Media.

Important

OAuth for “Criteo Retail Media” must be completed within Criteo prior to configuring OAuth in Amperity.

To configure OAuth

Step 1.

Open the Destinations tab and click Add Destination. The Add Destination dialog box opens.

Select Criteo Retail Media from the Plugin dropdown, and then from the Credential dropdown, select Create a new credential.

This opens the Create New Credential dialog box.

Step 2.

In the Create New Credential dialog box, click “Generate authorization URL”.

Copy the URL, and then provide the URL to a user who has credentials that allow access to Criteo Retail Media. The user must log in and complete the steps required by the OAuth process for Criteo Retail Media.

After this is completed, you will be redirected to the Credentials page in Amperity.

Verify the credential is on the page, and then return to the Destinations tab.

Step 3.

Open the Destinations tab and click Add Destination. The Add Destination dialog box opens.

Select Criteo Retail Media from the Plugin dropdown, and then from the Credential dropdown, select the credential that is authorized to access Criteo Retail Media.

Note

The value for the Refresh Token setting is updated automatically after you select the credential.

Reauthorize Amperity

You may need to reauthorize access to Criteo Retail Media. This is necessary when an authorization token has expired or when it has been removed by someone with permission to manage access within Criteo Retail Media. To reauthorize access to Criteo Retail Media, follow the steps to configure OAuth and create a new credential.

Add destination

Use a sandbox to configure a destination for Criteo Retail Media. Before promoting your changes, send a test audience, and then verify the the results in Criteo Retail Media. After the end-to-end workflow has been verified, push the destination from the sandbox to production.

To add a destination for Criteo Retail Media

Step 1.

Open the Destinations page, and then click the Add destination button.

Add

To configure a destination for Criteo Retail Media, do one of the following:

  1. Click the row in which Criteo Retail Media is located. Destinations are listed alphabetically and you can scroll up and down the list.

  2. Search for Criteo Retail Media. Start typing “crit”. The list will filter to show only matching destinations. Select “Criteo Retail Media”.

Step 2.

Select the credential for Criteo Retail Media from the Credential dropdown, and then click Continue.

Tip

Click the “Test connection” link on the “Configure destination” page to verify that Amperity can connect to Criteo Retail Media.

Step 3.

In the “Destination settings” dialog box, assign the destination a name and description that ensures other users of Amperity can recognize when to use this destination.

Important

Be sure the name of the destination includes a reference to the type of audience that will be sent from Amperity. For example: “Criteo Onsite Display” or “Criteo Retail Media Offsite”.

Configure business user access

By default a destination is available to all users who have permission to view personally identifiable information (PII).

Enable the Admin only checkbox to restrict access to only users assigned to the Datagrid Operator and Datagrid Administrator policies.

Enable the PII setting checkbox to allow users with limited access to PII access to this destination.

Restricted PII access is enabled when the Restrict PII access policy option that prevents users who are assigned to that option from viewing data that is marked as PII anywhere in Amperity and from sending that data to any downstream workflow.

Step 4.

Configure the following settings, and then click “Save”.

Account ID

Required

The account ID for the account in Criteo Retail Media to which Amperity will send audience segments.

Retailer ID

Required

The retailer ID that is associated with the account in Criteo Retail Media to which Amperity will send audience segments.

Identifier type

Required

The identifier type. The correct value depends on the type of campaign.

For offsite campaigns must be one of the following identifiers:

  • Use “Email” to build audience segments using email addresses.

  • Use “IdentityLink” to build audience segments using LiveRamp identity graph data.

  • Use “UserIdentifier” to build audience segments using a unique identifier provided by your brand. The user identifier may be one of the following: “IDFA”, “AAID”, “LiveRamp ID”, or “Criteo Cookie ID”.

For onsite display campaigns choose the “CustomerID” identifier.

Audience segment description (Required at orchestration)

Optional. A description for the audience segment.

Step 5.

After this destination is configured:

  • Use orchestrations to send query results

  • Use orchestrations and campaigns to send audiences

  • Use orchestrations and campaigns to send offline events