# Track play analytics
Source: https://docs.aden.space/docs/help/run-the-business/track-analytics

See how many times a track and each of its versions has been played, when, and (for plays that came from a share link) which share they came from. Each play records where in the file the listener started and how long they listened.
{/* Generated by `bun docs:publish` from docs/features/track-analytics.md: edit the spec, not this file. */}

## What it is [#what-it-is]

**Play analytics** show you how a track is actually being listened to. Total
plays per version, when they happened, and, when a play came from a share link,
which share it originated from.

## Using it [#using-it]

Open a track and click **Analytics**. You'll see total plays per version, when
plays happened, and (if the play came from a share link) which share it
originated from.

Each version card also has an **Activity** tab with a compact per-version view:
plays, downloads, share links, and, new, **share page views** pulled from web
analytics, so you can see anonymous visitors who opened a share link, where
they were, and how long they listened. Share-link rows there are clickable:
click one to copy its public URL.

Every version card header shows its play count at a glance; hover it for the
number of distinct listeners and the total time listened.

## What happens to play history when a track is released [#what-happens-to-play-history-when-a-track-is-released]

While a track is in progress, each play is stored individually, who listened,
when, where in the file they started and how long they stayed.

Once you set the track to **released**, that whole history is saved to a file
and the individual plays stop being recorded. Nothing is lost: the Activity tab
reads the saved history back, so you can still see every play that happened
before the release, exactly as before. What changes is that the list stops
growing: a released track's numbers are final.

The version cards keep showing their play count either way, and say "archived"
in the tooltip once the history is saved, so an unchanging number doesn't read
as a broken counter.