Hello Matthew,
Michael here from IMA SDK Team. Thank you for reaching out to us.
I believe adTagParameters is the correct way of overriding some of the parameters of your stream request, including the npa value. However, would you be able to share with us the sample project implementation where you are attempting to override the npa value through adTagParameters but is not being reflected after all? Kindly indicate what SDK version you are using for testing, although we highly recommend using the latest version of the SDK. Kindly include the navigation steps to reproduce the behavior on our end. A screen recording / screenshot of the issue will help for better illustration of the problem.
Regards,
|
||||||
Hello Matthew,
In addition to my previous response, please share the requested details by following the upload form below.
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.
Hello Matthew,
Thank you for your response.
I believe the npa value should show up at every request you make (one per vast ad tag). It means, that if you make another ad request call, and set the npa parameter, then it should be reflected and all the ads that will be returned are considered non-personalized.
However, to reiterate, should you need us to further investigate the issue, would you be able to share with us the sample project implementation where you are attempting to override the npa value through adTagParameters but is not being reflected after all? Kindly indicate what SDK version you are using for testing, although we highly recommend using the latest version of the SDK. Kindly include the navigation steps to reproduce the behavior on our end. A screen recording / screenshot of the issue will help for better illustration of the problem.