How StreamClout Calculates Spotify Streams

StreamClout records the numbers Spotify makes public — per-track playcounts, artist monthly listeners and followers, top listener cities — collects them once a day, and keeps every daily snapshot so change over time is measured, not modeled.

Where the numbers come from

The pipeline reads the public figures Spotify displays: playcounts per track, monthly listeners and follower counts per artist, and the top five cities by listener count, through the same data feeds that power Spotify's web player. It never sees anything Spotify keeps private — no listening history, no demographics, no per-user data.

A discovery service scans Spotify's catalog for artists, albums and tracks that are not tracked yet, including new releases and acts surfacing in the charts. Once discovered, an entity joins the daily collection.

The daily pipeline

The pipeline is designed around daily snapshots. It reads public track playcounts, artist monthly listeners and followers, and top cities. Not every entity has a successful observation every day. Each day's collection is kept as its own snapshot, and analytics tables are built from available snapshots and cached for the site and REST API. A cached figure can lag the source.

Because every figure is a dated measurement, daily streams are the difference between two consecutive snapshots and growth rates compare two dated observations — a trend is a sequence of real readings, not a model.

What each number measures

Streams count every play that crossed the 30-second threshold, cumulatively, all time. Album totals are the sum of their tracks' playcounts; artist totals sum the tracked catalog.

Monthly listeners count unique people who played the artist at least once in the trailing 28 days — a deduplicated headcount, not a play count. Followers count people who actively tapped follow: the slowest-moving number on the page.

Limits of the data

Where a daily measurement is missing, StreamClout shows nothing rather than an estimate. Quality checks can flag some issues, but observed changes may still include catalog updates, backfills or incomplete track coverage.

A recorded stream count can fall for several reasons, including collection and processing errors. The decrease alone does not prove a fraud purge or identify another cause. StreamClout is independent and not affiliated with or endorsed by Spotify.