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

Version 1 Current »

Springserve has partnered with Streaming to enable seamless sharing of publisher content metadata. To facilitate this integration, the content metadata must be provided in a CSV or RSS file format, which needs to be added in the Streaming platform for access by Springserve.

For detailed instructions on how to import CSV files or add RSS feeds, please refer to the following guide [insert link or reference here]. This will walk you through the necessary steps to ensure that your content metadata is properly configured and accessible.

How to acces the meta data in Springserve:

Once the data is available in streaming, have your account manager enable the content ingestion feature setting in your Springserve account. With this flag, your account will be enabled to call an API to fetch the meta data associated to the content_id={{CONTENT_ID}} value that must be present in each request.

Setting up content targeting in Springserve can be found here: Content Attribute Targeting

The following content attributes will be targeted on based on the value of the content_id macro.

content_id
content_title
content_series
content_season
content_episode
Duration
content_categories
rating
content_genre
content_producer_name
network_name
channel_name
content_livestream
production_quality
cuepoints

Using the below sample row of meta data:

seatId

seriesName

videoTitle

contentRating

producer

genre

network

channel

content_id

78910

Bluey

Hats

TVG

Brumm

kids

Net1

ch-12

12345

If the request contains content_id parameter, call the API and populate all of the meta data associated to the content_id in outbound requests for ads

example: in the spreadsheet below the meta data associated to the content_id=12345 is

  • sample Inbound publisher request:

    https://tv.springserve.com/vast/32123?w=1920&h=1080&cb={{CACHEBUSTER}}&ip={{IP}}&ua={{USER_AGENT}}&pod_max_dur={{POD_MAX_DUR}}&pod_ad_slots={{POD_AD_SLOTS}}&content_id=12345&did={{DEVICE_ID} 
  • Sample outbound:

  • ortb spec with the content object contains all of the associated meta data to content_id value 12345

       "content": {
            "id": 12345,
            "title": Hats,
            "series": "Bluey"
            "genre": Kids,
            "producer": Brumm,
            "contentrating": TVG,
            }
        "ext": {
        "channel": "ch-12",
        "network": "Net1"
    },

  • No labels