Explain pre-save permissions clearly to fans

Identify the actual route

Record whether the campaign uses a native platform feature or a third-party authorisation. Keep the provider, destination release and current permission wording. Do not assume every pre-save asks for the same account access or works for every release.

Describe what will happen

Explain the intended library action and any additional requested permissions accurately before the fan proceeds. Spotify describes native Countdown Page pre-saving under its own conditions. That does not certify the access requested by an unrelated campaign provider or allow a promise that every fan will listen.

Keep marketing permission separate

A pre-save or streaming login is not automatically permission for unrelated email marketing. Provide a clear optional choice for the actual mailing list and explain the sender and purpose. Confirm the applicable legal requirements for the audience; UK ICO guidance is jurisdiction-specific, not a universal legal rule.

Explain control and correction

Point fans to the relevant platform or provider controls for withdrawing access, and keep the campaign’s contact route clear. Test the actual consent journey without collecting credentials yourself. No DistroBolt pre-save integration, personal account access or automatic marketing enrolment is activated by this guide.

Sources and review

Reviewed 4 November 2026. Platform requirements and plan terms can change. Examples are planning aids, not a promise of account access, release acceptance or earnings.

• Spotify native Countdown Pages
• ICO email-marketing guidance

Continue your release planning

• Prepare a music advertising brief before spending money
• Track campaign links with a consistent UTM convention
• Smartlink clicks are not streams: measure the difference

Ask the DistroBolt team about your release. Send a concise question and release reference; never send account passwords or verification codes.