This page details an example of how SpringServe can be used to pass contextual data.
Passing IRIS_ID and IRIS_CONTEXT Values to Another SpringServe Account
If you are using SpringServe, and leveraging DirectConnect to share inventory with another SpringServe publisher, DirectConnect will automatically pass the IRIS_ID and IRIS_CONTEXT values with no configuration needed by either publisher.
In Springserve, publishers need to pass the "iris_context" and "iris_id" key-value pair (KVP) in the ad tag.
This is how iris_context should appear when they are passed through the Springserve ad tag:
&iris_context=ic_4146983,ic_3809148
This is how the iris_id should be passed in through the Springserve ad tag:
&iris_id=iris_df09a302a3759de0
Using SpringServe's IRIS.TV Macros
In order to pass the values above, you will utilize IRIS specific macros in Springserve. IRIS.TV Macros simply look for the matching query string parameter in the ad request and fill in the value with what follows the equals sign. The below example should be appended to the SpringServe tag that you wish to pass IRIS-enabled values to.
Example:
&iris_context={{IRIS_CONTEXT}}&iris_id={{IRIS_ID}}
For additional information, refer to Springserve's Macro documentation or your SpringServe Account Manager.
For more information on SpringServe's IRIS-enabled Contextual Targeting feature, please refer to this page.
Using Publica's IRIS.TV Macros
If you are going to pass IRIS-enabled values into a SpringServe tag from your Publica ad server account, you can do so using Pubica's IRIS.TV specific macros, [IRIS_ID] and [IRIS_CONTEXT]. The below example should be appended to the SpringServe tag that you wish to pass IRIS-enabled values to.
Example:
&iris_context=[IRIS_CONTEXT]&iris_id=[IRIS_ID]
Other Ad Servers
It's possible to pass IRIS-enabled values from any ad server, but how this is done is unique to your ad server set up and how it's receiving IRIS-enabled values. For guidance, please reach out to your IRIS.TV Technical Account Manager.