Pre-Add 대 Pre-Save: 다른 신호들 [2026]

Apple의 pre-add와 Spotify의 pre-save는 모두 한 가지 이유로 존재합니다. 바로 발매일 전에 의도를 포착하여 그 의도를 첫날 청취로 전환하는 것입니다.

차이점은 각 플랫폼이 그 의도를 행동으로 전환하는 방식에 있습니다. 이러한 메커니즘을 이해하면 예산을 할당하고 실제로 전환되는 랜딩 페이지를 설계하는 데 도움이 됩니다.

나란히 비교

Apple Music pre-add

Pre-add는 Apple 플랫폼 내의 라이브러리 약정입니다. 다음의 경우 가장 유용합니다.

• Apple 중심 오디언스 (특정 장르, 미국 시장, 일본)
• 발매일에 실제로 이행할 열성적인 팬

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는 Spotify에서 첫날 라이브러리 행동을 지원할 수 있으며 Spotify의 편집 및 알고리즘 영역과 결합될 수 있는 의도 신호입니다.

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:

• 사용 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 국가 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.