Veeplay supports both server-side ad reporting (where Veeplay tracks the ad and sends beacons from our content servers directly) or client-side tracking (the Veeplay HTML, iOS or Android player tracks the ad and sends beacons from the user's device).
Veeplay defaults to server-side reporting. With server-side reporting, when the player requests an ad URL from the manifest, the service reports ad consumption directly to the ad tracking URL. After the player initializes a playback session with Veeplay, no further input is required from the player to perform server-side reporting. As each ad is played back, Veeplay sends VAST-compatible beacons to the ad server to report how much of the ad has been viewed (start of the ad as well as the ad progression in quartiles: the first quartile, midpoint, third quartile, and ad completion).
To perform server-side ad reporting, simply playback your HLS/DASH stream using any compatible player. When the player requests playback from an ad segment URL (
/v1/segment path), Veeplay sends the appropriate beacon to the ad server through the ad tracking URLs.
Configuring the front-end Veeplay player SDKs to work with SSAI URLs only entails specifying a unit manager when defining the main content. Snippets for programatic as well as JSON configuration methods are outlined below.