|
||||||
Hello,
Michael here and I work along with Teejay. Thank you for clarifying the issue.
The closest I see that can help to your use case is the getAdSlotID method. Additionally, here is the list of the methods from Ad level that may be a help to you, kindly check and see if there is anything that can satisfy your concern.
If the above would not be enough, kindly share to us the sample VAST Tag that contains the information you want to retrieve via the SDK. Please add also the screenshot that highlights this data so we can raise it precisely to our team and it will help for faster investigation and evaluation.
Regards,
|
||||||
Hi,
Thanks for your response.
Hello,
Thank you for your response. I am trying to test from your shared VAST xml, converting it to Ad Url Tag using our internal tool, and using the generated tag into our VSI but I am constantly encountering an AdError400. Would you be able to share the VAST Ad Tag url itself instead of the xml? Additionally, please provide your sample project implementation where we can reproduce the issue with logs so we can easily check the called methods/functions.
If the file(s) you are looking to share are less than 25mb in total you can attach them to this case on your next reply. If you are having trouble attaching your file to this case or if your file(s) are larger than 25mb, you can share your files with me by performing the following steps:
1. Navigate to
2. Fill out all fields, and attach your file(s).
3. Please reply back on this thread when you have uploaded your file(s). Please do not share this link.
Should you opt to share the requested information directly on this thread, please send it privately via "Reply To Author" button.
Regards,
Hello,
Thank you for the information. However, I believe you have already shared this. Thus, I have already raised the issue to the rest of our team. We will let you know the result of the investigation once completed.
Regards,
Hello,
Hope you are doing well.
I just want to get back here as our team have informed us that it needs to be spelled adSlotID, and not adSlotId. They have confirmed that the example works if it is spelled correctly. You may check here for reference: https://iabtechlab.com/wp-content/uploads/2018/06/VAST4.1-June7-FINAL.pdf#page=63. To clarify, it means in the VAST response "ID" needs to be capitalized.
Let us know should you have feedback or further concerns.
Regards,
Hello,
Thank you for responding back to us. Glad that the issue has been resolved. For your other concern, it does not appear that we have available method for this call in our developer's guide. Thus, I am raising this to the rest of our team as a feature request instead. You may check our developer's guide at a later date or keep an eye on our blog post for future updates.
Regards,
Hello,
Hope you are doing well.
I just want to get back here as our internal team needed some confirmation with the request for API/method to get the URL of the CompanionClickTracking element written in the VAST:
A little confused on the request. Can you confirm, the publisher is asking for the click-through URL?
If this is the case, this is not possible to provide, however if the publisher would like to assign a custom element as the click-through button, they can use the AdDisplayContainer's third construction parameter to do this.
If they are asking for something different, the CompanionClickTracking element is an html5 element. This would not be written in the vast, and elements typically are not represented by a URL, as far as I know.
Let me know your feedback on the above.
Regards,