Media play counts
A play count is an accumulated application-defined measure whose interpretation depends on the events and state rules used to update it.
A play count stores an accumulated number associated with media use. Its exact meaning depends on the application's update rules: a playback start, sufficient progress, completion, an imported value or an explicit state update can be relevant in different systems.
The field name alone does not define which rule applies. Emby's user-item model exposes a nullable PlayCount separately from played status and the last-played date.
| Value or field | What can be concluded |
|---|---|
| Count 3 | The stored counter is three under the system's rules |
| Count 0 | A zero was supplied or retained |
| Missing/null count | No count value was supplied at this interface |
| Last-played date | One latest recorded date, if available |
| Played flag | A current played classification |
Treating null as zero erases the difference between “known zero” and “not supplied.”
A total cannot reconstruct its events
A count of three does not tell us whether the events occurred yesterday, across three years, or before a history import. It cannot reveal how much of the programme was viewed or which source was used.
Even count 3 plus one last-played date leaves the earlier dates unknown. Those events require a separate history record if an application wants to reconstruct them.
Consider a fictional migration that imports count 3 for a film seen elsewhere. The number can faithfully preserve a previous counter without proving three local streaming sessions occurred on this server.
The useful comparison keeps the definition
Play counts can help a listener find frequently revisited music or contribute evidence to a recommendation system. Comparing them is meaningful only when the counting conventions and scope agree.
A counter for one user differs from a household total. A song-play definition differs from a film-completion definition. A change in event rules can also make an old and new count difficult to compare directly.
The public Emby API exposes both played-state operations and user-data updates, but their existence does not specify every automatic counter transition. For a precise interpretation, use the relevant implementation/version's behavior rather than equating the counter with completed screenings.