Treat every playlist-placement offer as a compliance and data-quality risk until it earns your trust. Spotify explicitly prohibits selling playlists or accepting compensation to influence playlist contents in its User Guidelines, and it warns that third-party services that guarantee streams are scams that can lead to removals and withheld royalties. Vet the playlist using public signals (concept, update history, curator identity) and then validate using first-party analytics (source of streams, playlist sources, geography, saves). If you see abnormal spikes or suspicious behavior, stop new outreach, pause any paid spend that would amplify the problem, document everything, and escalate to your distributor or the platform. Prevention is an SOP: pre-vet, monitor daily during release week, and only use official pitching and marketing tools.
Warning If money changes hands for "guaranteed placement" or "guaranteed streams," treat it as high-risk by default (see Spotify’s User Guidelines and third-party services guidance).
Policy baseline (what platforms actually prohibit)
Use Spotify as the strictest "floor," then apply the same standard everywhere.
- Spotify’s User Guidelines prohibit selling a playlist or taking compensation to influence playlist contents. Spotify also documents artificial streaming and warns against third-party services that guarantee streams.
- Apple warns in Apple Music for Artists to protect yourself from streaming manipulation, including methods that use bots and fake accounts.
- YouTube’s fake engagement policy states artificial traffic may not be counted and can lead to enforcement actions.
- TikTok explains how it counters deceptive behaviour and its ads policies prohibit deceptive practices, including fake engagement services.
Practical posture: if someone offers you a predictable outcome (streams, placements, followers) in exchange for payment, treat it as a compliance risk first, and a marketing opportunity second.
25-point playlist vetting checklist (go/no-go)
Use this checklist before you pitch, and again after you get any placement, to decide whether a playlist is safe enough to engage.
Playlist quality (public signals)
- Clear concept: The playlist has a tight, stable sound (genre + mood) rather than keyword soup.
- Cohesive tracklist: The songs make sense together, not random genre whiplash.
- Human update pattern: Adds and removals look periodic and selective, not bulk swaps every day.
- Reasonable density: The playlist is not so long that any add is effectively invisible to listeners.
- Fit evidence: Your track matches what was added recently, not just the playlist title.
- Real audience intent: Comments, social proof, or community indicators exist (when available) without looking manufactured.
Curator legitimacy (identity and incentives)
- Identity is consistent: Curator name, handle, and brand are consistent across platforms.
- Contact is professional: The email domain looks legitimate, and the message is not a copy-paste blast.
- No "algorithm boosting" claims: No one can promise algorithmic prioritization in exchange for payment, Spotify warns against services that promise outcomes like streams or placements (see third-party services guidance).
- No guaranteed outcomes: They do not guarantee streams, saves, or placements.
- They can explain their audience: Curator can describe who listens and why the playlist exists.
- They disclose how submissions work: You can tell whether this is editorial taste, community submissions, or a paid submission marketplace.
Traffic patterns (first-party analytics checks)
These checks use first-party analytics, not proprietary tooling. Spotify for Artists is the most useful for diagnosis because it exposes Source of streams and the constraints of Seeing playlists your music is on.
- Source sanity: Streams attributed to playlists line up with what you can see in
Source of streams. - Playlist visibility: If you have a big spike but the playlist never appears, treat it as a risk signal (Spotify only shows top playlists and has minimum listener thresholds for displaying playlist data).
- Geo plausibility: Listener geography matches the playlist's claimed audience and language.
- Save behavior: Programmed streams convert into saves at a rate that is directionally consistent with the track's own baseline, not near-zero (Spotify documents how it counts saves).
- Playlist adds vs streams: You see meaningful playlist adds and library behavior, not only streams.
- Active vs programmed shift: After a placement, you see some lift in active sources (profile, listeners' playlists, library) rather than only programmed contexts.
- Timing looks human: The spike is not perfectly flat hour-by-hour or day-by-day with no natural variance.
- No obvious "ghost lift": You do not see huge streams without any supporting signals (new listeners, saves, followers, or repeat listening).
Contract terms and payment risk
- No pay-for-placement language: No "pay per add," "pay per stream," or "pay per follower" framing.
- No credential requests: Never share artist login credentials or grant account access to third parties.
- Payment transparency: If there is a fee, it is for a legitimate service with clear deliverables (for example, content production), not for an outcome.
- Refund terms: Any paid relationship has written terms and an invoicing trail.
- Reporting is verifiable: If they offer reporting, it is anchored in first-party screenshots or platform exports, not a made-up dashboard.
"If this, then that" response plan
Use this as an operator SOP for release week and for any catalog track that suddenly spikes.
1) If the outreach message includes guarantees, stop Do not negotiate. Archive the message and move on. Spotify explicitly warns against third-party services that guarantee streams.
2) If you are unsure pre-placement, ask two clarifying questions Ask (a) who their audience is, and (b) how submissions are reviewed. If you cannot get a straight answer, treat it as a no-go.
3) If you suspect botted traffic, pause amplification Do not run paid campaigns that would train ad platforms on corrupted engagement. See Google’s guidance on invalid traffic and Meta’s notes on cracking down on spammy content.
4) Document the incident while data is fresh Capture playlist URL, timestamped screenshots, messages, invoices, and first-party analytics screenshots (for example
Source of streams, playlists view, geography, saves).5) Escalate through your distributor first Your distributor or label services partner has the most direct channel for platform escalations and policy investigations.
6) Keep monitoring for downstream effects Watch for removals, reporting discrepancies, or eligibility issues in marketing tools. Spotify documents artificial streaming and warns against guaranteed-stream services.
Sample incident log template (copy/paste)
Use this to keep internal notes consistent across a team.
| Field | What to capture |
|---|---|
| Track | Title, artist, ISRC/UPC (internal), release date |
| Suspected source | Playlist name + URL, curator name, contact channel |
| Timeline | First anomaly time (UTC), peak time (UTC), when you noticed |
| Evidence | Screenshots of messages, invoices, and analytics |
| Spotify for Artists | Source of streams, playlists view, top countries, and saves behavior (see how Spotify counts saves) |
| Action taken | Paused spend, outreach stopped, distributor contacted, report filed |
| Outcome | Removal, royalty hold, distributor warning, "no issue found" |
Downstream risks (why fraud hurts more than one track)
Fraudulent playlist traffic is not only a Spotify problem. It creates downstream damage across your marketing stack:
- Distributor risk: Artificial streaming investigations can trigger fines, takedowns, or account actions depending on distributor policy (see Spotify’s artificial streaming guidance).
- Optimization corruption: Ad platforms can treat bot-like behavior as invalid or deceptive engagement, which breaks learning and attribution (see Google’s invalid traffic and Meta’s spam crackdown).
- Bad audience insights: Geography and source-of-streams data becomes unreliable, which leads teams to target the wrong markets or playlist niches.
Safe alternatives (how to get playlist exposure without risking the catalog)
This is the short list that scales and stays policy-safe.
Use official editorial pitching tools. Spotify documents pitching music to playlist editors and promoting music on Spotify inside
Spotify for Artists.Build owned playlists and listener funnels. Curate label and artist playlists that genuinely match the catalog, then drive listeners through real content and ads.
Use paid media to earn playlisting, not buy it. The goal is to drive real listeners who save and add to their own playlists, which then shows up as active signals over time (see Source of streams and how Spotify counts saves).
Partner with creators on content, not placements. Pay for content deliverables with usage rights, and let playlists be an earned side effect, not the purchased product.
What to do if it already happened
If a team already paid for a placement, the priority is damage control, not defending the decision.
- Stop additional payments and do not "double down" to smooth the curve.
- Ask for removal from any playlists you can identify, in writing.
- Log the incident and notify your distributor with the evidence you collected.
- Watch for artificial streaming messaging, reporting discrepancies, and sudden eligibility or visibility changes (see Spotify’s artificial streaming guidance and track monetization eligibility).
- Re-baseline your measurement for the track, and treat the period as contaminated when evaluating ROI.
Measurement (what to monitor during release week)
If you have to pick only three checks, use these:
- Source of streams: whether lift is coming from editorial, algorithmic, listener playlists, or active sources (see Source of streams).
- Playlists view: which playlists are contributing listeners, with the caveat that Spotify limits playlist reporting (see Seeing playlists your music is on).
- Saves behavior: how Spotify counts saves, and whether the placement converts into intent actions (see how Spotify counts saves).