Vendor support troubleshooting guide for YouTube and VAST tags

For YouTube campaigns in Display & Video 360, creating VAST tags correctly is important to ensure there are no serving issues or delays in campaign launches. 

Use the following guide to ensure your VAST tags are properly set up for trafficking.

  1. Use YouTube VAST tags.
    • YouTube VAST tags should be used instead of the standard Display & Video 360 VAST tags for YouTube campaigns. 
  2. Ensure Innovid tags have a Universal Ad Id and are YouTube compliant.
    • For Innovid tags, YouTube requires Universal Ad ID. Standard Display & Video 360 VAST tags don't include the Universal Ad ID object within the XML.
  3. Confirm the click tracker is correctly placed.
    • The click tracker must be added on a separate click tracking node.
    • Click tags for Innovid and Campaign Manager 360 must be separated, as Innovid tags are set to "click tracking" and Campaign Manager 360 tags are set to "click through".
  4. Confirm the VAST tag uses a MP4/Webm asset and does not contain Geo Blockers
    • VAST tags can't use YouTube Video Link as a creative and can't contain Geo BlockersThis can cause an "Unacceptable video" error. 
  5. Confirm media file size does not exceed 10 MB. 
  6. Remove all non-approved Partner Pixels from the VAST tag.
    • Only approved partners should be included:
      • Viewability: MOAT, DoubleVerify, IAS
      • Brand Suitability: DoubleVerify, IAS
      • Brand Lift: Kantar, Dynata
  7. Alert the client when a creative refresh occurs.
    • If the creative was updated in the VAST tag, it can take 24 hours for the ad to be reviewed and to start serving. As such, a drop in spend may result.
  8. Re-traffic the creative if a VAST tag is detected as "Invalid".
    • This will typically resolve the issue.
  9. Check your tag!

Was this helpful?

How can we improve it?

Need more help?

Try these next steps:

Search
Clear search
Close search
Main menu
11915367325808268456
true
Search Help Center
true
true
true
true
true
69621
false
false