Finetic Analytics: Sessions, Performance and Playback Routes
Interpret Finetic playback analytics, session quality, concurrency, bandwidth, route selection, device trends and retained performance evidence.
1Retained evidence scope2Routes and session qualityWhat Analytics measures#
Analytics summarises retained playback history and client telemetry on one Finetic installation. It is an administrator workspace for understanding use, delivery choices and measured client performance; it is not a public tracking service.
Choose the evidence window#
The range selector controls the reporting period. User, library and device filters narrow all compatible measures to the selected scope. Clearing the filters restores the installation-wide view for that period.
The page states the number of retained sessions and telemetry events it used. Empty evidence remains empty rather than being filled with estimates.
Headline measures#
| Measure | Exact meaning |
|---|---|
| Playback sessions | Canonical retained viewing sessions in the selected scope |
| Watch time | Sum of actual retained watched seconds |
| Active viewers | Distinct retained user identities with playback in scope |
| Concurrent peak | Highest number of overlapping retained sessions |
| Conversion hours | Retained watched time not delivered through Direct Play or HLS remux |
These are historical measures. The live Active Streams counter remains the authoritative view of what is playing now.
Sessions and route selection#
The sessions chart groups canonical playback sessions over time. Route summaries separate:
- Direct Play
- Remux
- Audio-only conversion
- Full video conversion
- Unknown legacy methods
One successful fallback does not prove that an earlier Direct Play attempt succeeded. Finetic's attempt-aware evidence keeps each concrete route separate; see Playback planning.
Session quality#
Session-quality cards use explicit rules:
| Measure | Definition |
|---|---|
| Short sessions | Retained watched time below 120 seconds |
| Abandoned sessions | Stopped or terminated below 10% progress |
| Recovery sessions | Logical sessions containing more than one playback attempt |
| Completed sessions | Sessions with the canonical completed outcome |
A short session is not automatically a failure. It may represent deliberate sampling or a short test. Expand the associated history and attempts before drawing a conclusion.
Performance evidence#
Where clients supplied telemetry, Finetic calculates percentile evidence for:
- Time to first frame
- Seek delay
- Rebuffer duration and count
- Dropped frames
- Client-reported buffer level
Percentiles are calculated only from retained observations in scope. A missing percentile means there is insufficient evidence, not zero delay.
Bandwidth and location#
Bandwidth views use retained delivered-byte or bitrate evidence when available. Local versus remote classification uses the installation's network classification. Approximate location and provider evidence appear only when the relevant IP-retention control is enabled.
Finetic does not require a third-party geolocation API key for the zero-configuration local database path. Administrators can disable or reduce network evidence retention.
Devices, users and titles#
Device and platform trends group retained compatibility identities. Exact installation identities remain separate from broader compatibility profiles, and repeated historical aliases are reconciled where the server can prove they belong to the same installation.
Top-title and top-user lists are observation counts and watched time within the selected range. They do not expose data outside the administrator's own installation.
Reading failures honestly#
The failure section distinguishes decoder, delivery, source, network and unknown failures where the client supplied enough evidence. A generic player error is not automatically treated as proof that a codec is unsupported.
Use the relevant logical session, attempt chain and raw failure category before changing a planner policy. Playback troubleshooting provides the complete workflow.
Retention and exports#
Analytics changes when history or telemetry reaches its configured retention boundary. The page displays its retained evidence scope so an administrator does not mistake a partial window for lifetime totals.
When exporting or sharing diagnostics, exclude credentials, cookies, licence tokens, private media paths and reusable playback claims. Follow Diagnostics and support.