streaming

They look like the same button. They do measurably different things to a release.

Every release campaign asks you to pre-save. It is worth knowing what that click does, because it does more than it looks like it does.

You can listen to our full playlist which contains the artist's music, and know more about the artist's work by scrolling down the page.

PLAYLIST

Three Buttons, Three Mechanisms

Pre-save, pre-add and waitlist look interchangeable and do measurably different things, and the differences matter when planning a release.

A pre-save authorises a service to add a release to a listener's library automatically on release day. A pre-add is the equivalent within a different platform's ecosystem, with its own behaviour. A waitlist collects interest without any automatic action.

Each produces a different signal to the platform and a different experience for the listener, and treating them as one thing leads to campaigns that miscount their own results.

Pre-Save Buys Day-One Activity

The value of a pre-save is that it converts interest accumulated over weeks into activity concentrated on release day.

When the record appears, every pre-saved account receives it simultaneously, which produces a spike of library adds and, usually, plays within the first hours. That spike is exactly the early signal recommendation systems respond to.

That is the actual mechanism: not the saves themselves but the concentration. The same number of saves spread across a fortnight would produce far less algorithmic response than all of them landing at once.

Pre-save also front-loads a signal the platforms read as organic. A large number of library adds in the first hours looks like discovery rather than marketing, which is precisely why it influences algorithmic distribution.

The Permission Cost Is Real

Pre-save campaigns require the listener to grant a third-party service access to their account, and that access is frequently broader than the task requires.

Many pre-save tools request permissions to modify libraries, follow artists and read listening history, and retain that access indefinitely unless revoked. Listeners have become noticeably more reluctant as this has become better understood.

That reluctance is a genuine conversion cost. A campaign asking for extensive permissions converts worse than one asking for an email address, and the difference has grown.

Follows May Matter More Than Saves

A frequently overlooked detail is that many pre-save flows also add an artist follow, and the follow is often worth more than the save.

A follower receives notification of every subsequent release automatically, which is a durable channel. A save applies to one record and does nothing for the next one.

Campaigns that optimise purely for save counts while treating the follow as incidental are undervaluing the more useful outcome, and the reporting on most tools encourages exactly that mistake.

Follow counts also carry weight in editorial consideration, since an artist with a substantial following demonstrates an audience that will engage with a placement rather than skip past it.

Waitlists Trade Automation for Ownership

Collecting an email address or a phone number instead of a platform permission gives up the automatic day-one action and gains something more durable.

A contact list belongs to the artist and works regardless of which platform a listener uses, which platform changes its policies, or whether the listener still uses the service they authorised two years ago.

For artists building long-term, that ownership is usually worth more than a single release-day spike, and the strongest campaigns collect both rather than choosing.

What to Actually Do

The practical approach is to be clear about which outcome each mechanism produces and to run them for their specific purposes.

If the goal is algorithmic momentum in the first hours, pre-save is the tool, and the campaign should run long enough to accumulate meaningful numbers. If the goal is a channel that survives beyond this release, collect contacts directly.

Measuring them against each other is the common error. They are not competing tactics, they produce different assets, and a release plan generally needs both.

Running both is straightforward: the pre-save flow can collect an email address on the confirmation step, which costs one extra field and converts a one-release asset into a permanent one.