Overview: The following information is pertaining to details how the IRIS.TV Contextual Video Marketplace activates contextual data to enable publishers to activate contextual private marketplace deals. This page covers how to pass both the “context” and “iris_id” into the ad request.
Passing the “context” Values Received from IRIS.TV as a Custom Key-Value Pair into the Initial Ad Request
...
Pass the “context” values as comma-separated values into nto the “context” key
In GAM, custom key-value pairs are passed using the “cust_params” parameter either manually or through the IMA SDK
To manually add “cust_params” to your GAM calls please consult the following documentation provided by Google: https://support.google.com/admanager/answer/1080597 [Note: it is required to encode certain characters within the “cust_params” section]
To add “cust_params” through the IMA SDK, please reference the documentation specific to the version of the IMA SDK you are working with
Example of manual GAM ad request with “cust_params” populated [Note: this request has been simplified and truncated]:
https://pubads.g.doubleclick.net/gampad/ads?iu=231779945/Ad_Unit_2&env=vp&gdfp_req=1&output=xml_vast4&sz=640x480&vid=6026440620001&cust_params=context%3Dsport_basketball&sdkv=h.3.384.1&osd=2…
If you are not using GAM, please consult your ad server’s documentation to learn how custom key-value pairs are passed in the ad request
...
Prerequisite: Your ad server must support passing custom key-value pairs that flow through the demand chain using macros.
Pass the “iris_id” value into the “iris_id” key
...