Campañas de pre-save: qué hacen y cómo ejecutarlas

Define what the current pre-save tool actually does

Source scope: Getting music on Release Radar; Promote your music with Apple Music marketing tools. Platform-, provider-, and territory-specific statements below are scoped to these 2026-07-11 checks and the complete bibliography.

A pre-save campaign gives an eligible listener a pre-release action that a particular platform, distributor, or campaign provider may fulfill when the release becomes available. Behavior differs: destination platforms, permissions, follow behavior, data returned, release matching, and edit handling are provider-specific. Verify the live documentation and consent screen for the tool you choose.

A pre-save is not a stream, purchase, editorial pitch, playlist placement, or proof of future listening. Describe the action in the same terms the user sees. Do not promise an algorithmic benefit unless a current authoritative source explicitly supports that scoped claim.

Prepare the release and landing page

Confirm final artist and release identifiers, distributor state, intended date, artwork rights, territory, canonical post-release destination, privacy notice, support, and change owner. Generate the campaign only after the provider can reliably match the release.

The page should identify the artist and release, explain the action and requested permissions, link the relevant terms/privacy information, offer support, and work on mobile and signed out as far as the provider permits. Avoid preselected marketing consent or vague bundling. If an email or other direct contact is optional, distinguish it from the platform authorization.

Test:

1. each supported platform and territory available to the team;
2. account authorization, permissions, cancellation/revocation;
3. confirmation and error states;
4. release mapping and date changes;
5. mobile, accessibility, analytics/consent, and support;
6. the post-release redirect or destination.

Run and close the campaign

Create content that explains why the release matters, using the pre-save as one optional next step. Give people a normal profile or release path if they do not want authorization. Partners need approved copy that does not overstate the action.

Monitor provider state and support. If the release identifier or date changes, follow the provider's process and pause promotion until the page is reverified. On release, check fulfillment and the final destination. Update or retire the landing page so old links remain truthful.

Measure completed provider-reported actions, page errors, support, optional valid consent, and post-release destination health. Do not translate those counts into guaranteed listeners.

How Bandruption can help

Bandruption can connect a release plan, current artist profile, approved content, and follow-up around an independently verified pre-save provider. It does not redefine provider permissions or promise outcomes. Review Music Pro workflows after the tool's live consent and release-matching behavior are checked.