Table of contents
Appendix - Criteo Bid Data Policy
With the introduction of Header Bidding technologies and Google Enhanced Bidding Dynamic Allocation, Criteo is now facing new challenges. One of them is to avoid bidding multiple times for the same display. In order to find instances when Criteo receive several requests for the same user at the same time for the same banner, Criteo has implement a "Bid Data Policy" meant to leverage several pieces of information which can typically be sent by SSPs and build a Publisher Graph and a channel selection logic. It is compulsory for SSP to comply with this policy.
According to Criteo Bid Data Policy, the following informations should be sent in each bid request:
Parameter | Description | Criteo Field | OpenRTB references |
|---|---|---|---|
Display URL | Full URL of the page on which the display will be made | site.page (v2.3) | |
Placement id | Most granular representation of a placement | impressions.tagid | Imp.tagid (v2.5) |
tid | A unique identifier for the impression, generated by whoever originates the impression; whenever an SSP also generates opportunities (through their own wrapper for example, or if they call other SSPs, regardless of method), we require them to generate it. When the SSP is downstream from a player that generates the tid, we require the SSP to read and transmit this tid to Criteo unaltered | impressions.tid | source.tid (v2.3) |
Source type | Indication of the context of the bid request (wrapper, server-side implementation). For prebid.js scenario: there is already a page identifier in Prebid.js (bidRequest.requestId) which we require to be passed to us as "tid" until we are able to generate an impression identifier | impressions.sourcetype | source.fd (v2.3) |
Network seller id | Identifier of the entity that will be paid by the SSP | site.publisher.id/ app.publisher.id/ publisher id (v2.3) | |
Publisher id | Identifier of the website | site.id (v2.3) | |
App bundle | Platform-specific application identifier intended to be unique to the app and independent of the exchange | app.bundle | app.bundle (v2.3) |
Bid Loss Notifications | Notifications sent by the SSP when the auction is over to inform Criteo of the reason of the bid loss | See "Bid Loss Notifications" section | Loss Reasons (v2.5) |
Appendix - OpenRTB Tables used by Criteo
Connectiontype (used in the bid request)
Value | Description |
|---|---|
0 | unknown |
1 | Ethernet |
2 | WIFI |
3 | Cellular Network, unknown generation |
4 | Cellular Network - 2G |
5 | Cellular Network - 3G |
6 | Cellular Network - 4G |
Visibility (used in the bid request)
Value | Description |
|---|---|
0 | unknown |
1 | Above the fold |
2 | Deprecated, will be considered as Unknown |
3 | Below the fold |
4 | Header |
5 | Footer |
6 | Sidebar |
7 | Full Screen |