Search
Clear search
Close search
Google apps
Main menu

MRSS feed migration guide

We are excited to announce some major improvements to DFP content ingestion, which include a much simpler MRSS feed specification for you to implement and maintain.

Benefits to content ingestion with new feed specification


  • DFP will only need one MRSS XML feed. There will no longer be a need to maintain separate "full" and "delta" feeds.
  • The DFP interface will include MRSS feed debugging tools that clearly show content ingestion problems, including details about what's wrong, and information about exactly when content was ingested.
  • New content and changes to existing content will both be visible to DFP and available immediately for ad targeting.

The old MRSS feed specification has been deprecated.


In order to fully enable these benefits, your feeds need to be compliant with the new MRSS feed specification, including the changes outlined below.

After January 31, 2018, the "delta" feed URL will no longer be read. DFP will continue to read all fields (including deprecated fields) from full feeds only, and automatically syncs once per day.

After March 31, 2018, feeds that do not comply with the new feed specification will not be ingested.

MRSS feed specification changes

Element Description of changes
<guid> This field is being deprecated in favor of <dfpvideo:contentId>.
<link> This field is being deprecated.
<media:player> This field is being deprecated.
<media:title>

This field is being replaced entirely by the <title> field. Previously feeds could include either <media:title> or <title>.

With the new specification, only <title> will be supported.

<pubDate>

Previously, a "delta" feed needed to be sorted in reverse chronological order by <pubDate>. With the new specification, there will no longer be a need for a "delta" feed.

Instead, the MRSS feed should be sorted in reverse chronological order by <dfpvideo:lastModifiedDate>. The <pubDate> field will now only be used for video ad rule configurations, not for content ingestion.

<atom:published> This field is being replaced by the <pubDate> field.
<media:category> This field is being replaced by the <dfpvideo:keyvalues> field. You can set a category by using the "key" of "category".
<media:keywords> This field is being replaced by the <dfpvideo:keyvalues> field. You can set a category by using the "key" of "keyword".
<dfpvideo:lastModifiedDate> This field, which used to be optional, is now required. For the fastest performance, your feed should be sorted in reverse chronological order by <dfpvideo:lastModifiedDate>, with the most recently published content at the top of the file.
<dfpvideo:monetizable> This field is being replaced by the <media:status> field. Instead of marking a video with <dfpvideo:monetizable> field set to "false", your feed should use the <media:status> field set to "blocked". This is the way to mark a video as inactive.
<media:content> The only accepted attribute for this element is "duration" and "url". All other attributes that were previously accepted on the <media:content> field are being deprecated.
<media:description> This field is being deprecated.
<media:group> This field is being deprecated.
<media:status> This field is important if your feed previously used the <dfpvideo:monetizable> field.
<openSearch:itemsPerPage> This field is being deprecated.
<openSearch:startIndex> This field is being deprecated.
<openSearch:totalResults> This field is being deprecated.
<dfpvideo:preconditioned> This field is being replaced by an attribute on the <dfpvideo:ingestUrl> element. Values could be preconditioned="true" or preconditioned="false", with the default being "false".
 

 See an annotated sample MRSS feed in compliance with the new feed specification.

Was this article helpful?
How can we improve it?