-
Notifications
You must be signed in to change notification settings - Fork 742
Description
Hello,
I am trying out HLS Interstitial ads using AWS MediaTailor.
(Reference: https://aws.amazon.com/ko/blogs/media/support-for-hls-interstitials-in-aws-elemental-mediatailor/)
When requesting the X-ASSET-LIST, the response from MediaTailor includes a custom JSON object called TRACKING that contains client-side ad tracking information, alongside the standard ASSETS array.
Example JSON Response:
{
"ASSETS": [
{
"DURATION": 14,
"URI": "https://segments.sample.mediatailor.aws.a2z.com/tm/.../asset.m3u8"
},
{
"DURATION": 14,
"URI": "https://segments.sample.mediatailor.aws.a2z.com/tm/.../asset.m3u8"
}
],
"TRACKING": {
"avails": [
{
"adBreakTrackingEvents": [],
"adMarkerDuration": null,
"ads": [
{
"adId": "4649886",
...
}
]
}
]
...
}
}I noticed that the current implementation ignores extra JSON objects outside the standard specification. I am looking for a way to process this custom data (like the TRACKING object) for client-side ad beaconing.
Could you let me know if there are any plans to support accessing such custom data in the future? Or is there any recommended approach to handle this?
Thank you.