Analytics

The Analytics top-level menu shows streaming performance for your releases across the stores that report data back to LabelGrid. Data is intended for trend-watching — final earnings come from royalty statements, not analytics.

The dashboard follows your light or dark theme automatically.

The five views

Analytics is organised into five views, each answering one question:

View	The question it answers
Performance	How am I doing, and which release or track is doing it?
Discovery	Where did these plays come from?
Engagement	How are people listening — and are they coming back?
Audience	Who and where are they?
Social	How is your music being used and shared across social platforms?

The filters at the top of the page — store mode, period, and scope — apply to every view.

---

Store modes: Combined, Compare, and Single

The store selector has three modes:

• Combined (the default) — one total across every store that reports data for your catalog. Where a chart combines stores, a note tells you which stores don’t report that metric, so a smaller number never silently means “one store only.”
• Compare — pick two or more stores and see them side by side as separate series on every chart. Compare is not limited to a pair: you can compare as many stores as you like, or choose All stores to compare everything at once. The All-stores comparison automatically includes any store we add later — you don’t need to update it.
• Single store — focus the whole dashboard on one store.

Your last mode is remembered, and the mode is part of the page URL — copy the address bar to share exactly the view you’re looking at.

Stores covered

Analytics currently reports data from nine stores:

Spotify, Apple Music, Deezer, Boomplay, AWA, Audiomack, Kugou, Kuwo, and QQ Music.

Social platforms (SoundCloud, Instagram, Snapchat, and others) are covered separately on the Social view — social activity is never mixed into your streaming totals.

Weekly stores: Kugou, Kuwo, and QQ Music

Kugou, Kuwo, and QQ Music report weekly, not daily. Each week you’ll see one data point per week carrying that whole week’s total, dated on the day the report covers. On a daily chart these appear as single dots with empty days between them.

Note

A gap between two weekly points is not missing data — it’s simply how these stores report. Totals over any period are still correct: the weekly point already contains the full week. The dashboard never divides a weekly total into invented daily values.

All other stores report daily.

---

Period and granularity

Choosing a period

Quick-selects cover the last 7, 30, 90, 180, or 365 days, or 2 years (30 days is the default), or pick a custom start and end date. Custom ranges can span up to two years; a longer selection is trimmed automatically.

The Day / Week / Month / Auto toggle

Next to the period picker, a granularity toggle controls how the time-series charts bucket their points:

• Day — one point per day
• Week — one point per week
• Month — one point per month
• Auto (the default) — picks a sensible granularity for the period you’ve selected, so a two-year chart isn’t 730 cramped daily points

Your choice is remembered and shareable through the URL, just like the store mode.

:::tip Partial buckets are marked, not hidden When your selected period covers only part of a week or month — say, your range ends mid-week — that bucket is visibly marked as partial (for example, “partial week — 3 days”) instead of being drawn as if it were a full week that suddenly dropped. A “falling” final bucket usually just means the bucket isn’t finished. :::

---

Still reporting: why the latest days look low

Stores report with a lag, and different metrics arrive at different speeds. The dashboard is honest about this:

• Each card shows a “Reported through” caption — the newest date for which that metric’s data is complete.
• Days after that date are drawn as a dashed, provisional tail: data has started arriving but the day isn’t final yet, so the numbers can still rise.
• If no complete day exists in your selected period yet (for example, a period covering only the last day or two), the card says “Still reporting — no complete day in this period yet.”

The most recent day is almost always partial — stores finalise a day with a delay. Major stores typically complete a day within 1–3 days; smaller stores can take longer.

---

What each store reports

Not every store reports every metric. The main coverage at a glance:

Metric	Reported by
Streams	All nine stores
Listeners	Spotify, Apple Music, Audiomack
Saves	Spotify, Audiomack
Skips, shares, completion rate, lyrics views, canvas views, device split, source split	Spotify
Streams by country	Spotify, Apple Music, Deezer, Boomplay, Audiomack
Listener gender and age	Spotify, Apple Music
Library adds, editorial playlist adds, Shazams	Apple Music
Playlist and station placements	Spotify, Apple Music, Deezer

When a card isn’t reported by the store you’re focused on, it says “not reported” for that store instead of showing a misleading zero. This is expected, not an error. In Combined mode you see the total across the stores that do report.

Listeners are counted per day — and stores count them differently

A “listener” is a person who played your music that day. Two things to know when reading listener numbers:

• Listener totals over a period add up each day’s listeners. Someone who plays your track on ten different days counts ten times in a 30-day total. That’s normal for streaming analytics — read listener trends day to day rather than as “unique fans this month.”
• Audiomack counts slightly differently. Spotify and Apple Music report a de-duplicated daily listener count per track. Audiomack reports listeners per country and subscription tier, and the daily figure adds those slices up — so a listener active in more than one country or tier on the same day can count more than once. Audiomack listener numbers run a little “hotter” as a result.

---

Top performers

The Top performers card ranks your catalog for the selected filters and period, with three tabs:

• Releases — your releases ranked by streams (the default tab)
• Tracks — individual tracks
• Artists — your artists

Use it to see what’s driving listening activity. The selected tab is part of the URL, so a shared link opens on the same tab.

Playlists and stations (placements)

The Top Playlists & Stations card in the Discovery view shows where your music has been placed — editorial and user playlists, stations, and charts — with the streams each placement drove and, where the store reports it, your position in the list.

• A store filter on the card narrows it to Spotify, Apple Music, or Deezer (the stores that report placements).
• Apple Music editorial playlist rows show a dash (—) in the plays column. Apple reports that your track is on the playlist, and at what position, but doesn’t report how many plays came from editorial playlists. The dash means “not reported,” never zero.

---

The Social view

The Social tab covers how your music is used and shared on social platforms — SoundCloud, Snapchat, Instagram, Facebook, Threads, WhatsApp, and Messenger, with TikTok coming soon.

Social activity is a different kind of number: creates (your track used in a post or Snap), views, reposts, likes, and follower growth — not streams. It’s counted separately per platform and never added to your streaming totals or store shares.

---

Release analytics

Each release has its own Analytics tab on its detail page, scoped to that release. Until a release is live and stores report streams, the tab shows “No analytics for this release yet.”

---

Analytics vs. royalty statements

Streaming analytics and royalty statements answer different questions:

• Analytics is fast and directional — it tells you what’s happening days after it happens.
• Royalty statements are the financial record — final, audited earnings, reported on the stores’ accounting schedule.

The numbers here will not match the final amounts on your royalty statements. See Statements and Reports for the financial record.

---

When data is missing

If the analytics page is empty or a card looks wrong:

• New accounts may not have any reported streaming data yet — wait until the first store reports come in
• Releases must be delivered and live on a store before any streams can be reported
• A card marked “not reported” isn’t missing data — that store simply doesn’t report that metric (see What each store reports)
• A low or dashed most-recent day is usually a day that’s still reporting, not a drop
• Single dots with gaps on Kugou, Kuwo, or QQ Music are their normal weekly reporting
• If a release has been live for several weeks and still has no data, contact support with the release details

---

Related guides

• Analytics API: Platforms, Availability, and Limits — the same data through the public API
• Statements and Reports — the financial record
• Distributing a Release — getting your music live so streams can be counted

---

Need help? Contact our support team.