Skip to content
BSBBaba Sai Batte
Portfolio/Selected work/NBA

Experience-based case study · NBA · Jun 2021–Sep 2026

Making video playback data more meaningful

Video measurement work using Bitmovin Media Analytics, with structured context for playback and requirements for attribution across complex viewing experiences.

Playback events analysts can actually interpret — with the content, device, and view context attached.

  1. 01 · Problem
  2. 02 · Responsibility
  3. 03 · Approach
  4. 04 · Validation
  5. 05 · Outcomes
  6. 06 · Limits
Viewer action becomes a playback event; context joins before collection; validation confirms.VIEWERtapPLAYERstreamcontentdevice · viewEVENTplayback + contextCOLLECTsimulated✓ VALID
Viewer action → event + context → collection → validation

The context behind a playback event

Content, device, player, and view-mode context accompany a playback event.

01 · Problem

The problem

Playback events without context are ambiguous: the same play, pause, or view change means different things depending on the content, player, device, and whether a multiview experience is active. Emerging experiences such as multiview and game-related interactions made attribution requirements harder to preserve.

02 · Responsibility

My responsibility

  • Implemented video and playback measurement through Bitmovin Media Analytics.
  • Defined structured metadata requirements for user, device, player, content, and multiview contexts.
  • Shaped attribution and interaction requirements for multiview and game-related experiences.
  • Validated implementations across the documented cross-platform matrix with Charles, AEP Debugger, developer tools, and network inspection.

03 · Approach

Approach & architecture

A playback event is easier to interpret when the surrounding context travels with it. The documented work includes implementing video and playback measurement through Bitmovin Media Analytics and defining metadata for user, device, player, content, and multiview contexts.

  1. 01 Playback moment
  2. 02 Context metadata
  3. 03 Player implementation
  4. 04 Transition inspection
  5. 05 Attribution requirements

Interactive: explore the metadata model

Select a metadata field to see the kind of context that travels with a playback event. All values are synthetic.

MEDIA EVENT / DEMO
VIEW 02
VIEW 03

contentdemo title

Scope

The NBA role spans video alongside web, native mobile, and connected devices. For media and playback, the resume identifies Bitmovin Media Analytics and structured context that includes the user, device, player, content, and multiview dimensions.

The role also shaped measurement requirements for emerging experiences, including multiview and game-related interactive features. The focus is on attribution and interaction requirements that preserve analytical context across more complex user journeys.

Approach

Start from the media behavior that needs to be understood: playback transitions, the content being viewed, the player and device context, and whether a multiview experience is active. Define tracking and metadata requirements so the resulting events can be interpreted in relation to those dimensions.

Selecting a metadata field shows how playback context can be expressed using example values.

Attribution requirements for multiview and game-related interactions connect product discovery to the events that describe what happened. Preserving context is a measurement design concern; this portfolio does not assert a reported performance outcome.

Quality & governance

The broader measurement role includes validation across desktop, mobile web, iOS, Android, iPad, and connected-device implementations using Charles, Adobe Experience Platform Debugger, developer tools, and network inspection. That cross-platform quality practice is relevant to media implementations as well.

Event and property standards, content metadata conventions, and documentation help clarify which context belongs with a playback event. Product, analytics, engineering, and QA partners contribute through discovery, development, UAT, and release.

04 · Validation

Implementation & validation

  • Playback lifecycle transitions inspected with metadata attached at key transitions.
  • Content, player, device, and view-mode context confirmed as expected fields.
  • Cross-platform validation consistent with the broader measurement QA practice.

05 · Outcomes

Outcomes & evidence

  • Documented playback and media metadata requirements for user, device, player, content, and multiview contexts.
  • Measurement requirements defined for multiview and game-related interactions.
  • No performance or engagement outcomes are asserted — none are disclosed in the source resume.

Documented playback and media metadata requirements, measurement for multiview and game-related interactions, and cross-platform implementation validation within the broader architecture role.

06 · Limits

Limitations & boundaries

  • The visible model is illustrative and synthetic; it is not a production interface, footage, or employer payload.
  • No media-performance results, engagement metrics, or business outcomes are claimed.
Bitmovin Media AnalyticsEvent and property standardsContent metadataAttribution requirementsCross-platform QACharlesAEP Debugger