adaptive bit rate (ABR)
application programming interface (API)
average time spent
Cross-Device Resume (XDR)
Hosted At URL
HTTP Dynamic Streaming (HDS)
HTTP Live Streaming (HLS)
iPhone Operating System (iOS)
media RSS (MRSS)
Ooyala Player Token
tracking pixel URL
You can use tracking pixels to monitor the delivery of your ad assets. Tracking pixel URLs can be associated with both Ooyala ads and third-party ads to calculate ad impressions. (Ooyala does not track any other type of ad events, such as quartile playback or clicks.)
For third-party ads, tracking pixels are only relevant to VAST and VPAID tags and Google IMA. Ad manager modules enable publishers to manage trackers on their own, within an ad platform.
Each time a viewer watches an ad associated with a tracking pixel, an HTTP request is made to the tracking pixel URL. Tracking pixel URLs are usually used to make calls to third-party ad platforms that they use to track ad delivery. You can specify up to three pixels for each ad asset (which notifies up to three third-party ad platforms).
unique plays requested
- Ooyala mobile SDK for iOS: The Ooyala mobile SDK for iOS generates and stores a random unique ID which is application-specific. The unique ID is generated in the "OOClientID" class and is stored in the "standardUserDefaults" object and is valid until the application is deleted. This unique ID cannot be erased or reset by the end user without deleting the app. The application developer can store a different ID than the generated ID by erasing the existing ID [OOClientID resetID] and setting a new ID [OOClientID setID:New_ID].
- Ooyala mobile SDK for Android: The Ooyala mobile SDK for Android generates and store a random unique ID which is application-specific. The unique ID is generated in the "OOClientID" class and is stored in the "SharedPreferences" file and is valid until the application is deleted. This unique ID cannot be erased or reset by the end user without deleting the app. The application developer can store a different ID by erasing the existing ID [ClientID.resetID(context)] and setting a new ID [ClientID.resetID(NEW_ID)].
- All other environments (HTML5, Flash, Chromecast): In other environments, a unique user is identified by local storage or cookies. To generate the GUID, Flash players use the timestamp of when the GUID is generated and append random data to it. The string is then converted to base64. To generate the GUID, HTML5 players use the current time, browser information, and random data and hash it and convert it to base64. Within the same browser on desktop, once a GUID is set by one platform it is used for both platforms for the user. If a user clears their browser cache, that user/device's ID will get regenerated next time they watch video. Incognito modes will track a user for a single session, but once the browser is closed the GUID is erased.