THE TAKEAWAY

A page of listening destinations helps fans choose a service. A pre-save requires a provider-supported action before release. Links2 can organize verified music links or link to an external pre-save page; it does not perform the pre-save itself.

Music promotion tools use terms such as smart link, release page, pre-save, and player for different parts of the listener journey. Before choosing a tool, write down what the fan should be able to do today. A recording that is already available needs a listening route; an unreleased recording may need a supported pre-save action or simply clear release information.

Separate three jobs that can appear on the same page

A multi-service release page collects destinations so a listener can choose where to hear or buy a recording. An embedded player offers supported playback on the page. A pre-save is a separate provider-supported process intended to save an upcoming release to a listener’s library when it becomes available.

The label ‘smart link’ alone does not establish which of those jobs a tool performs. Check whether destinations are added manually or discovered automatically, whether a pre-save is actually supported for your release, and which actions require the listener to authorize another service.

Match the fan’s task to the destination

  • ‘Hear the single now’ → a verified released recording or listening-choice page.
  • ‘Pre-save the next single’ → a working provider-supported pre-save flow.
  • ‘Preview the sound’ → an available player or authorized public preview.
  • ‘Find release details’ → an accurate date and useful information, even if no pre-save exists.

Verify the exact pre-save page you were given

For example, DistroKid says the HyperFollow pages created for its uploads can collect Spotify pre-saves and update with streaming links when the release goes live. Its documentation distinguishes those pages from separately created HyperFollow pages that do not have the same pre-save or automatic-update functionality. This is a reason to inspect the actual page, rather than assume every page from a brand behaves alike.

Read the action and permission prompts a listener sees. Check the artist, release, date, and selected service. Do not describe an ordinary follow button, mailing-list form, or unreleased service URL as a confirmed pre-save. Product behavior and eligibility can vary, so verify your provider’s current instructions for the release you are promoting.

DistroKid: which HyperFollow pages support pre-saves and release updates ↗

Use Links2 to organize the release journey

Links2’s musician page can contain a manually configured release card with artwork and listening or buying destinations. You supply and verify those URLs. Supported players can be included where appropriate. Automatic cross-service matching and native pre-save processing are not part of this workflow.

If your distributor or promotion provider supplies a working pre-save page, add it as an ordinary link and label it accurately. That button opens the external provider; it does not connect Links2 to the listener’s streaming account. Keep a useful current release or show link available for visitors who are not taking the pre-save action.

See the manual listening-link and release-card setup in the musician release page walkthrough.

Plan the change from upcoming to available

Keep a checklist for release day: verify availability on each service, update the status line, replace any expired pre-release action, and test the published page from your shared social address. Even if an external provider promises automatic updates, check that the resulting links identify the correct recording.

A Links2 page does not automatically rewrite your manually supplied destinations when a release launches. Edit and publish the changes yourself. Preserve the page’s shared address where practical so older posts still lead to useful information, and avoid leaving a ‘coming soon’ message after the music is available.

Use the before, during, and after release checklist ↗

Keep pre-save, click, and listening counts distinct

Use the pre-save provider’s own records for the actions it confirms. Use Links2 for measured page activity and destination clicks, and the music services for their available listening reports. A click on an external pre-save button does not prove the visitor completed authorization or that a save later occurred.

Record the measurement source and date range when comparing a campaign. Do not treat pre-saves as guaranteed future streams or assume a change in listening was caused by a particular page edit. The practical question is whether the intended action works and whether the available evidence supports the conclusion you are drawing.