Step 1: define the real goal of the placement
Playlist pitching can support multiple goals, but not all of them are realistic from a single placement.
| Goal | What "success" looks like in first-party metrics |
|---|---|
| Delivery | Clear lift in playlist-attributed streams/listeners (not your only goal) |
| Intent | Lift in saves and playlist adds relative to the track's own baseline |
| Durable demand | Follower growth and more listening from active sources over time |
| Audience movement | New active and reactivated listeners increasing, not just passive plays |
If your only goal is "more streams," you will over-credit low-quality placements.
Step 2: measure the right Spotify for Artists metrics
Spotify exposes enough first-party signals to build a practical scorecard.
Delivery: where streams came from
Use Source of streams to separate editorial, algorithmic, listener playlists, and active sources (see Source of streams).
Key interpretation:
- A placement can deliver streams without creating durable demand.
- Durable demand shows up as increased listening from active sources (profile, library, listeners' playlists), not only programmed contexts.
Intent: saves and playlist adds
Spotify documents how it counts saves, and saves are one of the cleanest "intent" actions you can track inside Spotify for Artists.
Track changes in:
- Saves (and derived save rate if you compute it internally)
- Playlist adds
- Any lift in track engagement during the placement window
Demand: followers and repeat listening proxies
Spotify documents listener and follower stats and how follower behavior relates to future listening.
Track:
- Net follower growth during and after the placement
- Whether listeners return through active sources after the placement ends
Audience movement: segments and recency
Spotify documents audience segments (for example new active, previously active, and reactivated) and how those windows work.
Use segments to answer: did this placement attract people who will be in the audience again next month?
Step 3: build a clean measurement window (pre, during, post)
The simplest repeatable workflow is a three-window analysis.
1) Pre window: establish a baseline Pick a baseline window (commonly 28 days) and capture daily streams/listeners, saves behavior, and source mix. Keep notes on other marketing running (ads, PR, creator posts) so you do not misattribute lift.
2) During window: log the placement and watch conversion Log the date added, playlist type, and the markets you believe the playlist reaches. Monitor daily lift, then check whether saves, playlist adds, and follower growth move in the same direction.
3) Post window: test persistence Keep measuring after the placement ends. The key question is whether listening persists through active sources and whether audience segments grow, not whether the spike looked impressive on a chart (see Source of streams and audience segments).
Step 4: estimate incrementality (what you can and cannot claim)
You cannot prove causality from playlist data alone. You can still make better decisions by using proxy methods:
- Trend break: Did the track’s trajectory change meaningfully at the time of the placement?
- Geo split: If the playlist is market-skewed, do you see lift in that market more than elsewhere?
- Track control: Compare behavior against another track that did not receive placement during the same period.
Warning Do not attribute all growth to playlists when other marketing is running. Treat playlists as one variable in a multi-channel release system.
Step 5: flag "empty streams" and fraud risk early
Common patterns that signal low quality:
- Streams spike from programmed contexts, but saves and playlist adds do not move.
- Geography looks implausible for the playlist’s audience.
- Lift collapses immediately after removal with no persistent active-source listening.
If you used a third-party service that promised outcomes, treat the data as suspect and prioritize catalog safety (see Spotify’s guidance on third-party services that guarantee streams and artificial streaming).
Revenue Benchmarks: What 1,000 Streams Actually Pays
When calculating ROI, you need concrete revenue-per-stream figures. Playlist pitching generates streams across multiple surfaces, and each pays differently.
Per-platform revenue inputs
Use the current royalty dashboard instead of a frozen table. The most useful pages for playlist ROI are Spotify, Apple Music, Amazon Music, and YouTube Music and Art Tracks.
Individual payouts vary by listener geography, subscription type, and platform-specific pool calculations.
Applying Revenue Data to Your Scorecard
When you fill in the placement scorecard below, multiply your observed delivery (stream lift) by the relevant platform rate to convert streams into estimated revenue. A placement that generates 25,000 incremental Spotify streams and 3,000 cross-platform Apple Music streams produces:
- Spotify: 25,000 x $3.02/1K = $75.50
- Apple Music: 3,000 x $5.43/1K = $16.29
- Combined: $91.79 from a single placement event
Compare this against your pitching costs (time, service fees, ad spend during the editorial window) to calculate true placement ROI. Factor in the save-driven long tail: streams from saved tracks continue generating revenue at these same rates for months after the placement ends.
One-page placement scorecard (template)
Use one row per placement event. Add a second row for "post window" notes after the placement ends.
| Field | What to write |
|---|---|
| Track | Title + ISRC (internal) |
| Playlist | Name + URL |
| Placement type | Editorial, algorithmic, listener playlist, unknown |
| Date added / removed (UTC) | YYYY-MM-DD / YYYY-MM-DD |
| Observed delivery | Lift in playlist-attributed streams/listeners (directional) |
| Conversion quality | Saves behavior, playlist adds, follower delta (directional) |
| Persistence | Did active sources lift post-placement? |
| Audience movement | New active / reactivated movement (directional) |
| Risk flags | Any fake-engagement signals or policy concerns |
| Decision | Keep pitching, adjust targeting, or stop |
Worked example (example only, fictional numbers)
This is a structural example only, not a benchmark.
| Field | Example |
|---|---|
| Track | "Example Track" (ISRC: internal) |
| Playlist | "Indie Chill Finds" |
| Date added / removed | 2026-03-01 to 2026-03-10 |
| Observed delivery | Streams up vs baseline during placement |
| Conversion quality | Saves up vs baseline, followers slightly up |
| Persistence | Active-source listening stayed higher for 2 weeks after removal |
| Decision | Continue outreach to similar playlists, repeat with next single |
One placement vs 10+ placements per month
If you only have one placement, focus on clean logging and post-window persistence. Your main goal is learning whether this playlist lane creates durable demand.
If you run 10+ placements per month:
- Standardize the scorecard for every placement.
- Export platform data where possible and keep a consistent calendar of placements and campaigns (see Spotify’s exporting data guide).
- Review placements in batches so you do not over-react to a single spike.
Common pitfalls (and how teams fool themselves)
- Confirmation bias: A spike feels like success, so teams stop questioning quality. Force a post-window review before labeling a placement "worked."
- Mixing windows: Misaligned time zones and reporting delays create fake "start dates." Log in UTC and align analysis to Spotify’s counting rules (see time zone for stats and when stats update).
- Ignoring data limits: Spotify does not show every playlist and has reporting limits. "Not listed" does not mean "no playlists" (see Seeing playlists your music is on).