Hi William,
Unfortunately that API doesn't work because we're not using DAI here. You always return null.
Can you please provide answers to the following questions at the utmost speed?
1. The getAdData() API, you always say that it returns extra data, but there is no definition of what is extra. Can you please clearly define what this API returns, and point to the exact tags out of the VAST that you return?
2. Since you have no way to get at the image data or any other data for that matter within the CompanionAd segment today, how hard is it for you to add this so we can read an image url, and sizes out of there?
3. In addition, as I mentioned above, we would like to send down instructions to the device to display a button with some text and a url to go to on click. Since it seems like you don't support this within the CompanionAd segment, we will send it through as part of the Extension tags....but do you support reading these tags and expose it to us?
4. If required, I am happy to jump on a call to clear this up with you to explain our use cases, and understand how you can help, and the timeline for that.
Thanks,
Ronak