RE: [ima-sdk] VPAID ADAPTER ISSUE?

109 views
Skip to first unread message
Message has been deleted

IMA SDK

unread,
Jun 28, 2022, 1:50:51 AM6/28/22
to silvia...@gmail.com, ima...@googlegroups.com

Hello Silvia,

 

Michael here from IMA SDK Team. Thank you for reaching out to us.

 

First, I have tested the vast tag sample in the VSI and as you mentioned, everything seem to work fine. However, let me emphasize that I have removed this param from the tag url as it returns an error since auction price has no exact value pr=42:${AUCTION_PRICE}. Let me know if this is important and give us a value we should use in adding that parameter.

 

Additionally, would you be able to share a screen recording with navigation steps using the FW test page url: https://vi.freewheel.tv/apc/index as I cannot run properly the VAST Tag on my end using that tool? This is for better illustration of the issue.

 

Moreover, would you be able to elaborate what you were trying in this screen recording: https://drive.google.com/file/d/171YVbYX7NVDqYhMHSvy291itD2jDMiDQ/view?usp=sharing?

 

Lastly, have you tried reaching out to the Ad Manager SDK from FreeWheel support team? As the issue you encounter is using their tool, it might be best to to seek for their insights as well.

As a side note, I have removed your first post on the forum thread as it contains sensitive information. Rest assured that we have all the information shared on that message that will be used for further investigation.

 

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

https://docs.google.com/forms/d/e/1FAIpQLSfkAiXMeYP-fw1W3Z-tT9uwmATEKO5X6S-th0gR2ezdKaaqfg/viewform?usp=pp_url&entry.400550049=IMA+SDK&entry.460850823=5004Q00002cDeFDQA0&entry.80707362=00112313

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 details directly on this thread, please send it privately via "Reply to Author" button.

Regards,

 

Google Logo
Michael Angelo
IMA SDK Team
 


ref:_00D1U1174p._5004Q2cDeFD:ref

Silvia Bello Fernández

unread,
Jun 28, 2022, 3:58:43 AM6/28/22
to Interactive Media Ads SDK

Hi Michael,


1. Here you have a screen recording of the FW test tool: https://drive.google.com/file/d/1kzKACBeMGZob2R5rznW8f5X6aURIXckA/view?usp=sharing

1. Copy the Deal VAST tag
2. Paste into the FW test tool > Submit
3. HTML5 Ad preview
4. Mouse right click > Inspect
5. Network tab

As you can see it is calling the tag again and again till it stops, most probably with a timeout error.

2. What you can see in the screen recording is the same process as before but doing it manually. We go into every wrapper that the tag has, and it never stops, because it never ends in a xml with the mediafiles (mp4 or whatever..). That's why it stays in a loop and never serve the creative.


3. Yes, we are in conversations with the FW team in the meantime.


Thank you.
Regards.

IMA SDK

unread,
Jun 29, 2022, 12:52:10 AM6/29/22
to silvia...@gmail.com, ima...@googlegroups.com

Hello Silvia,

 

Thank you for further clarifying the issue and providing more information.

 

I have tested the shared VAST Tag yesterday and it appears to working perfectly on our VSI, as what you also mentioned. However, testing it now results to Ad Error 901 which could be caused by any of the following:

  • SSP VPAID wrapper not buying
  • SSP VPAID wrapper timeout
  • VPAID creatives required insecure mode
  • An Authorized Buyers "IMA Adapter" tag is used with the IMA SDK, and a VPAID ad is returned (the "Direct SDK" tag should be used)

 

You may refer here for more information. Since this kind of error relates more to a VAST issue, we would recommend reaching out to your ad provider.

 

On the other hand, since the initial concern you have is with the FW tool and is not reproducible in our VSI, we suggest that you wait for FW support team feedbacks for now, as their specialist could provide insights as to why the behavior occurred on their platform.

Regards,

 

Reply all
Reply to author
Forward
0 new messages