MRSS feed migration guide

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

Benefits to content ingestion with new feed specification

  • Ad Manager only needs one MRSS XML feed. There is no need to maintain separate "full" and "delta" feeds.
  • The Ad Manager interface includes 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 are visible to Ad Manager and available immediately for ad targeting.

The old MRSS feed specification has been deprecated.

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

Since January 31, 2018, the "delta" feed URL is no longer read. Ad Manager continues to read all fields (including deprecated fields) from full feeds only.

Since March 31, 2018, feeds that do not comply with the new feed specification are not ingested.

MRSS feed specification changes

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

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

With the new specification, only <title> is supported.

<pubDate>

Previously, a "delta" feed needed to be sorted in reverse chronological order by <pubDate>. With the new specification, there is 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 is now only used for video ad rule configurations, not for content ingestion.

<atom:published> This field is replaced by the <pubDate> field.
<media:category> This field is replaced by the <dfpvideo:keyvalues> field. You can set a category by using the "key" of "category".
<media:keywords> This field is 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.

Your feed must 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 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.
<dfpvideo:version> This field is new, and is required. It indicates the current version of the MRSS spec that this feed uses. Currently, the only valid <dfpvideo:version> value is 2.
<media:content> The only accepted attributes for this element are "duration" and "url". All other attributes that were previously accepted on the <media:content> field are deprecated.
<media:description> This field is deprecated.
<media:group> This field is deprecated.
<media:status> This field is important if your feed previously used the <dfpvideo:monetizable> field.
<openSearch:itemsPerPage> This field is deprecated.
<openSearch:startIndex> This field is deprecated.
<openSearch:totalResults> This field is deprecated.
<dfpvideo:preconditioned> This field is 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 helpful?

How can we improve it?
true
Release notes

Read about the latest Ad Manager features and Help Center updates.

See what's new

Search
Clear search
Close search
Google apps
Main menu
3525268953219483313
true
Search Help Center
true
true
true
true
true
148
false
false