Receive user matching requests from Index

Index Exchange (Index) initiates user data matching when we receive a request from a user's browser that is not already matched or if the matched data has expired.

Before you begin:  

  • At the time of integration, provide the user match URL that Index should include in the 1x1 pixel.

  • To implement iFrame user matching with Index, the URL must return a correct and properly-formatted HTML page that includes an image pixel call to our user matching URL. In the case of secure iFrame user matching, any additional HTML contained within the iFrame must use HTTPS.

To receive user matching requests from Index, the following process occurs:

Index drops a 1x1 pixel on the user's browser which contains the DSP user data matching URL. The URL includes a callback to our user data matching endpoint.

The pixel sends a request to the DSP for user data matching. For more information about the fields that are sent in the request, see List of request fields sent to DSPs in Index initiated user data matching.

Note: Regional DSPs receive user data matching requests only for the regions that are enabled at the time of integration. This is to make sure that you are not syncing with users in geographical zones where you do not conduct business (for example, EMEA or APAC).

The DSP responds back to Index with the user details and returns a 1x1 pixel calling one of the following Index endpoints. For more information about the fields to include in the response, see List of response fields from DSPs in Index initiated user data matching.

    • https://dsum-sec.casalemedia.com/crum (for secure requests)
    • http://dsum.casalemedia.com/crum (for insecure requests)

The user is matched and the data is sent as part of the OpenRTB bid request in the buyeruid field. For more information about the fields to include in the response, see List of response fields from DSPs in Index initiated user data matching.