...
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
Accessing the Metadata in Springserve:
Once the data is available in streaming, have your Streaming, you need to contact your Springserve account manager to enable the content ingestion feature setting in for your Springserve account. With Once this flagfeature is activated, your account will be enabled able to call an API to fetch the meta data associated to that fetches the metadata associated with the content_id={{CONTENT_ID}} value that parameter. This parameter must be present in each request to retrieve the relevant metadata.
Setting For information on setting up content targeting in Springserve can be found here: , refer to the guide: [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
...
Example Metadata and Usage:
Below is a sample row of meta datametadata:
seatId | seriesName | videoTitle | contentRating | producer | genre | network | channel | content_id |
|---|---|---|---|---|---|---|---|---|
78910 | Bluey | Hats | TVG | Brumm | kids | Net1 | ch-12 | 12345 |
If the request contains the content_id parameter, Springserve will call the API and populate all of the meta data associated to the content_id associated metadata in outbound requests for ads
example: in the spreadsheet below the meta data associated to the content_id=12345 is
sample Inbound publisher request:
...
.
Example 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 Request:
...
The following represents a sample outbound OpenRTB spec where the content object contains all
...
the associated
...
metadata for content_id
...
=12345
...
:
"content":
...
{
...
"id":
...
12345,
...
"title":
...
"Hats
...
", "series":
...
"Bluey"
...
, "genre":
...
"Kids
...
", "producer":
...
"Brumm
...
", "contentrating":
...
"TVG
...
" }, "ext":
...
{
...
"channel":
...
"ch-12",
...
"network":
...
"Net1"
...
}
This approach ensures that metadata such as title, genre, producer, and more is shared between Springserve and Streaming to enhance ad requests.