VAST skipoffset for Linear Ads

[Elston Sa]

I am testing the SDK and find that setting the skipoffset to 15 seconds does not work. It always takes it a 5 seconds.
here is the snippet from my VAST xml
...
     <Linear skipoffset="00:00:15">
      <Duration>00:00:30</Duration>
......

Am I missing something here?

Thanks

Elston

[Shawn Busolits (IMA SDK Team)]

Hi Elston,

Which SDK are you working with (Flash, HTML5, iOS, Android)?

Thanks,

Shawn Busolits

IMA SDK Team

[Elston Sa]

Hello Shawn,

I am using the iOS SDK.

Thanks

Elston

[Shawn Busolits (IMA SDK Team)]

Hi Elston,

It looks like this may be a bug - no matter what value I fill in there, I get a 5 second timer. I'll let the rest of the team now and we'll let you know when we have it resolved.

Thanks,

Shawn Busolits

IMA SDK Team

[Shawn Busolits (IMA SDK Team)]

Hi Elston,

Can you confirm that you're using a VAST 3 tag? Custom skip times are supported in VAST 3 but are *not* supported in VAST 2.

Thanks,

Shawn Busolits

IMA SDK Team

[Elston Sa]

Hello Shawn,

Here is the vast xml.
<VAST xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="vast.xsd" version="3.0">
 <Ad id="001">
  <InLine>
   <AdSystem>GDFP</AdSystem>
   <AdTitle>test ad</AdTitle>
   <Description>test ad with skip offset</Description>
   <Survey><![CDATA[http://www.fakeDomainSurvey.com]]></Survey>
   <Error><![CDATA[http://www.fakeDomainSurvey.com]]></Error>
   <Impression><![CDATA[http://www.fakeDomainSurvey.com]]></Impression>
   <Creatives>
    <Creative id="1221111" sequence="1">

     <Linear skipoffset="00:00:15">
      <Duration>00:00:30</Duration>

      <TrackingEvents>
       <Tracking event="start"><![CDATA[http://www.fakeDomainStart.com]]></Tracking>
       <Tracking event="firstQuartile"><![CDATA[http://www.fakeDomainFirstQuartile.com]]></Tracking>
       <Tracking event="midpoint"><![CDATA[http://www.fakeDomainMidpoint.com]]></Tracking>
       <Tracking event="thirdQuartile"><![CDATA[http://www.fakeDomainThirdQuartile.com]]></Tracking>
       <Tracking event="complete"><![CDATA[http://www.fakeDomainComplete.com]]></Tracking>
       <Tracking event="mute"><![CDATA[http://www.fakeDomainMute.com]]></Tracking>
       <Tracking event="unmute"><![CDATA[http://www.fakeDomainUnmute.com]]></Tracking>
       <Tracking event="rewind"><![CDATA[http://www.fakeDomainRewind.com]]></Tracking>
       <Tracking event="pause"><![CDATA[http://www.fakeDomainPause.com]]></Tracking>
       <Tracking event="resume"><![CDATA[http://www.fakeDomainResume.com]]></Tracking>
       <Tracking event="fullscreen"><![CDATA[http://www.fakeDomainFullScreen.com]]></Tracking>
       <Tracking event="creativeView"><![CDATA[http://www.fakeDomainCreativeView.com]]></Tracking>
       <Tracking event="acceptInvitation"><![CDATA[http://www.fakeDomainAcceptInvitation.com]]></Tracking>
      </TrackingEvents>
      <VideoClicks>
       <ClickThrough id="GDFP"><![CDATA[http://www.fakeDomainClickTracking.com]]></ClickThrough>
      </VideoClicks>
      <MediaFiles>
       <MediaFile id="GDFP" delivery="streaming" width="480" height="270" type="application/x-mpegURL" bitrate="312"><![CDATA[http://fakeDomain.com/ad.m3u8]]></MediaFile>
      </MediaFiles>
     </Linear>
    </Creative>
   </Creatives>
   <Extensions>
    <Extension type="geo">
     <Bandwidth>3</Bandwidth>
    </Extension>
    <Extension type="waterfall" fallback_index="0"/>
   </Extensions>
  </InLine>
 </Ad>
</VAST>

Thanks

Elston

[Bret McGowen]

Hi Elston,

Thanks for sending the VAST 3 XML. Shawn and I will take a look and let you know what we come up with.

Cheers,

Bret McGowen

IMA SDK Team

[Elston Sa]

Hello Bret,

Just following up. Do you have any update.

Thanks

Elston

[Shawn Busolits (IMA SDK Team)]

Hi Elston,

I wasn't able to test with your provided VAST - it fails to load because all of the URLs are fake. I was, however, able to test with the following sample tag, and I see it setting the skip offset to 7 seconds as provided by the vast:

http://pubads.g.doubleclick.net/gampad/ads?sz=640x360&iu=/6062/iab_vast_samples/skippable&ciu_szs=300x250,728x90&impl=s&gdfp_req=1&env=vp&output=xml_vast3&unviewed_position_start=1&url=[referrer_url]&correlator=90224067

If you have a tag with real URLs that is still exhibiting this issue I'd be happy to take a look.

Thanks,
Shawn Busolits
IMA SDK Team

[Elston Sa]

Sorry, I had provided the vast for reference only.

Are you testing on iOS?  I was able to reproduce this issue on iOS with the url you provided. i.e. The Skip offset is always 5 seconds inspite of being set as 7sec in VAST.

-Elston

[Shawn Busolits (IMA SDK Team)]

Hi Elston,

I tested this using the sample app - is this an issue with the iOS SDK or the HTML5 SDK on iOS?

Thanks,

Shawn Busolits

IMA SDK Team

[Elston Sa]

Hello Shawn
I am using the iOS SDK https://developers.google.com/interactive-media-ads/docs/sdks/ios/v3/

Thanks

Elston

[Shawn Busolits (IMA SDK Team)]

Hey Elston,

I think I've found the issue - I was testing using the SDK built from our internal repo, which has some bug fixes that haven't been included in a release yet. This looks to be related to another bug that has already been fixed, but not yet released. Our beta6 release is already underway, and this didn't make it into that unfortunately, but the fix should be out when we release beta7.

Thanks,

Shawn Busolits

IMA SDK Team

[Dang Tran]

Hi Shawn,

It seems like this issue is fixed for iOS but is occurring for Android SDK.

Here are some details of my findings:

Affected IMA version: v9 and 3.b10.3 (beta)
Could not download previous IMA plugin so could not test.

Sample App: https://github.com/BrightcoveOS/android-player-samples/tree/master/BasicIMASampleApp

AdTag URL to test: http://cs1.brightcodes.net/dtran/ads.xml

Description:
Even with <Linear skipoffset="00:00:07"> it still loads with 5 seconds offset on Android.

In other environment (iOS and Desktop) the offset time is correct.
Here is a sample page I created to validate the adTagURL: http://cs1.brightcodes.net/dtran/NG-ad-sponsors.html

Can you please advise whether or not this has been reported of if this has been looked at. If not can you please look at resolving this.

Thanks,

[Shawn Busolits (IMA SDK Team)]

Hi there,

Thanks for the info. It looks like this is indeed still not fixed in the Android SDK. I'll work with the team to get this resolved.

Thanks,

Shawn Busolits

IMA SDK Team

[Dang Tran]

Hi Shawn,

Thanks for looking into it.

Can you please let me know of any progress. Also do you have any ETA?

Thanks

- Dang Tran

[Shawn Busolits (IMA SDK Team)]

Hi Dang,

No ETA yet but I will let you know as we make progress.

Thanks,

Shawn Busolits

IMA SDK Team

[Dang Tran]

Hi Shawn,

Can I please get an update on the progress of this?

Kind regards,

[Shawn Busolits (IMA SDK Team)]

Hi Dang,

This issue should be fixed with the latest release of our Android SDK, beta 11. Give that a try and let us know if you're still seeing and issues.

Thanks,

Shawn Busolits

IMA SDK Team

[Dang Tran]

Thanks for the update!