Sample feed for Video Solutions

This sample feed complies with the new MRSS feed specification for Video Solutions.
This version simplifies the ingestion of MRSS content sources, and allows for improved error handling and syncing. The table lists all of the fields that Video Solutions for Google Ad Manager recognizes (and in some cases, expects) in your XML feed. Only these elements are recognized.

You can use this sample as a guide when setting up a feed for video on Ad Manager. This version includes elements used for Dynamic Ad Insertion, for demonstration purposes. Learn more from the descriptions of important elements below.

 1 <rss xmlns:atom=""

These name spaces are required in all Ad Manager MRSS feeds.

Learn more about feeds for Video Solutions.

 2 <channel>  
 3 <title>Sample video</title>  
4 <dfpvideo:version>2</dfpvideo:version> Indicates the current version of the MRSS spec that this feed uses.
5 <atom:link rel="next"
An MRSS feed may contain many thousands of items, but should be paginated with no more than 100 items per page. This link should lead to the next page of your feed. The last page of your feed should have no <atom:link rel="next"/> element.
6 <item>  
7 <pubDate>Fri, 12 Nov 2016 18:19:10 +0000</pubDate>

The published date element identifies the date on which the content was published. This is used for video ad rules.

8 <title></title>  
9 <dfpvideo:keyvalues key="episode" value="5" type="int"/>
<dfpvideo:keyvalues key="season" value="2" type="int"/>
<dfpvideo:keyvalues key="title" value="Example Title"

The key values elements describe a given video content, and can be mapped to Ad Manager key-values.
10 <media:thumbnail
  Big_Buck_Bunny_thumbnail_vlc.png"width='280' height='190'/>
The thumbnail element is displayed in the the Ad Manager interface. It will never show up larger than 280 pixels wide and 190 pixels high.
11 <media:content duration="39" url=""/>

The content duration element can be mapped to a key-value in Ad Manager, which can be used for targeting or ad rules.

The url attribute is not used in ad serving, but appears in the Ad Manager interface.

12 <dfpvideo:contentId>video1</dfpvideo:contentId>

The content ID element is required for all feeds.

It can be used for the vid parameter on a video ad request.

13 <dfpvideo:lastModifiedDate>Fri, 12 Nov 2016 18:19:10

The modified date element is required for all feeds, and indicates when any aspect of this video or its metadata was last modified.

14 <dfpvideo:lastMediaModifiedDate>Fri, 12 Nov 2016 18:19:10

Only used on DAI feeds.

The media modified date element indicates when the video content (referenced in the ingestUrl element) was most recently modified.

Use of this field is strongly recommended. When Ad Manager sees that this date has been updated, it triggers a re-ingest of the original video content.

15 <dfpvideo:cuepoints>10</dfpvideo:cuepoints>

The cuepoints element indicates the time(s) (in seconds) when mid-roll ads should be inserted.

16 <dfpvideo:ingestUrl type="application/x-mpegURL" preconditioned="true">

Only used on DAI feeds.

The ingest URL element is required for DAI feeds. It is the location that contains the original video content (without ads).

The currently supported mime types on this field are application/x-mpegURL for HLS, or application/dash+xml for DASH.

The preconditioned attribute indicates if the stream is preconditioned for mid-roll ad insertion. It defaults to false if not explicitly set.

17 </item>  
18 </channel>  
19 </rss>  

For any issues related to DAI troubleshooting or outages, contact publisher support.

Was this helpful?
How can we improve it?

Need more help?

Sign in for additional support options to quickly solve your issue