Inconsistent Behavior Between GAM and Other Ad Server URL

[Decoydoll]

We are currently using Video.js IMA for serving ads. Previously, we directly used a GAM VMAP URL as the adTagUrl. However, due to specific requirements, we have implemented a proxy for the GAM VMAP URL. After implementing this proxy, we noticed a different behavior: neither Video.js IMA nor the Android IMA SDK appends the ppid parameter to the requests made to our proxy. In contrast, when we switch back to making requests directly to the GAM URL, the ppid parameter is appended as expected. We also see the same thing happen to some other parameters that usually appended by the SDK.

Is this behavior expected? Considering that the IMA SDK is designed to work with any VAST-compliant ad server, we believe this inconsistency is not expected. We would have anticipated consistent behavior regardless of whether a proxy is used.

Here is the sample url:
Other Ad Server URL
GAM URL

[Kiro705]

Hello @Decoydoll,

My understanding is this is expected behavior for the IMA SDK, and not specific behavior to this Video.js IMA plugin. This issues queue should be reserved for issues that are specific to this plugin's codebase.

That said, when IMA requests ads from non-GAM urls, IMA will not include ad tag parameters that are GAM specific (like ppid).

My understanding is, it would be the proxy's responsibility to append the necessary GAM parameters when the request is made to GAM.

Thank you,
Jackson
IMA SDK team