Your Spotify Algorithmic Plays Went to Zero. Here Are the Five Things That Actually Cause It

A track that was picking up Radio, Daily Mix and Autoplay plays quietly stops. Other songs on the profile carry on. Nothing was taken down, nothing was emailed, and the dashboard just shows a line sliding to the floor: Spotify algorithmic plays at zero, with no notification and no obvious cause.

The most-shared explanation comes from an r/musicmarketing post on 5 September 2026 (31 upvotes, 23 comments at our 13 September pull): "if you have no showcase available for a song then that song is flagged by Spotify… You will see algorithmic plays decrease over time until they are zero." Ten commenters reported the same pattern.

The symptom is real. The causal arrow points the wrong way, and one commenter had already spotted why: "Google says that I need 1000 streams in the last 28 days to be eligible though." That is the actual rule, it is in Spotify's documentation, and it is a rolling window — eligibility is calculated from recent streams, so when streams fall, eligibility falls with them. The missing Showcase button is the thermometer, not the disease.

Five different things put algorithmic plays on the floor, and they need five different responses. We read Spotify's own support and newsroom documentation on 15 September 2026 and built the differential diagnosis nobody in this search result has written.

What "algorithmic plays at zero" looks like in your dashboard

First the vocabulary, because Spotify for Artists does not use the phrase artists use. There is no metric called "algorithmic plays". The number people mean lives under Segmentation → Source of Streams, on the Audience, Song or Release overview pages. It splits streams into six buckets:

The bolded row is what everyone means. Check it per song rather than per artist, over the last 28 days, and compare a healthy track against the dead one — the contrast is the diagnostic. Stats are recorded in UTC and the time zone cannot be changed.

One more distinction: Release Radar is recency-driven, while Discover Weekly, Radio and Autoplay are engagement-driven. A zero in the combined bucket can mean the recency half expired on schedule and the engagement half never started — two problems wearing one number.

The five causes, ranked by how often they explain it

The whole article in one table. Each row has a test you can run in Spotify for Artists in under five minutes.

Causes 1 and 2 account for most reports and neither is a penalty. Cause 3 is the one Spotify documents as switching recommendations off. Cause 4 is new this month. Work down the list in order.

Cause 1: the release aged out, exactly on schedule

The dullest explanation and the most common one. Spotify's page on getting music on Release Radar states it directly: "We'll include a song for up to 4 weeks if a listener hasn't heard it." It adds "We don't include a song in a listener's Release Radar if they've already listened to it", and that each listener gets one song per artist per week.

So a release has a built-in decay curve that owes nothing to your performance. Every follower who hears the track leaves the pool; everyone else ages out at four weeks. If Release Radar carried most of your programmed streams — as it usually does for an artist with followers and no editorial support — week five is a cliff by design.

Week 1 is the peak, weeks 2–4 decline as listeners hear it or age out, and from week 5 Release Radar contributes zero by policy — leaving only the engagement-driven sources, which build in that same window if saves and repeats are there.

The widely-repeated "4–6 weeks after release" figure comes from growth blogs, not Spotify, and so do the stream-and-save thresholds quoted for Discover Weekly. Spotify publishes none of those numbers. It does publish the four-week window, and that alone explains the shape people report.

The test: does the drop land four to six weeks after release, and is it confined to that one release? If both, you are looking at a schedule, not a flag, and there is nothing to repair. What remains is the engagement-driven half, which responds to saves, repeat listens and playlist adds — a different job from filing a support ticket.

Cause 2: no Showcase available — the thermometer, not the flag

This is the claim that sent people looking, so it gets the full treatment. Spotify Showcase requirements, quoted from Spotify's display campaign documentation:

Two rows dismantle the theory. The 1,000-streams rule makes eligibility downstream of plays: a song whose reach has gone quiet loses Showcase availability as an arithmetic consequence, weeks after the plays drop. And the release-type exclusions mean one song can be permanently ineligible while the rest of a catalogue is fine — exactly the pattern people describe as being singled out. A remaster, a re-recording or a five-artist collaboration will never show a Showcase button however it performs.

The country list is one of the most out-of-date facts in circulation. Display campaigns are available to teams based in Austria, Belgium, Denmark, Finland, France, Germany, Ireland, Italy, Netherlands, Norway, Portugal, Spain, Sweden, the United Kingdom, Canada, Mexico, the United States, Australia, New Zealand, Argentina, Brazil, Chile and Colombia — 23 countries. Spotify adds: "You won't see the Campaigns tab if your artist isn't eligible or your team isn't based in a supported country." Outside those 23 there is no Showcase option for anyone, which says nothing about your music.

Spotify has never published anything linking Showcase eligibility to an internal content flag, and the published rules explain the reports without one. If it documents such a link, this section is wrong.

The test takes a minute, and a commenter described it correctly: open Spotify for Artists on desktop and try to create a campaign for the song. Then check its last-28-day streams against 1,000, and its release type against the table.

Cause 3: artificial-streaming enforcement

This is the one case where Spotify explicitly documents algorithmic reach being switched off. From its artificial streaming page, an artificial stream is "a stream that doesn't reflect genuine user listening intent, including any instance of attempting to manipulate streaming services like Spotify by using automated processes (like bots or scripts)." When streams are identified as such:

• "Those streams do not earn royalties"
• "Those streams do not count toward public stream numbers or charts"
• "Those streams do not positively influence recommendation algorithms"

That third line is this article's symptom, described by Spotify as a documented consequence. Playlist removal, account suspension and track removal are listed as further possibilities. Since 1 April 2024 Spotify has also charged labels and distributors per track where flagrant artificial streaming is detected, noting "this charge is only applied for very high rates of artificial streaming per track."

What catches ordinary artists is that they rarely generated the streams. A paid pitching service, a "guaranteed streams" package, or a promoter several rungs below whoever took your money can put bot traffic on a track you released honestly. The tell is an unexplained spike, often from a country you have no audience in, followed weeks later by the programmed sources going quiet.

Stop the source and talk to your distributor: the per-track charge lands on them first. Conflating this with AI screening is common, and they are unrelated — enforcement here is about where your streams came from, AI screening about how the audio was made. Our Spotify for Artists guide covers the dashboard side.

Cause 4: an AI Persona badge — the cause no growth guide covers yet

This one is a month old and changes the answer for a specific group of artists. On 11 August 2026 Spotify announced an AI Persona badge for artist profiles, rolling out "starting mid-September" — which is now. The consequence is stated without hedging: "By default, Spotify will not include AI Personas in any editorial or algorithmic recommendations", unless a listener actively follows the profile. The music stays up and playable; the discovery surfaces are switched off.

Read the scope carefully, because secondary coverage has blurred it. Spotify says "this badge is about the artist's public identity, not about how the music was made", and describes the target as profiles presenting a photorealistic identity that is AI-generated and does not represent a real person. AI Credits and SongDNA are the separate features covering AI's role in making a track.

The tell that separates this from causes 1 and 2 is scope: a badge suppresses recommendations across the whole profile, not one song. If everything went quiet at once and the profile carries a badge, stop looking at individual tracks.

The knock-on effects have started elsewhere. SubmitHub's AI policy page now blocks submissions scoring 85% or higher on its detector, reports "roughly 11% of tracks uploaded in the last month have been detected as 85%+ likely to be AI", puts approval for those at "16% (vs non-AI average of 31%)", and says "there won't be a path for requesting a workaround." Its stated reason quotes Spotify's rule directly: one platform's recommendation policy is becoming another's admission gate.

Two honest limits. Six distributors — DistroKid, RouteNote, UnitedMasters, LANDR, Amuse and Symphonic — accept AI-generated music openly, so this is a discovery problem, not a distribution ban; our Spotify AI music policy page covers where the platform draws its lines. And no processing of your audio changes an AI Persona badge, because the badge is assessed from your profile. Audio work belongs to the separate gate of screening at upload, where artifact removal is the relevant tool and where we cover Undetectr. EraseAI's page on the badge has the mechanics.

Cause 5: a metadata, rights or takedown event

Worth ruling out before you spend a week on the others:

1. Right artist profile? A mismatched ISRC or artist ID at delivery can split a release onto a duplicate profile. The streams exist; they are just not yours in the data.
2. Live in every market you expect? Territory restrictions or a regional rights conflict read as a partial collapse, not a clean zero.
3. Has a rights claim landed? A sample dispute or publishing conflict can pull a track without an obvious notification.
4. Did you re-deliver? A takedown and re-upload creates a new ISRC, and Release Radar excludes "re-releases of songs already on Spotify" — the second version gets no window.
5. Did the release date move after delivery? That can void the seven-day pitching window entirely.

All five belong to your distributor. Spotify for Artists cannot fix a delivery your distributor made, and a ticket in the wrong queue is a week you do not get back.

Is Spotify Showcase worth running to recover?

If cause 2 was your diagnosis, the next thought is to buy the reach back. Here is the honest arithmetic, and the Spotify Marquee vs Showcase comparison people want here.

If your problem is an older song, Marquee is not an option — it is new-release-only and needs 5,000 monthly actives. Showcase is the one you could run.

Does Spotify Showcase work? As advertising, it does what advertising does. Spotify states campaigns are priced per click, saves are billable, and "We can't guarantee delivery of your full budget. You'll only be charged for the number of clicks that your campaign receives." Third-party reporting puts the click floor around $0.40 — a few hundred clicks on the $100 minimum. Spotify publishes no CPC itself, so treat any figure as an estimate.

Is Spotify Showcase worth it as a repair? There is a plausible mechanism — saves are billable clicks, and saves are among the signals programmed sources read — but Spotify publishes nothing on how often a campaign restores algorithmic reach, so nobody quoting a conversion rate has a source. Run it as paid reach you were going to buy anyway, and not at all if your diagnosis is cause 3 or 4. Note the loop in cause 2: a campaign that lifts a track back over 1,000 streams per 28 days also restores its eligibility, which tells you how little that eligibility ever signalled.

What Spotify support can and cannot do about it

The original post is blunt: "regular support will not be enough to help you." Another commenter reported "generic answers and a closed ticket in the end." That matches the structure of the problem, not hostility at the support desk.

• Causes 1 and 2 — nothing to escalate. No decision was made; a window closed or a threshold was not met.
• Cause 3 — the distributor is the right party; the per-track charge and the account relationship sit with them.
• Cause 4 — a real process exists. Reviewed profiles are notified and can appeal, so a wrongly applied badge is the ticket worth filing.
• Cause 5 — your distributor, every time.

Four of the five are not Spotify support's to fix, which is the likeliest reason the copy-paste replies feel like stonewalling. File only for the case with a decision behind it, and put your diagnosis in the first line.

When algorithmic discovery is not coming back

Sometimes the honest answer is that the recommendation surfaces are not returning — because of a badge you will not appeal, or because the track never built the engagement those systems read. This is the part most advice in this niche gets wrong. Getting distributed is not the wall any more. Finding listeners is, and the routes that run through someone else's algorithm are exactly the ones a policy written a month ago can switch off. Our nobody listens to AI music page has the supply-side arithmetic.

So build the routes that do not depend on algorithmic discovery. Paid sync placement is the clearest: a track in a show, a game or an ad is a licence fee negotiated with a human, and it does not care whether Discover Weekly picks the song up. Played.fm's sync-deals route is built around pitching for exactly that, and the same platform lets you sell direct to listeners you already have. Our sync licensing page covers how those deals are structured, and streaming royalties has the per-stream numbers behind why one placement can outweigh a year of algorithmic plays.

None of that makes the zero less annoying. But four of these five causes are identifiable in an afternoon, and knowing which one you have is the difference between a week of support tickets and a week spent on something that moves.