Apple pre-adds and Spotify pre-saves both exist for one reason: capture intent before release day, then convert that intent into day-one listening.
The difference is how each platform turns that intent into behavior. Understanding these mechanics helps you allocate budget and design landing pages that actually convert.
Side-by-side comparison
| Feature | Apple Music pre-add |
Spotify pre-save |
|---|---|---|
| What happens | Release added to library automatically on drop | Release saved to library on drop |
| Where it lives | Apple Music library | Spotify library |
| Day-one behavior | Appears in library, ready to play | Appears in library, may trigger Release Radar |
| Algorithmic signal | Indirect (via listening behavior) | Direct (informs Release Radar inclusion) |
| OAuth required | Yes | Yes |
| Best for | Apple-heavy audiences, genre/region dependent | Spotify-heavy audiences, algorithmic play |
| Tracking | Via Linkfire or landing page events | Via Spotify for Artists pre-save links |
Apple Music pre-add
Pre-add is a library commitment inside Apple's platform. It is most valuable for:
- Apple-heavy audiences (certain genres, US market, Japan)
- warm fans who will actually follow through on release day
The key difference: Apple does not have an equivalent to Release Radar. The pre-add converts into library behavior, but whether Apple's discovery surfaces pick up the track depends on downstream listening signals, not the pre-add count itself.
Pre-adds do not directly trigger algorithmic placement. They position the release in the listener's library so it is available on drop day. The value comes from what happens next: if pre-add users actually listen, complete the track, and add it to playlists, those signals feed Apple's recommendation system.
Spotify pre-save
Pre-save is an intent signal that can support day-one library behavior on Spotify and can be paired with Spotify's editorial and algorithmic surfaces.
The advantage: Spotify's algorithm uses pre-saves as one input for Release Radar inclusion. A strong pre-save campaign can directly influence algorithmic reach in the first week.
Pre-saves also help with editorial pitching. If you pitch through Spotify for Artists and your track has strong pre-save numbers, that signals audience anticipation to the editorial team. It is not a guarantee of placement, but it provides supporting evidence.
The risk with pre-saves is that they can become a vanity metric. If you drive pre-saves from cold traffic that does not actually listen on release day, the gap between pre-save count and actual engagement hurts more than it helps.
The OAuth friction problem
Both pre-adds and pre-saves require OAuth authentication. The user must connect their streaming account to your landing page service to complete the action.
This friction reduces conversion rates compared to simple link clicks. Expect 20-40% drop-off between landing page visit and completed pre-save/pre-add action. The exact rate depends on how warm your traffic is and how clean your landing page flow is.
To minimize friction:
- Use a landing page service with smooth OAuth flows (Linkfire, Feature.fm, ToneDen)
- Keep the page focused on one action, not a menu of options
- Make the value proposition clear before asking for the commitment
What to prioritize
Prioritize based on audience reality:
Apple-heavy audience: Lead with pre-adds. This typically means US hip-hop, pop, and country releases where Apple's market share is closer to Spotify. Japan is also Apple-heavy.
Spotify-heavy audience: Lead with pre-saves. This is the default for most global releases, especially in markets where Spotify dominates (Latin America, Europe, emerging markets).
Label release: Run both, but do not split your landing page CTA evenly. Pick the primary CTA based on your audience data, then offer the other as a clear secondary option.
Measuring success
Pre-save and pre-add counts are leading indicators, not outcomes. Track what happens after release:
- Pre-save to stream conversion: What percentage of pre-savers actually stream on release day?
- Completion rate: Do pre-save users finish the track or skip early?
- Library add behavior: Do pre-add users leave the track in their library or remove it?
If your pre-save numbers are high but release day engagement is weak, your campaign is attracting the wrong audience. Tighten targeting and focus on people who actually want to hear the music.
Campaign timing
Start pre-save/pre-add campaigns 2-4 weeks before release. This gives enough time to build momentum without losing urgency.
- Week 4-3: Announce the release, launch pre-save landing page, target core fans
- Week 2: Expand to lookalike audiences, increase budget
- Week 1: Final push, retarget non-converters with urgency messaging
- Release day: Shift messaging from "pre-save" to "listen now"
Do not run pre-save campaigns indefinitely. Set a clear end date and transition to release day creative.