Pre-save is usually presented as one of the simplest actions in music promotion.
An artist publishes a link. A listener clicks a button. The song is automatically added to their library on release day.
At least, that is how it appears in promotional descriptions.
In practice, an entire chain of additional steps can appear between clicking the link and completing the pre-save. The user may be asked to log in to Spotify again, approve permissions, move between several windows, or figure out why the link has opened inside the Instagram, Facebook, or TikTok browser.
We looked for a solution that would genuinely allow someone to press one button and complete the action. We considered different services, changed settings, tested different page designs, and tried paid features.
But we still did not find a complete solution.
Some options look better. Some require fewer steps. Some are designed more elegantly. But none of them can guarantee the simple action they were created to perform.
The User Is Already Logged Into Spotify — but the System Cannot See It
Most regular listeners use Spotify through an installed application. Whether on a phone or a computer, the app is already open and the user has been logged in for a long time.
It would seem logical that when someone clicks a Spotify pre-save link, the service should recognize this active session.
Usually, it does not.
A link from a social network often opens not in the Spotify app but inside the built-in browser of Instagram, Facebook, or TikTok. That mini-browser has its own separate session. It does not know that the user is already logged into the installed Spotify application.
In effect, several separate states exist:
- the user is logged into the Spotify app;
- the user is logged into the Spotify website in their regular browser;
- the user is logged into Spotify inside a social network’s embedded browser.
These states are not interchangeable.
A person may listen to Spotify every day and still appear “logged out” in the particular window where the promotional link opens.
That is the heart of the problem. It is not the absence of the app, or even an unwillingness to pre-save. It is the break between different authentication contexts.
What Happens After the Click
Instead of the expected action, the user often encounters the following sequence:
- They click a link in a social network.
- They arrive on an intermediary pre-save page.
- They click the Spotify button.
- They are taken into an embedded browser.
- They enter their Spotify credentials again or choose a login method.
- They approve access to their account for a third-party service.
- They are redirected back — if the transition works correctly.
- Only then do they receive confirmation that the pre-save has been completed.
To a music marketing specialist, this may look like a perfectly normal technical process.
To an ordinary listener, it is already too much.
This is especially true when the person is not a devoted fan, but someone who has discovered the artist in their feed for the first time and is willing to give them only a few seconds.
Every additional screen becomes another exit point.
Why Authentication Cannot Simply Be Removed
A pre-save is not an ordinary link to an upcoming song.
For a third-party service to add the release to someone’s library after it becomes available, it must receive permission to interact with that person’s Spotify account. This is handled through OAuth: the user is redirected to Spotify’s authorization system and asked to approve access.
In other words, some form of consent is genuinely necessary. A service cannot quietly modify a person’s library simply because they clicked an attractive button.
This is a reasonable security requirement. At the same time, it is precisely what makes a true pre-save technically more complicated than its name suggests.
Spotify’s documentation confirms that a third-party application must receive separate authorization before it can access account data and functionality.
Is a “One-Click Pre-Save” Really One Click?
Some music marketing platforms offer what they call a one-click pre-save.
The idea makes sense: take the listener out of the social network’s embedded browser, open the Spotify app, use the existing login session, and reduce the number of intermediary steps.
Feature.fm, for example, openly describes the problem of repeated logins inside embedded browsers and offers redirection into the Spotify app. However, the availability of particular features depends on the chosen subscription, while the link’s behavior may still vary according to the social network, device, operating system, and user settings.
A paid subscription provides more tools, more design options, better analytics, and additional settings. But paying for the service does not give the artist control over how Instagram, Facebook, TikTok, the browser, and Spotify transfer the user from one environment to another.
We confirmed this through practical testing.
The page can be made more attractive. Unnecessary buttons can be removed. A shorter route can be selected. Advanced functionality can be purchased.
But there is still no guarantee that the link will open, for every listener, in the exact environment where an active Spotify session already exists.
“One click” often means not a completed pre-save, but merely the beginning of the process.
Even an Improved System Still Loses Most Users
The marketing platforms’ own data reveal the scale of the problem.
Linkfire reported that after introducing a simplified Spotify pre-save process, its conversion rate increased from 21% to 32%. That is a significant improvement. But the same result can be viewed from another angle: even after optimization, roughly two-thirds of users still did not complete the action.
These figures were published by the service itself rather than by an independent study, so they cannot be treated as universal across all campaigns. Nevertheless, they demonstrate something important: even a well-configured, simplified system does not turn expressed interest into a guaranteed pre-save.
Linkfire also reports that Spotify performs better than other music platforms, yet the overall conversion rate still remains only slightly above 30%.
This creates a strange situation.
The industry calls the tool a “pre-save,” yet most people who reach the page with the intention of using it never complete the action.
Free and Paid Solutions Change the Presentation, Not the Architecture
DistroKid automatically creates a HyperFollow page for each release. This is convenient: the artist quickly receives a ready-made page, and after release day it becomes a standard link to streaming platforms.
Other services offer more flexible design, analytics, custom domains, retargeting pixels, email collection, and additional actions.
All of this can be useful for a marketing campaign.
But our task was much simpler:
A person presses a button and saves an upcoming release on Spotify without having to log in again, become confused, or navigate unnecessary transitions.
Existing solutions do not fully accomplish that task.
A free service is usually limited in its settings. A paid service allows the artist to create a more attractive page and collect more data. A one-click feature may shorten the route. But no subscription can remove the boundaries between the Spotify app, a regular browser, and the embedded browsers used by social networks.
The problem exists at a deeper level than page design.
The Cost of Friction for an Independent Artist
For a major artist, losing some users may be compensated for by the size of the audience.
For an independent musician, every person matters.
We invest time and money in creating the song, visual materials, and advertising. We then try to lead a potential listener toward one simple button. But at the final moment, the listener encounters a technical barrier that the artist cannot control.
The statistics may record a link click, but not a completed pre-save.
The person showed interest. The advertisement worked. The music caught their attention. But the technical chain failed to turn that interest into a completed action.
This is often interpreted as a lack of audience engagement. Yet some of the loss may have nothing to do with the music or the listener’s behavior. It may be caused by the poor architecture of the process itself.
What a Real Solution Should Look Like
A complete pre-save system should:
- recognize whether the Spotify app is installed;
- open the app itself instead of a social network’s embedded browser;
- use the user’s existing authentication;
- explain clearly and briefly what permission is being granted;
- provide unambiguous confirmation that the pre-save has been completed;
- work consistently across Android, iOS, and desktop computers;
- never require listeners to understand the difference between a browser session and an application session.
Ideally, this functionality should be built directly into Spotify and made available on the page of an upcoming release.
Spotify Countdown Pages move partly in this direction because the pre-save takes place within Spotify’s own environment. But this feature has limitations and is not a universal solution for every independent artist, every single, or every external advertising campaign.
As long as pre-save remains a function provided by third-party services, it will continue to depend on OAuth, browsers, deep links, social network policies, and differences between devices.
Our Conclusion
We did not find an ideal solution.
Not because we failed to understand the settings. And not because we were unwilling to pay for the necessary tools.
We tested different approaches and found that each solves only one part of the task.
One service provides an attractive page. Another offers analytics. A third provides deep linking. A fourth automatically transforms the link after release day. A paid subscription combines more features, but it does not eliminate the central technical divide.
Today, a Spotify pre-save is still not a single button. It is a small system of redirects, permissions, and incompatible login sessions.
It can be made slightly more convenient.
But it cannot yet be made genuinely simple, predictable, and consistent for everyone.
Perhaps honestly acknowledging this problem is more valuable than making another promise of a “seamless user experience.”
Because sometimes a technology looks complete only from the perspective of the person who created the button.
For the person expected to press it, the task is still unresolved.