Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

Overview: The following information 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:

Overview: Passing the “context” Values Received from IRIS.TV as a Custom Key-Value Pair into the Initial Ad Request

Prerequisite: Your ad server must support passing custom key-value pairs that flow through the demand chain using macros

  • In your ad server create a new custom macro called “iris_context”

  • Pass the “context” values from the IRIS.TV Context API as comma-separated values into the “iris_context” macro

  • 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

Passing the “iris_id” Value:

Overview: Passing the “iris_id” Values Received from IRIS.TV as a Custom Key-Value Pair into the Initial Ad Request

Prerequisite: Your ad server must support passing custom key-value pairs that flow through the demand chain using macros.

  • In your ad server create a new custom macro called “iris_id”

  • Pass the “iris_id” value from the IRIS.TV Context API into the “iris_id” macro

  • 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=iris_id%3Diris_480ajfo0810&sdkv=h.3.384.1&osd=2…

  • No labels