Artificial Streaming: 9 Signals for a Label Investigation

Investigate artificial-streaming concerns using analytics, royalty reports, campaign records and platform notices. Separate signals, confirmed corrections and payments.

An unexplained burst of streams deserves investigation. It does not, by itself, identify a fraudulent artist, campaign or payment. Spotify defines artificial streaming by the absence of genuine listening intent, including automated manipulation. Its policy excludes confirmed artificial streams from royalties and public counts.

Start by separating four records: artist analytics, the distributor's royalty report, campaign documentation and any platform notice. They answer different questions. Several signals below require analytics or promotion records and will not be visible in a royalty file.

Use these nine prompts to organize an investigation. They are not a validated fraud score or an official nine-point platform test. For ordinary quantity and timing differences, start with Streaming Counts vs Royalty Statements.

Nine signals to investigate

1. An unexplained spike

Spotify lists unexplained spikes among patterns worth examining. Check the track's analytics against release dates, campaign records and known exposure. Record both the anomaly and possible legitimate explanations. A useful question is “What changed on these dates?”, rather than “Who bought these plays?”

2. A rapid drop after the spike

Keep the spike and the following decline in the same case. Save dated views before drawing conclusions from a later screenshot. Ask whether a promotion ended or whether a provider issued a correction. Adjacent reporting periods are useful context, but are not interchangeable with daily listening dates.

3. A territory change with no explanation

Spotify also flags unexpected geography. Compare the territory breakdown with the campaign's intended audience and available placement records. Request an explanation for the change; do not treat a country as inherently suspicious. Keep any missing territory detail visible in the case instead of inventing an allocation.

4. An unexpected traffic source

Spotify identifies surprising sources of streams as another prompt. Capture the source label exactly as displayed and ask the provider what it means. A category such as “Other” is not a verdict. Do not map an analytics category onto a royalty-file field unless their definitions actually match.

5. Stream growth without corresponding engagement

As an editorial cross-check, compare available saves, follows and other engagement records over the same scope. This guide supplies no minimum save rate or streams-to-followers threshold. Missing engagement data cannot be treated as zero, and a mismatch is a question for investigation, not a basis for reducing a royalty.

6. A brief follower surge

Spotify's examples include sudden, short-lived follower growth. Preserve the dates and compare them with campaign activity. Combine related observations in one case so a stream spike and follower spike are not mistakenly presented as two independent confirmations of manipulation.

7. A vendor guarantees streams or placement

Spotify prohibits paid services promising streams or playlist placement. Before hiring a vendor, request its methods and reporting. Keep its offer, invoices and correspondence if concerns arise. DistroKid separately warns about problematic campaigns and playlists, including placements the artist did not purchase. Involvement does not establish who caused it. Read Spotify's policy and DistroKid's guidance.

8. Analytics and the royalty report differ

Spotify says private analytics can include artificial activity after related royalties are withheld and public metrics corrected; sometimes detection occurs before the dashboard shows it. A difference still needs an explanation for the particular track and period. Check ordinary reporting delays as well.

Use the source report to establish the reported income, then apply the relevant agreement. Reported income is not automatically the artist's royalty, statement balance or bank payment. Do not replace a missing report with public streams multiplied by an assumed universal rate.

9. A warning, correction or charge arrives

Preserve the exact notice and its affected tracks, dates, quantities and amounts. Distinguish an investigation request from a confirmed adjustment. Spotify describes per-track charges to labels and distributors for flagrant activity with very high artificial-streaming rates; this guide states no universal charge or artist pass-through rule.

Check the issuer's current process and the agreement before allocating a fee. Ask a qualified adviser about disputed liability or contractual authority. Spotify's artificial-streaming guidance explains its reporting and escalation routes. Do not promise a successful appeal or a resolution date.

A four-step investigation record

Preserve the records

Keep dated source files, analytics exports, playlist references, vendor records and notices. Add a short case summary identifying what is known, what is disputed and what is missing. Store evidence with appropriate access controls; this is not a universal retention-period recommendation.

Compare the same scope

Identify the recording, platform, territory and relevant dates in each record. Separate usage dates from the report's accounting period. Document unavailable fields. An identifier helps locate a recording; it does not establish ownership, contract participation or responsibility for the activity.

Ask before concluding

Give the case an owner and a specific question for the distributor or platform. Include the campaign information relevant to that question. Record the response and any next step. An unexplained pattern remains unresolved until the evidence supports a conclusion; avoid accusing an artist or vendor on the strength of a chart alone.

Reconcile the accounting

Separate a source-income correction, a fee and a change to an artist's royalty. For each, preserve the original and revised amount, currency, reason and authority. Follow the applicable agreement and reporting workflow. A note saying “suspected fraud” supplies neither a calculation nor permission to withhold a payment.

What Qlero's reporting controls establish

Qlero's sales-row statuses describe data validation and contract reporting. Invalid rows are excluded from calculation until their data issues are resolved. Valid means the row has passed those data checks. Reported concerns processing the participating contract shares; it can include a matching zero rate. These statuses are not findings about genuine listener intent or proof of bank settlement.

For a correction, choose the documented action for the actual error:

• Missing information on invalid rows: revalidation revisits those rows without rereading the upload. It does not recalculate statements.
• A mapping error affecting already valid rows: re-import reads the stored original file again and replaces its processed data. Linked periods must be in eligible review states and then reprocessed. Published or Closed periods block re-import.
• A replacement report from the provider: import it as a new file and establish how the earlier report is treated. A new upload does not reverse previously reported royalties.
• A correction after closing: a Closed period cannot be reopened or recalculated. Qlero documents an Other entry for a balance correction flowing into a later calculated period. Confirm the intended amount and agreement before recording it.

See revalidate versus re-import, the period lifecycle and advances and adjustments. Manual advance and Other entries use their full entered amount without applying a royalty rate; they do not transfer money.

Illustrative correction: source income versus royalty

Assume one contract with 100% participation and a 25% rate on the relevant EUR source-income base. Assume no deductions, escalation, currency conversion or other balances. These are synthetic inputs, not a platform tariff or a customer result.

• Original base: EUR 120. Royalty: 120 × 100% × 25% = EUR 30.
• Confirmed source correction: minus EUR 20. Revised base: EUR 100.
• Revised royalty: 100 × 100% × 25% = EUR 25.
• Royalty difference: 25 − 30 = minus EUR 5.

The source correction is EUR 20; the royalty difference is EUR 5 under these assumptions. Do not enter minus EUR 20 as the contract's royalty adjustment merely because that was the source correction. A separately charged fee needs its own contractual analysis. Check the royalty calculation, then reconcile the resulting statement and any external settlement evidence.

Frequently asked questions

Does a stream spike prove fraud?

No. Open an investigation and preserve the supporting records. Do not infer responsibility from the shape of a chart.

What are the common warning signs?

Use the first six prompts to organize observations, not to award points or create an automatic verdict. The engagement comparison is an editorial suggestion, not a published detection threshold.

Can a campaign explain unusual growth?

Test that explanation against its dates, scope and records. Keep a plausible explanation separate from a verified one.

Do artificial streams earn Spotify royalties?

Spotify's stated exclusion concerns confirmed artificial activity. A label's unexplained anomaly is not itself that confirmation.

Why might analytics and the report disagree?

Check the period, the data definition and documented corrections. Use the linked reconciliation guide for the broader comparison instead of assuming manipulation.

What should we do after a warning?

Preserve it, establish its scope and follow the issuer's support process. Explain any supported statement change to the affected rights holder.

What if the artist did not hire the service?

Record that fact and investigate who arranged the promotion or placement. Do not treat lack of knowledge as proof that the activity did not occur, or involvement as proof of intent.

Can public stream counts determine the artist's payable amount?

Use the report and agreement for calculation, and separately reconcile balances and settlement. A public count cannot supply all of those records.

Does a successful royalty import clear a track of fraud?

No such conclusion follows from Qlero's documented validation statuses. Ask for evidence of any specific detection capability before relying on it; this guide does not establish that capability's presence or absence.

How should an unresolved anomaly be recorded?

Retain the evidence, open questions, responsible person and next action. Leave the conclusion unresolved and distinguish any confirmed accounting correction from the wider investigation.

Put the findings into a controlled reporting workflow

Use the investigation to explain supported changes, not to manufacture a deduction. For related controls, read importing and validating sales reports, royalty accounting controls and royalty suspense.

For additional platform context, see Spotify's royalties guide and trusted-platform information. These are platform statements, not independent tests of a label's case.

Book a Qlero demo to walk through a representative source report, the applicable contract calculation and the correction path for an open or closed period.