Vast troubleshooting

Vast Versions

If you notice that some of VAST campaigns are struggling with spending, it might be that it's because the VAST is running on certain version, most likely VAST 4,  most of vast traffic comes from VAST 2 and VAST 3

To check witch VAST version is being used, you need to open pre-wrapped VAST XML, To open VAST XML just paste the VAST URI in the browser :

Usually, the best scenario is when the client shares tags for all VAST versions, but if you get only 1 tag from the client, and it's VAST 4, you can manually change the version by adding &vastVersion=3 in the end of the tag, for example:

https://unified.adsafeprotected.com/v2/1598445/73100257?omidPartner=[OMIDPARTNER]&apiframeworks=[APIFRAMEWORKS]&bundleId=[BUNDLEID]&xsId=[PLEASE_IMPLEMENT_UNIQUE_ADSERVER_IMPRESSION_ID_HERE]&ias_xappb=[ctv_appid]&originalVast=https://dsp-media.eskimi.com/vast?e=0lmb8oMQVJj0yEnGgCyv80W1t7OatF8Pm7Zn7si7J0JT9a5Egr2JFN7H8Y7ugeyBsppmSqkKmTICU8lbQm7g83l6Z2hxb2pha2xjbm1ydHU&vastVersion=3

 

Vast Size

If after uploading Remote VAST URI we see VAST size as 0x0 we need to check what is inside the VAST XML

To open VAST XML just paste the VAST URI in the browser, as mentioned previously:

VAST XML will look something like this, in  that XML we should look for a <Mediafile> element, in that element you will see defined dimensions for the video, if the <Mediafile> element is missing in the XML, our system will automatically set the VAST size to 0x0.

This happens because of 2 reasons.

1. This is wrapper URL that needs to placed in VAST mp4 video and not as Remote VAST URI:

MORE INFORMATION REGARDING THIS

2. Video was wrapped incorrectly, usually the XML would just be empty (but there are edge cases as well, if you're not sure, you should escalate this to tech support):

 

Wrapped tags

VAST wrapping works by sending our VAST URI from campaign A to the client, then the client wraps that URI and sends it back to us and we set that tag on campaign B. If you see that the wrapped tag looks correct and for some reason campaign B is still not spending anything, it might be because campaign A has expired. The original campaign that we took the URI from and sent to the client needs to be at least pending (it doesn't need to be live), but it cannot be expired, so always set the campaign A duration to the campaigns B ending date.