Hi Arun,
Thank you for reaching out to us.
Could you please clarify the issue here? It would be best If you could provide to us a screen recording showing the unexpected behavior of the SDK, you can also use one of our sample apps for replicating the behavior.
On the other hand, the correlator parameter accepts a variable value that is shared by multiple requests coming from the same page view. It is used to implement competitive exclusions, including those in cookieless environments. When the IMA SDK is used, the correlator value is set automatically. If your player attempts to set this value, the SDK overwrites it with its own value.
Regards,
|
||||||
Hi Arun,
Thank you for providing additional details. However, we will also be needing the Ad Tag used that can replicate the behavior. Upon submitting the requested information, we will raise it to the rest of the team to further investigate.
Please share the information privately using the "reply to author" button or send it directly to our testing alias imate...@gmail.com. Notify us here once submitted.
Regards,
Hi Arun,
Thank you for providing the requested Ad Tags. However, I wasn't able to test on our end as I was getting an empty response from all the VAST you shared. My best guess is the Ad Tags has some kind of geo restriction you haven't mentioned, am I correct? If so, on what location do I need to spoof in for this to work?
Regards,
|
||||||
Hi Arun,
Thank you for your response.
Just to clarify, yes we can see the issue on your shared screen recording. However, we do need to test this on our end as well as this will be also asked by our team once we have raised the issue to them. I am leaning towards a possible geolocation restriction on your Ad Tag and if you can answer where we should be spoofing at or on what location are you in when making this test results, it will probably help us to make the Ad Tag work on our end.
Generally, we can't just test on an empty response from the VAST Tag.
Regards,
|
||||||
|
||||||