Passing Contextual Data to your SSPs
      Back to home
      1. Knowledge Base and Documentation
      2. IRIS-enabled™ Contextual Data: Publishers
      3. Passing Contextual Data to your SSPs

      Passing the IRIS_ID to your SSP Partners

      The following explains how to pass "iris_context" and the "iris_id" key-value pairs from your ad server to your SSP partners.

      Once you have set up the custom key-values in your Ad Server you will need to pass those values to your SSP partners. See the following information for how to do this across each SSP.

      SSP Specific Documentation

      For any SSP partners not listed above complete the following:

      Passing the “iris_context” Key-Value Pair:

      Pass the values in the “iris_context” key from your Ad Server to your SSP.

      • If your demand partner (SSP in this case) is being called directly by your ad server, you will need to ensure the “iris_context” key and all values contained flow through from your initial ad request to your SSP partners

      • This is done using macros inserted into your demand partner ad tags that reference the “context” values passed to your ad server

      Passing the “iris_id” Key-Value Pair:

      Pass the values in the “iris_id” key from the Ad Server to your SSP.

      • The IRIS_ID should always be passed to all SSPs you are working with in the content.id field

      • If your demand partner is being called directly by your ad server, you will need to ensure the “iris_id” key value flows through from your initial ad request to your SSP partners

      • This is done using macros inserted into your demand partner ad tags that reference the “iris_id” value passed to your ad server

      Your SSP partner should specify which key in their ad request needs to be populated with the “context” values, as this will be different from partner to partner

      Passing the IRIS_ID via OpenRTB

      Below is an example of how the iris_id should be passed to SSPs via the content.id field under the app or site object (whichever is relevant to your usecase):

      "954-YGtx": {
            "app": {
              "storeurl": "https://www.vizio.com/en/smart-tv-apps?appName=CRACKLE&appId=vizio.crackle",
              "name": "Crackle Vizio",
              "publisher": {
                "name": "Crackle OTT",
                "id": "1054805"
              },
              "id": "177fc3551a7542d1b55ca2512a09afca",
              "bundle": "vizio.crackle",
              "content": {
                "genre": "Comedy",
                "contentRating": "TV-PG",
                "id": "iris_7e03144c1e8d3f2e",
                "livestream": 0
              }
            }

       

      Once Completed

      Once you've configured the "iris_context" and "iris_id" passing to the SSP, the next step is to configure contextual impression tracking, Please read this page: Tracking and Reporting.