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 built-in 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 | http://w3.org/2005/Atom |
atom |
| Media RSS | http://search.yahoo.com/mrss/ |
media |
| Video Solutions metadata | http://api.google.com/dfpvideo |
dfpvideo |
| TMS / Gracenote metadata | http://data.tmsapi.com/v1.1 |
tms |
Frequently asked questions
Your feed URL points to a paginated feed of all videos in 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: <pubDate>, <lastModifiedDate>, and <lastMediaModifiedDate>. They are each used for different purposes. The data format in each of these XML elements must conform to RFC 822 specification or follow IS0 8601 format.
RFC 822 examples
Wed, 31 Oct 2016 08:00:00 ESTWed, 31 Oct 2016 13:00:00 GMTWed, 31 Oct 2016 15:00:00 +0200
ISO 8601 examples
201610312016-10-312016-10-31T08:00:00+01:00
<pubDate>
This field identifies the date on which the content was published. It is only used for video ad rules.
<lastModifiedDate>
This field indicates when any aspect of this video or its metadata was last modified.
<lastMediaModifiedDate>
This field is only used if the feed is a source of video-on-demand content for Dynamic Ad Insertion. The date in this field indicates when the video file referenced in the <dfpvideo:ingestUrl> was last modified. You should update this field if you have re-transcoded your content or altered it in any way (for example, if you added or removed variants).
If this value is ever updated in the feed, the <lastModifiedDate> for the content also needs to be updated.
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.
