Spotify Pre-Save Campaigns Explained: How Day-One Saves Shape Release Radar

What a pre-save actually is

Before you can run a pre-save campaign, it helps to understand what the mechanism actually does, and what it does not do.

A pre-save is an authorization, not a direct action inside Spotify. When a listener clicks your pre-save link, they are directed to a Spotify OAuth login screen. By completing that login, they grant a third-party tool, the platform you used to create the pre-save link, permission to save your upcoming release to their Spotify library on release day. The save does not happen at the moment of authorization. It happens automatically on the release date you specified when you set up the campaign.

This means you cannot create a pre-save link natively inside Spotify's artist tools. Spotify does not offer a built-in pre-save feature for artists. The pre-save mechanism depends on a third-party platform (such as Feature.fm, DistroKid's HyperFollow, or similar tools) that has integrated Spotify's OAuth API. As Feature.fm's pre-save documentation explains, the pre-save tool handles the authorization process and then fires the library save on release day on behalf of each listener who authorized it.

This is worth understanding clearly because it shapes how you talk about pre-saves to your audience. You are not asking listeners to save your song now. You are asking them to authorize a future save, which is a lower-friction ask in some ways (the listener does not need to remember to come back on release day) but requires a bit more trust (they are logging in through OAuth with a third party).

How the day-one save connects to Release Radar

The reason artists run pre-save campaigns in the first place is the relationship between release-day saves and Release Radar.

Release Radar is a personalized playlist Spotify generates for each listener, updated every Friday, featuring new music from artists that listener follows, has recently saved, or has engaged with. As Spotify for Artists' documentation on how releases reach listeners describes, Release Radar is driven by the listener's own history and engagement signals, not by editorial decisions, and not by anything the artist can directly control inside Spotify.

When a pre-save fires on release day, it generates a save event in Spotify's system. A save is one of the higher-weighted engagement signals the platform tracks; it indicates a listener considered the track worth keeping in their library rather than simply streaming and moving on. When that save happens on or near release day, which is exactly what a pre-save campaign produces for every listener who authorized it, it lands in the critical early window when Spotify's systems are forming an initial impression of how a release is performing.

For a listener who pre-saved your release, the save event on release day improves the likelihood that the track will appear in their personal Release Radar playlist that Friday. The save also adds the track to their library, where it may surface in their Liked Songs or Daily Mixes. The concentration of saves on day one, across all your pre-savers simultaneously, is what gives a pre-save campaign its algorithmic relevance.

What pre-saves do not do is expand your audience. Pre-savers are people who were already aware of and interested in your release; they clicked your link before it was live. The campaign is a mechanism for converting that existing interest into a concentrated day-one engagement signal, not a way to reach new listeners who have never heard of you.

The Release Radar mechanism in practice

To be precise about how Release Radar works: it is a personalized playlist, so its behavior varies by listener. Whether your release appears in a specific listener's Release Radar depends on several factors beyond the pre-save: whether they follow you on Spotify, the recency of their engagement with your catalog, how many competing new releases are relevant to them that week, and how Spotify's personalization model weights your release for that individual.

According to Spotify for Artists' release eligibility documentation, tracks are eligible for Release Radar if they have been released within the prior 28 days, the artist has not been excluded from the algorithm, and the listener has a relevant relationship with the artist. A pre-save creates a save event and a library addition, both of which are relevant signals for that listener's relationship with your catalog. It does not override the other eligibility factors.

The practical implication: a listener who pre-saved your release but had never engaged with your catalog before is less likely to see it in Release Radar than a listener who pre-saved and was already a regular listener. The pre-save amplifies an existing relationship. It does not create one from nothing.

Why day-one listening behavior matters more than the pre-save number

The pre-save number is a leading indicator, not the outcome that matters. What happens after release day is more consequential than how many people authorized a pre-save.

Spotify's algorithmic systems, including Discover Weekly, Radio, and Autoplay, respond primarily to how listeners behave with a track after they start playing it. Save rate, completion rate (how much of the track a listener completes before skipping), and return-play behavior are among the signals that indicate a track is resonating with its audience.

A large pre-save number that converts to low completion on release day sends a different signal than a smaller pre-save number where most listeners complete the track and a meaningful share saves it after listening. The pre-save campaign concentrates engagement on day one. The quality and relevance of the music, delivered to an audience with a genuine interest in it, is what determines whether that initial engagement signal extends into sustained algorithmic promotion.

This is why the brief window between release day and the first Friday Release Radar update matters. If day-one listening behavior is strong (completions are high, saves from first-time listeners are accumulating), the track enters that Release Radar cycle in a stronger position than it would have without the concentrated early signal.

Building the campaign

A pre-save campaign has two practical phases: setup and distribution.

Setup. To create a pre-save link, you need a confirmed release date in your distributor's system and a pre-save tool that supports Spotify OAuth. Most major distribution platforms have either a native pre-save feature or a partnership with a pre-save tool. DistroKid's HyperFollow, for example, automatically creates a pre-save link for every upload. Feature.fm, Linkfire, and similar platforms offer pre-save functionality with additional options for custom landing pages, email capture, and analytics. As Feature.fm's pre-save documentation explains, the setup requires connecting the tool to your upcoming release with the correct release date so the save fires at the right time.

Distribution window. The recommended timing for a Spotify pre-save campaign is to create the link 2 to 3 weeks before your release date and to concentrate promotion in the 7 to 10 days immediately before release. This window is short enough that the release feels imminent, which increases conversion because listeners do not have to wait long to hear what they just pre-saved, but long enough to distribute the link across your channels meaningfully.

Channels for distribution include your Instagram bio and Stories, your TikTok bio, any email list you maintain, your Spotify artist page (the "Artist Pick" feature can surface your pre-save link to existing followers), and any YouTube community posts or video descriptions. The pre-save link is most effective when placed wherever engaged listeners already look for information about your releases: your existing audience, not a cold audience you are trying to reach for the first time.

Honest framing: what a pre-save campaign can and cannot do

A pre-save campaign is a foundation for a release, not a guarantee of outcome. Here is a clear-eyed summary of what the mechanism does and does not deliver:

What it does: Concentrates saves on release day for listeners who authorized the pre-save. This creates a day-one engagement signal that is relevant to Release Radar eligibility and potentially to Spotify's early assessment of the release's performance. It also eliminates the friction of asking listeners to remember to save the track on release day.

What it does not do: Generate new listeners. Reach people who have never heard of you. Guarantee editorial playlist consideration (that is a separate process handled through Spotify for Artists' pitch tool, with no connection to pre-saves). Produce algorithmic promotion on its own without strong downstream listening behavior.

The honest version is that a pre-save campaign is useful (it concentrates existing interest into a high-quality day-one signal), but its value depends entirely on whether the listeners you recruit are genuinely interested in the music, and whether the music retains them after they listen. A pre-save from a listener who skips after 15 seconds contributes less than no pre-save from a listener who discovers the track organically and listens to completion.

Build the pre-save campaign as one element of a release plan that includes consistent audience-facing promotion before, on, and after release day. It is not a substitute for that plan.

A note on third-party pre-save tools

Because pre-saves require a listener to authorize through Spotify's OAuth system, the listener is trusting a third-party tool with access to their Spotify account permissions. Choose tools with established track records and clear privacy policies. Feature.fm, DistroKid's HyperFollow, and Linkfire are among the platforms that have published documentation on how they handle OAuth permissions and what data they collect. Transparently communicating to your audience what they are authorizing, a library save on a specific date and nothing more, is a reasonable practice that helps listeners feel confident clicking the link.

---

FTSMusic analysis is based on anonymized aggregate artist data, internal campaign observations, and publicly available industry documentation. Individual outcomes vary by catalog, genre, audience quality, and release strategy.