A pre-save link is a page fans can visit before your release is out. In its full form, a fan authorizes a streaming service to add the release to their library the moment it goes live. In its simplest form, it collects an email and sends a reminder on release day. Both are useful. Only one of them touches a streaming account, and it matters that you know which one you are running.
What pre-save can actually do
A genuine pre-save, through a provider that supports it, does exactly one thing: on release day, the track or album appears in the fan’s library automatically. That first-day library add can contribute to early streams, which people believe influences editorial and algorithmic attention. Whether it does, and by how much, is not something any third-party tool can prove — the platforms do not publish how their systems weigh it.
What a pre-save cannot do is guarantee playlist placement, guarantee streams, or "boost the algorithm" in any way a vendor can demonstrate. A tool that promises those things is describing hopes as features.
The honest fallback: notify me on release day
Pre-save requires each streaming provider’s API approval, per tool. When that approval is not in place, the honest alternative is a release-day reminder: the fan leaves an email, and when the release converts, they get a message with the live links. It is labelled as what it is — an email, not a library add — and in exchange it gives you something a pre-save never does: a fan contact you own, with a consent record attached.
DropRoute ships this fallback by default and never displays a pre-save button for a provider that has not been verified. If you have seen tools claim pre-save for every service under the sun, know that several of those services have no public pre-save API at all.
Setting one up
A pre-release campaign on DropRoute takes a few minutes:
- Create a link, choose the pre-release type, and set the release date and timezone.
- Add the destinations you already know — the page shows them as "available on release day".
- Publish. The page collects reminders (and pre-saves where a provider is verified).
- On release day the page converts automatically: destinations resolve to live URLs, the countdown becomes buttons, and reminder emails go out. The URL never changes, so every poster and bio link keeps working.
When to launch it
Two to four weeks before release is the working range for most independent campaigns. Earlier than that and the fans who saved in week one have forgotten the song exists by release day; later and there is no time for the link to circulate. If your distributor gets the release into stores early enough that streaming services list it as "pre-release", launch the moment that listing exists — a pre-save against a listed release converts more reliably than one against a promise.
The one hard rule: the pre-save page must exist before any promotion that carries its URL. Posters, teaser videos, and pinned comments outlive their posting date, and every one of them should point at an address that will still be correct after release. This is why a converting page matters more than a pretty countdown: the URL you print in week one is the URL fans tap in month six.
Mistakes that cost real campaigns
- Making a new link for release day. The pre-save page should BECOME the release page at the release moment, automatically, at the same URL. Two links split your click history and strand every early share on a dead page.
- Setting the release time in the wrong timezone. "Midnight" is midnight somewhere specific; a page that converts at midnight UTC for a US audience converts in the early evening, mid-promotion.
- Collecting emails without consent records. If the reminder list has no evidence of what each fan agreed to, it is a liability, not an asset — and several jurisdictions treat it exactly that way.
- Believing a tool that claims pre-save "for every platform". Most services have no public pre-save API. A button that cannot do what it says erodes exactly the trust the campaign exists to build.
What to measure
Judge a pre-save campaign by what it verifiably produced: visits to the page, reminder signups (with consent), pre-save authorizations where real, and click-through after conversion. Day-one stream counts belong to your distributor dashboard, not your link tool — a link tool that reports "streams" without provider data is renaming clicks.
The comparison worth making is against your own last release: did more people arrive before release day, did more of them leave a contact, and did the release-day click-through hold up? Those three numbers, tracked release over release, describe whether your audience is growing in the only sense that compounds.
Questions that come up every time
Does a pre-save count as a stream? No. A pre-save is a library add. The stream happens only if the fan actually plays the release, and that play is counted by the streaming service, reported through your distributor. The two numbers usually differ a lot, and that difference is normal.
Does pre-save exist on Apple Music? Apple’s equivalent is called pre-add, and it runs through a different mechanism (MusicKit, with a user token granted in the browser) than Spotify’s API flow. Tools that show an Apple pre-add button without having built that flow are showing a button that cannot work. DropRoute declines to show it until the flow exists — the reminder fallback covers Apple listeners honestly in the meantime.
Can a fan undo a pre-save? Yes — they can revoke the authorization from their streaming account’s connected-apps settings, or simply remove the release from their library after it lands. Treat the authorization count as intent, not a contract.
How many pre-saves is a good number? Measured against your own audience: a useful rule of thumb is to compare pre-save-plus-reminder signups to your typical first-week listener count from the last release. Ten committed contacts from a hundred-listener audience is a strong signal; a thousand from a million-listener audience is not. Absolute benchmarks that ignore audience size are noise.