How to setup the Context API Bypass in your SpringServe Seat

Setting up your Context API credentials to inject the IRIS_ID into your ad requests from SpringServe

Enabling contextual level targeting and the IRIS_ID has never been easier thanks to the SpringServe team and their native Context API integration. 

Once your inventory has been onboarded by the IRIS.TV team, there are only a few easy steps left before you can start sending the IRIS_ID downstream to your SSP and DSP partners:

1. Retrieve your API credentials from your IRIS.TV Technical Account Manager. Credentials consist of two tokens:
   
   1. Client Token
   2. Access Token
2. Provide your Access token to your SpringServe Account manager to enable IRIS.TV contextual support for your SpringServe Account. Once that token has been applied to your account, you will have access to the IRIS.TV settings menu in Supply Partners.
3. Setup your API client token and IRIS.TV API Parameter in  Supply Partner Settings. Please confirm with your IRIS.TV Technical Account Manager what your API parameter is.
   NOTE: This must be setup for each supply partner you have
   
   
4. Last step is to ensure that you are passing your content ID to SpringServe on the inbound request  to SpringServe by using the iris_content_id macro:
   1. See example below on how to configure a tag with the iris_content_id macro. The macro will signal to SpringServe that they must call the IRIS.TV API to retrieve the IRIS_ID
   2. https://tv.springserve.com/vast/12345?w=1920&h=1080&cb=&ip=&ua=&app_bundle=&app_name=&did=&iris_content_id=abdcgerteh44jj4

Once these steps are completed, the IRIS_ID will be sent downstream to all of your SSP partners automatically and allow you to compete in PMP deals where IRIS-enabled contextual segments are used for targeting.