AWS mediatailor documentation change

Service: mediatailor · 2025-08-28 · Documentation low

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

Summary

Added documentation about reportingMode parameter for client/server-side ad tracking, updated cross-references to session variables documentation, and added explicit examples for server/client-side session initialization

Security assessment

The change introduces configuration options for reporting modes but doesn't address any specific vulnerabilities. While server-side tracking might have security implications, the documentation change itself doesn't mention security aspects or vulnerabilities being mitigated.

Diff

diff --git a/mediatailor/latest/ug/ad-reporting-client-side.md b/mediatailor/latest/ug/ad-reporting-client-side.md
index 349749ca5..1158fbf61 100644
--- a//mediatailor/latest/ug/ad-reporting-client-side.md
+++ b//mediatailor/latest/ug/ad-reporting-client-side.md
@@ -10,0 +11,2 @@ Using the AWS Elemental MediaTailor client-side tracking API, you can incorporat
+For information about passing player parameters and session data to the ADS for client-side tracking, see [MediaTailor player variables for ADS requests](./variables-player.html) and [MediaTailor session variables for ADS requests](./variables-session.html).
+
@@ -128 +130 @@ Use the session-initialization JSON structure to enable, disable, or override Me
-The metadata submitted to MediaTailor at session initialization is immutable, and additional metadata cannot be added for the duration of the session. Use SCTE-35 markers to carry data that changes during the session. For more information, see [Using session variables](./variables-session.html).
+The metadata submitted to MediaTailor at session initialization is immutable, and additional metadata cannot be added for the duration of the session. Use SCTE-35 markers to carry data that changes during the session. For more information, see [MediaTailor session variables for ADS requests](./variables-session.html).
@@ -153,0 +156,41 @@ The metadata submitted to MediaTailor at session initialization is immutable, an
+### Reporting mode parameter
+
+You can specify the reporting mode when initializing a session by including the `reportingMode` parameter in the request body. This parameter controls whether MediaTailor performs client-side or server-side ad tracking for the session.
+
+  * `client` \- The player performs ad tracking and sends beacons to the ad server. This is the default mode if no `reportingMode` is specified.
+
+  * `server` \- MediaTailor performs server-side ad tracking and sends beacons directly to the ad server.
+
+
+
+
+###### Example Session initialization with server-side reporting mode
+    
+    
+    POST mediatailorURL/v1/session/hashed-account-id/origin-id/asset-id.m3u8
+    
+            {
+                "adsParams": {
+                   "deviceType": "ipad",
+                   "uid": "abdgfdyei-2283004-ueu"                     
+               },
+               "reportingMode": "server"
+            }
+
+###### Example Session initialization with client-side reporting mode (explicit)
+    
+    
+    POST mediatailorURL/v1/session/hashed-account-id/origin-id/asset-id.mpd
+    
+            {
+                "adsParams": {
+                   "deviceType": "androidmobile",
+                   "uid": "xjhhddli-9189901-uic" 
+               },
+               "reportingMode": "client"
+            }
+
+###### Note
+
+The `reportingMode` parameter is set at session initialization and cannot be changed during the session. If no `reportingMode` is specified, MediaTailor defaults to client-side reporting to maintain backward compatibility.
+