AWS mediatailor documentation change
Summary
Updated feature compatibility table with more detailed tracking mechanisms for both client-side and server-side ad tracking across different insertion methods, including technical implementation details
Security assessment
The changes provide technical documentation about how ad tracking works in different modes (client-side vs server-side) and across different insertion methods. There is no mention of security vulnerabilities, security fixes, or security features. The documentation is purely functional.
Diff
diff --git a/mediatailor/latest/ug/sgai-feature-compatibility.md b/mediatailor/latest/ug/sgai-feature-compatibility.md index 2c9700cea..083cab6ad 100644 --- a//mediatailor/latest/ug/sgai-feature-compatibility.md +++ b//mediatailor/latest/ug/sgai-feature-compatibility.md @@ -16,2 +16,2 @@ Feature compatibility by ad insertion method Feature | Server-side ad insertion -**Client-side ad tracking** | Uses GetTracking API | Uses TRACKING section in asset list -**Server-side ad tracking** | ✓ Supported | ✓ Supported +**Client-side ad tracking** | Uses GetTracking API | Uses `TRACKING` section in asset list (`GetTracking` API is not used) +**Server-side ad tracking** | ✓ Supported — beacons fire based on `/v1/segment` requests using the session ID | ✓ Supported (HLS only) — uses sessionless beaconing with encrypted beacon data embedded in ad URIs via `#EXT-X-DEFINE:QUERYPARAM`. Requires HLS v11 or later. DASH is not yet supported. @@ -43 +43 @@ Pre-roll ad timing works differently between insertion methods: -Client-side ad tracking uses different mechanisms: +**Client-side tracking** uses different mechanisms depending on the ad insertion method: @@ -45 +45 @@ Client-side ad tracking uses different mechanisms: - * **Server-side ad insertion:** Uses the GetTracking API endpoint + * **Server-side ad insertion (SSAI):** Uses the `GetTracking` API endpoint @@ -47 +47,10 @@ Client-side ad tracking uses different mechanisms: - * **Server-guided ad insertion:** Tracking information is provided in the TRACKING section of each asset list response + * **Server-guided ad insertion (SGAI):** MediaTailor provides tracking information in the `TRACKING` section of each asset list response. The `GetTracking` API endpoint is not used. The session initialization response does not include a `trackingUrl`. + + + + +**Server-side tracking** also differs between methods: + + * **Server-side ad insertion (SSAI):** MediaTailor fires beacons when the player fetches stitched ad segments through `/v1/segment/` using the session ID. + + * **Server-guided ad insertion (SGAI):** MediaTailor uses sessionless beaconing. MediaTailor embeds encrypted beacon data (`awsBeaconData`, `awsBeaconDomain`, `awsConfigurationName`) in the ad manifest URIs that it returns in the asset list. The ad manifest uses `#EXT-X-DEFINE:QUERYPARAM` tags so the player substitutes these values into segment URLs. When the player requests each ad segment, MediaTailor decrypts the data, fires the appropriate beacon, and redirects to the content segment. When server-side reporting is active, MediaTailor omits the `TRACKING` section from the asset list response. For details, see [Server-side tracking with server-guided ad insertion (SGAI)](./ad-reporting-server-side-sgai.html). @@ -62 +71 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Server-guided ad insertion overview +Guided prefetch with manifest heartbeating