thank you for sending your password protected site privately.
I had a look and I’m seeing these 5 events as the video ad plays:
`YuMe VPAID Wrapper event >> AdVideoStart
YuMe VPAID Wrapper event >> AdVideoFirstQuartile
YuMe VPAID Wrapper event >> AdVideoMidpoint
YuMe VPAID Wrapper event >> AdVideoThirdQuartile
YuMe VPAID Wrapper event >> AdVideoComplete`
Please have a look (or better send it to YuMe) at chapter 4.9.9 here: http://www.iab.net/media/file/VPAIDFINAL51109.pdf
It says: “AdVideoStart, AdVideoFirstQuartile, AdVideoMidpoint,
These five events are sent by the ad to notify the player of ad’s video progress. They match the VAST  events of the same names, as well as the “Percent complete” events in Digital Video In-Stream Ad Metrics Definitions , and must be im plemented to be IAB compliant. These strictly apply to the video portion of the ad experience, if any.”
Notice that there is no even for “100% quartile” or “AdVideoFourthQuartile”, but there is “AdVideoComplete” and that one fires properly as far as I can see.
Seems like their is still disconnect happening somewhere. I included the text tag for you guys to troubleshoot See tag and comment below:
I am still not seeing the 100 beacon fire, which is the video complete beacon. See screenshot of the same test tag firing off all of the beacons highlighted. If you place the test tag in the Google VAST inspector, you will see each beacon fire off. It looks like your video player may also be cutting the ad off before it is actually completed.
All of our tags contain 0, 25, 50, 75, and 100 beacons representing the ad start, quartiles, and video complete.
1) Notice that the AdVideoComplete event is present.
2) However notice that there is a failed request to htttp://as3_100/ Next open up the tag http://shadowcdn-01.yumenetworks.com/ym/1B3uA91O2152/1349/HifvrHol/vpaid_as3.xml in your web browser and check CDATA from Tracking event=”complete”. It says exactly that.
So it seems like this URL is not properly translated into a real URL, while it works for other Tracking events.
3) This all could indicate a problem bug at this point I’m not sure if it’s a problem on our side or in the VPAID ad unit itself.
I had a look at the VPAID inspector as suggested and I’m seeing the same error with “as3_100/” in there: https://foliovision.com/downloads/yume-tracking-complete-fail-google.png
Could you please send this back to YuMe?
my ad provider is YUME and they say:
“I have observed that the 100% quartile is not firing. Can you make sure that you send this beacon as well? The impression, 25, 50, and 75% quartiles are firing.”