Improving bidding with user data matching

User data matching, also known as cookie matching or cookie syncing, allows DSPs to make more effective bids that are based on user information. The user information is communicated in the OpenRTB An open industry standard for communication between buyers and sellers of online advertising in real-time bidding auctions. It's published by the IAB. User object of the bid request and DSP Demand-Side Platform (DSP). A software platform that automates bidding decisions in real-time and efficiently connects buyers and audiences through an ad exchange or SSP. Also known as a buy-side platform. specific User Identifiers (UIDs) are communicated through the user matching endpoints. To maximize the pool of impressions available, Index initiates pre-auction user matching to make sure that all DSP specific UIDs are available in the bid request An OpenRTB request that is sent from a supply-side platform (SSP) or ad exchange to the DSP requesting a bid response for potential impressions. A bid request contains information about the impression that allows the DSP to decide whether to bid on the impression.. Index supports secure user matching by dropping HTTPS user sync pixels on both secure (HTTPS) and insecure (HTTP) traffic.

There are two options to set up user data matching, both of which can be active at the same time. To maximize the pool of impressions available, you should enable both of the following methods:

Note: If a user does not accept DSP cookies, user matching is not attempted.