← Back to guides
Label Basics6 min readUpdated 2026-11-19

How to Share Streaming Data With a Record Label

Prepare streaming evidence a label can check, with clear metric names, date ranges, source files and context for the numbers.

The short answer

Ask what the label needs to evaluate, then send a short readout with the relevant recording or artist, exact metric names, date ranges and source evidence. Explain material context such as promotion or playlist exposure. Keep the original exports or screenshots, label any limits, and agree whether a snapshot answers the current request.

Three things to know

  1. 01

    Keep the platform, metric definition, artist or song scope, and measurement window visible beside each figure.

  2. 02

    Support the readout with the original export or screenshot so the recipient can check what you observed.

  3. 03

    Agree on the purpose of any account access separately from sending a snapshot for evaluation.

What belongs beside each streaming figure?

Use these four fields as a compact evidence note. Keep the source files privately with the same version of the readout.

  1. 01

    Observation

    The exact metric name, value, platform, recording or artist, and any territory or source filter.

  2. 02

    Window

    Start and end dates, any fixed rolling period, the capture date, and the latest complete date visible.

  3. 03

    Source

    The original export or screenshot filename and a way for the authorized recipient to review it.

  4. 04

    Context and question

    Relevant known campaign events, limits on what the number shows, and what the label is being asked to assess.

What does the label need to understand?

Ask whether the request concerns one recording, the artist’s recent audience, a particular territory, or what happened around a previous release. That determines which evidence belongs in the readout. The Records submission guide asks for honest audience evidence a recipient can evaluate. Start with a question such as which songs are attracting listeners in the proposed release market. Then choose a few relevant observations and explain which part of the question each can answer.

How do you keep the figures comparable?

Write the platform, exact metric label, artist or song, territory filter, and date range beside each figure. Check those fields before comparing two observations. Spotify’s audience definitions distinguish monthly listeners from monthly active listeners. Monthly listeners cover all listeners in the past 28 days, while monthly active listeners intentionally streamed from active sources in that period. Keep those labels intact when copying them into a summary. For campaign interpretation beyond this handoff, use the Records audience-metrics guide.

What evidence should accompany the readout?

Keep an original export where the service provides one. Spotify’s export guide lists selected downloadable CSV stats, including song stream counts and some audience and music tables. For a view without a suitable export, capture a screenshot that preserves the metric, scope and filters. Record the capture date and the latest date represented. Spotify’s update guide says its ordinary stats update daily and use UTC day boundaries. Identify a partial latest day or a live count if either appears in the evidence you share.

What does a clear evidence note look like?

In this fictional example, an artist captures two Spotify audience views on November 16. One shows 800 monthly listeners and the other 180 monthly active listeners. The readout keeps both metric names, their 28-day scope, the capture date and links to the retained screenshots. It explains that the active count is a subset of the broader count. The artist also notes a known playlist appearance during the period, without assigning all listening to it. A label can then ask for the song or source view that would help it evaluate the pattern.

Should the label receive account access?

Ask whether the current question can be answered by the readout and its supporting files. If ongoing review requires access, agree who needs it, what they will do, and when to review that permission. Spotify’s access-level matrix includes a Reader role that can see music and audience stats. Choose the role for the actual work, using the Records platform-access guide for setup. Keep passwords, account recovery details and unrelated private documents out of the evidence package.

What context and limitations should you disclose?

Describe known promotion, playlist exposure, a new release, or a change in available catalog when it materially affects the period. Keep an observation such as a rise during an ad campaign separate from an unverified claim that the ads caused it. Retain a representative timeline, including a peak and its aftermath when relevant to the question. Say when an export is unavailable, a definition is unclear, or the latest data is incomplete. End with the question that remains open and the next evidence that could answer it.

Frequently asked questions

What if this is my first release and I have little streaming history?
State how much history is available and when the recording went live. Support the music discussion with other relevant, verifiable context.
Can I combine listener counts from different platforms?
Keep each platform’s count separately labelled. The same person may listen on several services, so a combined count needs careful description.
What if the label’s numbers differ from my snapshot?
Compare capture dates, reporting windows, filters, recording scope and definitions, then agree which view answers the question.
Can I hide personal details in a screenshot?
Remove unrelated personal details while preserving the metric, dates and filters. Keep the unedited source privately for authorized checks.
What if I find an error after sending the readout?
Send a clearly dated correction identifying the figure, its corrected source and any conclusion affected. Ask the recipient to use the replacement.