Step 1: User Connection

The initial first step is when a user connects with your Presave to Spotify application. When this happens there are a number of standard and optional actions that take place, plus you as the client needs to decide what the primary pre-save playlist action is.

• Standard Pre-Save Actions:
  • Users follow the artist on Spotify and optionally they also follow the label
  • Users agree to receive email updates from the artist
• Primary Pre-Save Playlist Action:
  • Option #1: User selects or creates a Spotify playlist into which the presave album is saved when it is released. Any instant grat tracks that are or become available before the release are saved into this playlist.
  • Option #2: A default Spotify playlist is automatically created for the user. Any instant grat tracks that are or become available before the release are saved into this playlist.
  • Option #3: User follows an artist’s playlist and this Spotify playlist is used to deliver the pre-save album (or single)

Step 2: Day of Release

On the day of release a number of standard and optional actions also take place, some based on your previously selected primary pre-save playlist action .

• Standard Pre-Save Actions:
  • Album, EP or single gets added to your Spotify library (under albums)
  • The individual Spotify tracks in the album, EP or single get added to your Spotify library (under songs)
• Primary Pre-Save Playlist Action:
  • Option #1 or 2: The album, EP or single gets added to your previously selected or created Spotify playlist.
  • Option #3: Album, EP or single is added to the artist’s playlist so it is accessible by users (you need to perform this action on your end).
• Optional Email Action:
  • Optionally an email notification goes out from the music label or Metablocks letting the user know that the album, EP or single is now available on Spotify.