Last.fm scrobbles on any website.

A scrobble is a single record that a specific user played a specific track at a specific time. Last.fm coined the term in 2002 and the verb has stuck around for two decades. Every modern streaming service can be wired into Last.fm: Spotify has native scrobbling in its desktop app, Apple Music goes through third-party connectors like Marvis or Cider, Tidal scrobbles via official integration, and players like foobar2000, iTunes (via the legacy plugin), Plex, mpd and Roon all push scrobbles via the same Last.fm Audioscrobbler endpoint. The result is a single unified listening log that survives switching streaming services, switching devices and switching decades. Spotify Wrapped is a closed annual snapshot owned by Spotify. A Last.fm scrobble history is yours, public and permanent. That is why the same kind of listener who cared about a high-fidelity hi-fi rig in 1995 still maintains a Last.fm profile in 2026: it is the music identity layer the streaming services refuse to build because it would let users leave.

Last.fm was acquired by CBS Interactive in 2007 for around 280 million dollars, and CBS Interactive's parent merged into what is now Paramount Global, so Last.fm is currently a Paramount property. The radio-streaming side of Last.fm was shut down in 2014, and the service today exists primarily as a scrobble log, recommendation engine and stats dashboard. Last.fm makes money through display advertising and a small Last.fm Pro subscription that costs roughly 3 dollars per month and removes ads, adds extra recommendations, and unlocks a deeper profile dashboard. Crucially, the public Last.fm REST API is free for both Free and Pro users, so embedding a scrobble feed on your own site requires no Last.fm Pro subscription. Poper manages the API key on your behalf, so you do not need to register a Last.fm developer application. The API is rate-limited to 5 requests per second per key, which Poper handles centrally with edge caching so a 100,000-pageview site still only generates a handful of upstream Last.fm calls per minute.

The Last.fm API exposes two fundamentally different shapes of data. user.getRecentTracks returns the last N scrobbles in chronological order with timestamp, artist, album, track and image, including a special 'now playing' flag on the most recent entry if the user is currently listening. This is the right view for a music writer 'now spinning' sidebar, a journalist's author page, or a podcast host's show page where you want raw, unfiltered listening data. user.getTopArtists, user.getTopAlbums and user.getTopTracks return aggregated rankings over a rolling time window: 7day, 1month, 3month, 6month, 12month or overall (which is all-time, going back to the day the account was created). Top views are right for personal-site identity blocks, all-time fingerprint pages and label/artist influences pages where the message is 'this is who I am as a listener over time'. Most pages should embed both: a small now-playing chip in the header and a larger top-artists chart in the body. Poper supports rendering both from the same widget config without re-embedding the snippet.

Every Last.fm track Poper renders emits MusicRecording structured data per Schema.org's official music vocabulary, including byArtist (with full Person or MusicGroup nesting), inAlbum (with MusicAlbum nesting), and image references to the album artwork. This makes the embedding page eligible for Google's music carousel rich result, knowledge panel mentions for the artists you scrobble most, and AI Overview citations when someone searches 'what does [music writer] listen to' or 'top artists on Last.fm 2026'. Without MusicRecording schema, search engines see a generic page with image tags and miss the structured data signal entirely. Poper also emits MusicGroup schema for the top-artists view and ItemList schema for the rolling-window top-artists/top-albums charts, so the right entity type is announced to search engines for every layout. This single change is the biggest SEO reason to use Poper instead of the official Last.fm static badge image, which emits no structured data of any kind.

Every December, Spotify Wrapped takes over music Twitter for two weeks. Wrapped is a brilliant marketing campaign, but it is also a closed snapshot: you get one set of stats per year, owned by Spotify, only shareable as a templated story image. A Last.fm widget on your own domain inverts the model. Your listening data is public year-round, deep-linkable, and lives on your domain instead of Spotify's. For music writers and critics this is professional credibility (your taste is verifiable, not curated for an annual marketing moment). For indie musicians it is influence transparency (fans can see the records that shaped your sound, not just the press-kit references). For audiophiles and crate-diggers it is identity (a 15-year scrobble log is genuinely yours in a way no Spotify metric will ever be). Embedding a Last.fm feed widget converts the once-a-year Wrapped buzz into a permanent always-on identity block, and the timing of the December Wrapped news cycle drives a measurable spike in click-throughs to deep-linked artists each year.