AWS mediatailor documentation change

Service: mediatailor · 2025-07-16 · Documentation low

File: mediatailor/latest/ug/ad-reporting-client-side.md

Summary

Added detailed client-side reporting workflow section with sequence diagram and step-by-step explanation of tracking process

Security assessment

The changes describe workflow improvements and tracking implementation details rather than addressing security vulnerabilities. While the documentation mentions privacy compliance (VAST icon display), this appears to be standard functionality documentation rather than a security-specific update. No evidence of vulnerability fixes or security incident mitigation.

Diff

diff --git a/mediatailor/latest/ug/ad-reporting-client-side.md b/mediatailor/latest/ug/ad-reporting-client-side.md
index 061b6a44a..349749ca5 100644
--- a//mediatailor/latest/ug/ad-reporting-client-side.md
+++ b//mediatailor/latest/ug/ad-reporting-client-side.md
@@ -5 +5 @@
-Enabling client-side trackingAd server parametersOrigin interaction query parametersSession-configured featuresBest practices for client-side trackingPaging through ad beacons with GetTracking
+Client-side reporting workflowEnabling client-side trackingAd server parametersOrigin interaction query parametersSession-configured featuresBest practices for client-side trackingPaging through ad beacons with GetTracking
@@ -29,0 +30,23 @@ Using the MediaTailor client-side tracking API, you can send metadata to the pla
+## Client-side reporting workflow
+
+The following diagram shows the complete client-side reporting workflow from session initialization through ad playback and beaconing:
+
+![MediaTailor client-side reporting sequence diagram showing the interaction between the video player, MediaTailor, Ad Decision Server, content origin, and ad verification services during the complete workflow from session initialization through ad playback and beaconing.](/images/mediatailor/latest/ug/images/tracking_flow.png)
+
+The client-side reporting workflow includes the following steps:
+
+  1. **Session initialization** \- The video player sends a POST request to the MediaTailor session endpoint with JSON metadata including `adsParams`, origin tokens, and session features. MediaTailor responds with `manifestUrl` and `trackingUrl` for the session.
+
+  2. **Manifest request and ad decision** \- The player requests the personalized manifest from MediaTailor. MediaTailor requests the original content manifest from the origin, makes an ad request to the Ad Decision Server (ADS) using player parameters, receives a VAST response with ad metadata, and delivers a personalized manifest with ad markers to the player.
+
+  3. **Tracking data retrieval** \- The player polls the tracking URL at regular intervals (matching target duration for HLS or minimum update period for DASH). MediaTailor returns JSON tracking metadata containing avails, ads, tracking events, beacon URLs, and ad verification data.
+
+  4. **Ad playback and beaconing** \- During ad breaks, the player parses the tracking metadata, fires impression beacons when ads begin rendering, fires quartile beacons (start, firstQuartile, midpoint, thirdQuartile, complete) at appropriate timing, loads and executes ad verification JavaScript if required, and sends viewability/verification events to third-party verification services.
+
+  5. **Continuous polling** \- The player continues polling the tracking URL throughout the session to receive updated metadata for upcoming ad breaks and dynamic content.
+
+
+
+
+This workflow enables advanced features such as ad countdown timers, click-through functionality, companion ads, skippable ads, and VAST icon display for privacy compliance.
+