Frequency Integration

The following explains how publishers can add IRIS.TV data to their Frequency channels.

There are 5 steps to add IRIS.TV data to channels powered by Frequency:

  1. Provide video data to IRIS.TV via the Frequency platform

  2. Frequency to pass the Frequency content_id (their Content ID) on all ad requests

  3. Ensure all your supply tags have the content_id macro added

  4. Turn on the IRIS.TV Context API in your ad server

  5. Pass the IRIS_ID to SSP partners

Step 1: Pulling video data from Frequency:

IRIS.TV has a central integration with the Frequency CMS API enabling IRIS.TV to gain access to a publishers video metadata without any development work needed by the publisher.

Providing Channel API Access to IRIS.TV:

Publishers should complete the following steps:

  1. In the Frequency platform create a new user using the following email (platformops@iris.tv).

  2. Share your Frequency AccountName with your IRIS.TV Technical Account Manager.

Once the above is completed, IRIS.TV will do a historical ingest of all videos in the channel and set up the ongoing pull requests to receive future videos added to the channel.

Step 2: Frequency to pass the Frequency content_id on all ad requests:

Confirm with Frequency that they are passing the Frequency content_id (their Content ID) on all ad requests for all distributors and rights of sale.

Step 3: Ensure all your supply tags have the content_id macro added

Ensure you have added the content_id macro to all your supply tags to enable the Frequency content_id to be ingested into your ad-server.

  • Please reference your ad server's documentation for more information on how to format this macro.

Step 4: Turn on the IRIS.TV Context API in your ad server:

Ensure you have turned on the IRIS.TV Context API in your ad server to enable the IRIS_ID to be added to your ad requests using the Frequency content_id to match the content to the IRIS_ID.

Step 5: Passing IRIS.TV data to the SSPs:

Once the IRIS.TV data has been passed to the ad server the publisher will need to update their connection with each SSP per our normal process/steps for each SSP. See here for further documentation.