{"id":26606,"date":"2026-11-07T02:35:54","date_gmt":"2026-11-07T02:35:54","guid":{"rendered":"https:\/\/interspacemusic.com\/blog\/a-stream-count-needs-an-enforcement-record\/"},"modified":"2026-11-07T02:35:54","modified_gmt":"2026-11-07T02:35:54","slug":"a-stream-count-needs-an-enforcement-record","status":"publish","type":"post","link":"https:\/\/interspacemusic.com\/blog\/a-stream-count-needs-an-enforcement-record\/","title":{"rendered":"A Stream Count Needs an Enforcement Record"},"content":{"rendered":"

RBX has appealed the dismissal of a lawsuit alleging that Spotify selectively enforces its rules against fraudulent streams.<\/a> For a rightsholder, the issue is practical: a stream count records activity, while the platform\u2019s treatment of that activity affects whether the count can support a royalty claim.<\/p>\n

The rule sits between the count and the claim<\/h2>\n

The rule at issue is described as Spotify\u2019s \u201crules against fraudulent streams.\u201d<\/a> RBX alleges selective enforcement; the appeal follows a judge\u2019s dismissal of the lawsuit. Those are the facts of the dispute, not a finding that Spotify applied the rules selectively.<\/p>\n

The distinction matters when a label reviews a campaign. A count can tell the label that listening activity appeared. It cannot, by itself, tell the label how the platform classified that activity under its rules. If the label uses the count as the sole basis for expected income, it has skipped the step the dispute puts in focus: enforcement.<\/p>\n

Keep the count and any platform decision in separate fields. When a decision arrives, retain its wording and the affected recordings alongside the original count. That gives the label a way to identify the precise difference it needs to examine, rather than treating every gap between activity and expected income as the same problem. The useful question is not simply how many streams appeared. It is which streams the platform accepted under the rules that govern them.<\/p>\n

Promotion creates a different signal<\/h2>\n

Platform attention needs its own record. Apple Music\u2019s Up Next programme can place a release in a promotional setting, but the playlist alone cannot show its effect on listening.<\/a> A placement records an opportunity for discovery. A listening result records audience behaviour. Neither record answers how another platform will apply a rule concerning fraudulent streams.<\/p>\n

That separation protects campaign decisions. Suppose a label sees platform support and then sees a higher stream count. It can record the sequence, but it should still measure the listening result and retain the platform\u2019s treatment of the activity before assigning a royalty value to it. The playlist is evidence of placement; the count is evidence of recorded activity. They answer different questions.<\/p>\n

The same discipline applies before money goes into promotion. Define the audience result that would make the spending worthwhile, then decide what record will show that result. Reach alone does not price a use of music or show whether a campaign worked.<\/a> A label that specifies its measure in advance can assess the campaign without asking a royalty statement to explain every part of the outcome.<\/p>\n

A music use needs its own price<\/h2>\n

Enforcement is only one way a platform signal can be mistaken for money owed. A recording used in a social post needs rights terms and an audience measure set before the post goes live.<\/a> The use of the recording and the post\u2019s reach are separate matters. The first calls for a rights price; the second calls for a test of the campaign\u2019s audience result.<\/p>\n

For an independent label, that means deciding who may use the recording, on what terms, before treating the post as promotion. A large audience figure cannot supply a missing rights price after the fact. Nor does permission to use the recording prove that the post delivered the audience result the label wanted. Record the permission, price and result separately so that a later review can distinguish the value of the music use from the performance of the campaign.<\/p>\n

Build a ledger that answers the next question<\/h2>\n

A compact campaign ledger can give each decision its own place:<\/p>\n