Regards, |
Akash Shah |
CONFIDENTIALITY CAUTION
This communication (including any accompanying documents) is intended only for the use of the addressee(s) and contains PRIVATE AND CONFIDENTIAL information. Unauthorized reading, dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify us immediately by e-mail and promptly destroy the original communication. Please do not copy it or use it for any other purposes, or disclose its contents to any other person. Unless stated to the contrary, any opinions or comments are personal to the writer and do not represent the official view of the Company. In case where it represents our official view, it needs to be revalidated and is subject to the terms of our engagement.Thank you for your co-operation.
Hi Akash,
Thank you for getting back to us.
For your use case of client-side session management and passing data with ad requests, the recommended approach is to leverage the adTagUrl and its custom parameters. You can dynamically append your session-specific data as key-value pairs to the ad tag URL. The ad server can then parse this information from the URL to serve relevant ads. This is the standard and supported way to pass targeting data, user IDs, or other session-related information to the ad server.
For example, on Android or iOS, you would construct your adTagUrl by adding your custom parameters to the base URL. The IMA SDK will then make the request with this appended information.
An alternative, though not for passing cookies directly to the ad server, is the userContext property available in the AdsRequest object. This property allows you to attach any custom object to the ad request, and this object will be returned to you in the AdsManagerLoadedEvent and AdErrorEvent. This is helpful for your own internal application logic to correlate requests and responses, but it is not a mechanism for sending data to the ad server.
In summary, you cannot directly manipulate the cookies used by the IMA SDK's internal network calls.
![]() |
IMA SDK Team |
[2025-08-19 11:17:07Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01syGNQ:ref" (ADR-00328931)
Hi,
Thank you for getting back to us.
Cookies are managed internally by the SDK, and this behaviour cannot be overridden. Regarding your query on integrating video ad renditions, this functionality is already supported via VAST multiple “MediaFiles”.
Since the MediaFiles tag includes multiple media, the player will automatically select the most suitable media based on factors such as bandwidth, resolution, bit rate and screen size.
After reading the first thread it looks like you are trying to integrate the same above approach but using a custom cookie which is unfortunately not possible from IMA SDK.
Let me know if you have any different business logic behind using a custom cookie via SDK.
![]() |
IMA SDK Team |
[2025-08-22 13:36:43Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01syGNQ:ref" (ADR-00328931)
![]() |
IMA SDK Team |
[2025-08-25 18:27:10Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01syGNQ:ref" (ADR-00328931)