Troubleshoot an MRSS video content feed

Some features might not be enabled in your network. Contact your account manager to learn more.

Feed validation results appear in the Troubleshooting section of MRSS content sources.

1. Sign in to Google Ad Manager.
2. Click Video Content sources.
3. Click any content source name to open the source details.

The sync rule on the content details page determines how often Ad Manager syncs with your content source. You can set the sync rule to either automatic or manual.

• Automatic: The newest content in the feed is ingested every few minutes for content that has a <lastModifiedDate> later than the time of the previous new content sync.
• Manual: Content is synced only when you click "Sync" for either an individual content source or from multiple content sources in your network.

To manually sync multiple content sources, click Video  Content sources, select the sources you want to sync, and click Sync. To manually sync content from an individual source, open the content source details page and click Sync.

The "Troubleshooting" section displays any existing feed validation results. You can click Validate MRSS feed to run another validation when you make any changes to your feed.

Troubleshoot validation warnings and errors

When you click to open a content source, Ad Manager automatically loads all of the MRSS validation results (they appear after the "Loading MRSS validation results..." status completes). Results are categorized by the date and time of the sync, with the newest sync at the top.

Each sync displays the number of errors and warnings. You can click to expand any instance to see details of the warnings and errors that occurred. Specific MRSS fields are linked to their specification. For each warning or error, you can expand to see the exact instances where it occurred in your feed. In the case of a parsing issue, Ad Manager displays information about values or types, and what was expected.

Some of the feed issues may be syntax related (for example, malformed XML).

  Validation errors

Feed validation errors prevent either content, or your entire feed from being ingested.

Validation issue
Required field <dfpvideo:lastModifiedDate> not set
Content is not ordered by <dfpvideo:lastModifiedDate> from newest to oldest
Unable to parse <dfpvideo:lastModifiedDate> field
Missing required field <dfpvideo:contentId>
<dfpvideo:lastModifiedDate> is set to a future date
<dfpvideo:lastMediaModifiedDate> is set to a future date
<dfpvideo:lastMediaModifiedDate> is later than <dfpvideo:lastModifiedDate>
Unable to parse <dfpvideo:contentId>
Multiple content have the same value for <dfpvideo:contentId>
<guid> is deprecated. Use <dfpvideo:contentId> instead.
Missing required field <title>
<media:title> is deprecated. Use <title> instead.
Missing required field <dfpvideo:version>
<dfpvideo:version> set to multiple values in your feed
Invalid value set for <dfpvideo:version>
Invalid feed
Entity not parsed
XML not properly formatted
No data in feed
Account not found on CMS
Error connecting to source
Cyclic paging error

 Validation warnings

Feed validation warnings indicate issues that should be addressed, but did not prevent feed ingestion.

Validation issue
Non-secure (http) <dfpvideo:ingestUrl> found; secure (https) are strongly encouraged
Missing required field <pubdate>
Content is not ordered by <pubdate> from newest to oldest
Missing required type attribute for <dfpvideo:ingestUrl>
Missing required type attribute for <dfpvideo:closedCaptionUrl>
Missing required language attribute for <dfpvideo:closedCaptionUrl>
Custom key use is reserved for <dfpvideo:keyvalues>
Invalid type attribute for <dfpvideo:ingestUrl>
Invalid preconditioned attribute for <dfpvideo:ingestUrl>
Invalid type attribute for <dfpvideo:closedCaptionUrl>
Unable to parse <media:content> duration field
Unable to parse field <pubdate>
Unable to parse <dfpvideo:keyvalues>
Unable to parse <dfpvideo:fw_caid>
Unable to parse <dfpvideo:cuepoints>
The number of <dfpvideo:cuepoints> exceeds the maximum number allowed, which is currently 1000. After a video reaches this limit, we will truncate all cue points.
Unable to parse <dfpvideo:lastMediaModifiedDate>
<dfpvideo:lastMediaModifiedDate> field not set
<dfpvideo:keyvalues> not set
<title> set to multiple values on a single item
<media:content> duration field set multiple times for the same video
<atom:link> field set multiple times for the same video
<pubdate> field set multiple times for the same video
<dfpvideo:lastModifiedDate> set multiple times for the same video
<dfpvideo:lastMediaModifiedDate> field set multiple times for the same video
<dfpvideo:contentId> set multiple times on the same video
<dfpvideo:cuepoints> set multiple times for the same video
<dfpvideo:fw_caid> set multiple times for the same video
<dfpvideo:monetizable> is deprecated. Use <media:status> instead.
<media:keywords> is deprecated. Use <dfpvideo:keyvalues> instead.
<media:category> is deprecated. Use <dfpvideo:keyvalues> instead.
The feed URL set returned more than the recommended 100 items per page.