Overview of feeds for Video Solutions
To target ads to video content, Ad Manager connects to your CMS (content management system) and ingests the video metadata. For some systems, such as Brightcove and Ooyala, Ad Manager has a native integration that works through the Ad Manager interface. For most others, Ad Manager can ingest metadata by using a feed-based on RSS.
In the specification, you can see:
- How a video CMS should expose video content metadata in a feed for ingestion by Ad Manager.
- A mechanism for paging, to facilitate ingestion of large amounts of metadata, and speed up the periodic syncs needed to refresh the metadata. Paging ensures optimal performance.
Structure of the video content metadata feed
See the required and recommended elements, or the structure for setting up your feed in the sample feed. The elements correspond to the namespaces that Ad Manager reads while parsing the feed, listed below.
|Schema||Namespace URL||Namespace prefix used in examples|
|Atom syndication format||
|Open search schema||
|Video Solutions metadata||
|TMS / Gracenote metadata||
Frequently asked questionsHow does Ad Manager make a request for an MRSS feed?
Your feed URL points to a paginated feed of all videos in the your publisher's CMS.
The delta feed has been deprecated and no longer applies. Your content syncs according to the required
<lastModifiedDate>, which indicates when any aspect of the video or its metadata was last modified.
Three different date and time-related MRSS XML fields may be included in a MRSS feed:
<lastMediaModifiedDate>. They are each used for different purposes. Learn about the differences between the dates used in video feeds.
Ad Manager can handle any number of videos. You should always paginate your full feed; pages of 100 are recommended.
Whenever Ad Manager syncs with the content source, it ingests cue point information. You can also initiate a manual sync if you add or change cue points in videos and want to update the video information in immediately.