Forum

Post a new question

Categories:

Tags:

Using VAST for Advertizer SSAI

Rover 2018-08-02 03:07:58 UTC in Nimble Streamer
C16595918767b61dab93ac809def9753

Congrats on getting Advertizer SSAI working with HLS video!

I'm doing some tests here, and have gotten it working on some test cases.

Some questions:

Is it possible to take the video ads from a VAST response on our ad server instead of static files (which I have been using for my tests)? I'm assuming you'd use the handler to to poll the server, grab the files, etc.

In our use case, we currently use an ad server that fills from a couple of different ad networks. Is there any way to pull from a VAST tag for each SSAI? Would like to track impressions, etc.

Thanks!

Yury Udovichenko 2018-08-02 08:57:34 UTC
8926135388643c4be9ec685a7033dc32

Hello,

VAST is not supported directly but you can parse your VAST input in your handler and return ads URIs to Advertizer so it could play them.

Regarding tracking impressions. As Advertizer caches ads content, there will be impossible to track impressions via 3rdparty solutions. However you can parse Nimble's access log to see all ads chunks - a bit later we'll improve our docs to describe ads statistics.

Rover 2018-08-02 13:48:34 UTC
C16595918767b61dab93ac809def9753

Makes sense. Going out of town, but next week will give it a shot of grabbing VAST URI's in the handler.

I saw there was a "big red button" code example you provided, but didn't really look at it yet. That's essentially what I need: we take breaks at irregular intervals (it's a live show), so I need a way to tell it to "run ads now" but I am guessing that's what the code example does.

One downside to all of this: it pretty much negates running ad network stuff in the streams, since it caches it and no reporting. We get most of our revenue from ad network spots as opposed to ads sold in-house.

That being said, I do look forward to the ad stats docs when available.

Thanks!

Yury Udovichenko 2018-08-03 01:02:34 UTC
8926135388643c4be9ec685a7033dc32

Regarding "big red button" - you need to take a look at it for sure. It will have a gap as you will need to send response from a handler to Nimble. You'll need to set sync-up time of Advertizer to several seconds to make that gap less.

Post a reply



This website or its third-party tools use cookies, which are necessary to its functioning and required to achieve the purposes illustrated in the Privacy Policy. If you want to know more or withdraw your consent to all or some of the cookies, please refer to the Privacy Policy.
By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies.