View a markdown version of this page

Ad tracking with SGAI - AWS Elemental MediaTailor

Ad tracking with SGAI

SGAI supports both server-side and client-side ad tracking. You set the reporting mode at session initialization. The mode cannot change during the session.

Server-side tracking (default)

MediaTailor fires VAST beacons automatically when the player requests ad segments. Ad URIs in the asset list contain encrypted beacon metadata (awsBeaconData, awsBeaconDomain, awsConfigurationName). The player must support HLS #EXT-X-DEFINE:QUERYPARAM variable substitution. The asset list response does not include a TRACKING section.

For details about how SGAI server-side beaconing works, see Server-side tracking with server-guided ad insertion (SGAI).

Client-side tracking

Add aws.reportingMode=CLIENT to your session initialization request. The asset list response includes a TRACKING section with beacon URLs that the player fires during ad playback. The GetTracking API endpoint is not used for SGAI sessions. Instead, each asset list response includes tracking data directly. The tracking data uses the same JSON schema as the server-side ad insertion (SSAI) tracking response.

For details, see Server-guided ad insertion.