Skip to main content
0%

App S2S OpenRTB (Legacy)

Criteo Commerce Grid DocumentationIntegration Guides Server-sideApp S2S OpenRTB (Legacy)
Table of contents

Introduction

Welcome! This document will explain how to integrate with Criteo’s In-App server-to-server solution so you can begin your Criteo display campaign.

Purpose


This specification is intended for supply partners who want to integrate server-to-server with Criteo’s Commerce Grid SSP, e.g. server-side ad insertion (SSAI) vendors. Complying with this specification will allow for a faster and more efficient integration into Criteo’s production environment.

If you have any questions about this document, please reach out to rtbspecs@criteo.com.

Auction Definition

What is often referred to as an “auction” consists of:

  1. A bid request is being sent to Criteo (among other buyers),

  2. Criteo has returned a bid response,

  3. The partner selecting a winner (if any),

  4. The partner allows the winner to display an ad to the user,

  5. The partner returned feedback to Criteo.

Each of these steps will be specified in this document, along with parallel but equally important operations such as user matching and billing.

RTB Server-to-Server Protocol

Criteo uses JSON and the HTTP POST method.

Criteo returns HTTP 204 to signal that it doesn’t want to enter the auction.

Filtering

If you have the ability to do it, please filter out any traffic corresponding to the sections below.

User filtration

Unless instructed otherwise, Criteo should only receive bid requests containing an addressable ID from a Criteo perspective:

  • the user is matched with a Criteo UID provided in user.buyeruid

  • the EIDS array contains an ID which the source contains criteo (ex: criteo.com, esp.criteo.com)

  • the EIDS array contains a RampID which source is liveramp.com

  • the EIDS array contains a UID2.0 which source is uidapi.com

  • the EIDS array contains a NetID which source is netid.de

  • a Criteo RTUS ID is available and passed in user.ext.rtusid

  • an hashed email is available and included following these specs

  • an IFA is available (IDFA or GAID) and included in device.ifa

Privacy restrictions (DNT/LMT/COPPA)

Please filter out traffic corresponding to at least one of the following:

  • "device.dnt" = 1

  • "device.lmt" = 1

  • "regs.coppa" = 1

Mobile-web interstitial

Please filter out traffic corresponding to the combination of the 3 following:

  • Mobile (ex: "device.os" = "iOS" or "Android")

  • Web (ex: "site.page" exists)

  • Interstitial (ex: "instl" = 1)

(Native only) AdChoice icon handling

By default, please filter out Native traffic from publishers that can't handle the display of Criteo AdChoice icon (corresponding to the OpenRTB field. imp[i].native.privacy).

Blocklisting API

Please filter out traffic that is linked to the list stored in the blocklisting API. For more details, please refer to the Blocklisting API section.

0%
0%