Your Digital Media Has Never Looked So Good

Posts: 224
Joined: Wed Jul 15, 2015 8:30 am

Re: RAF not correctly determining ad pods from VMAP

Wed Jul 12, 2017 8:26 am

Good catch, it took me quite a while to figure out that RAF backfills ads by default. This caused quite a bit of head scratching and some conspiracy theories.
IMHO backfill should be opt-in, not opt-out.
For anyone else reading this thread, include the following line to turn off backfill ads:
'disable roku's backfill ads
User avatar
Posts: 404
Joined: Fri Mar 31, 2017 2:22 pm

Re: RAF not correctly determining ad pods from VMAP

Thu Jul 13, 2017 9:15 pm

acreskey wrote:
So what was happening was that Auditude provided me with a URL for the VMAP that wasn't actually ready. If I requested that VMAP immediately (i.e. the next line of code), it would most often fail. So basically I was providing RAF with an invalid ad URL.

Because the default RAF ad prefs are set to backfill ads,  RAF was making its own ad request against the Roku default ad service (hence the "preroll" ad pod). So I've disabled the backfill of ads and I have to poll the VMAP URL until it's valid. Thanks for the help.

TL;DR: RAF did not actually have any issues in determining ad pods from a valid VMAP. If you provide an invalid URL the default behaviour is to backfill with Roku ad service ads.

Wow, i can only try to imagine how confusing that is. And thanks for explaining what the cause was. Indeed turn off backfill (at least for development) and... why is Auditude providing non-ready VMAP? What's the logic behind?! There must be some way that can be tuned up...
User avatar
Tyler Smith
Posts: 118
Joined: Thu Apr 14, 2016 10:51 am
Location: Nova Scotia, Canada

Re: RAF not correctly determining ad pods from VMAP

Mon Jul 17, 2017 5:59 am

We had this same issue.
With Auditude, you must always make a request to your m3u8 BEFORE the VMAP in order for the VMAP to return. 
Tyler Smith
Senior Developer, REDspace

Who is online

Users browsing this forum: No registered users and 5 guests