This page covers data collection for the Dropped frames variable. See Dropped frames for the corresponding reporting dimension and metric.
The dropped frames variable is the running count of frames the player has dropped during the session. Set it on the QoE object and update the value whenever the player reports new drops. The backend reports the latest value at session close.
0 between updates, the backend receives 0 as the final value and reports zero dropped frames for the session regardless of what actually dropped earlier.a.media.qoe.droppedFrameCountc_contextdata.a.media.qoe.droppedFrameCountRecommended implementation types
Set droppedFrames inside xdm.mediaCollection.qoeDataDetails when calling sendEvent:
| code language-javascript |
|---|
|
Pass dropped frames as the fourth argument to createQoEObject. Update the tracker before any quality event fires.
| code language-swift |
|---|
|
Pass dropped frames as the fourth argument to createQoEObject. Update the tracker before any quality event fires.
| code language-kotlin |
|---|
|
Set droppedFrames inside xdm.mediaCollection.qoeDataDetails when calling sendMediaEvent:
| code language-brightscript |
|---|
|
Call the bitrateChange endpoint with droppedFrames inside xdm.mediaCollection.qoeDataDetails:
| code language-json |
|---|
|
Legacy implementation types (Analytics-only)
Pass dropped frames as the fourth argument to ADB.Media.createQoEObject:
| code language-javascript |
|---|
|
Pass the cumulative dropped frame count as the fourth argument to ADBMobile.media.createQoSObject and update the tracker:
| code language-javascript |
|---|
|
Include media.qoe.droppedFrames in the params object:
| code language-json |
|---|
|
See the Media Collection API events reference for the full request structure.