How to Evaluate Any Pre-Save Tool After Spotify's Latest API Change

Spotify's move to a six-month refresh token expiration is a reasonable moment to check whether your pre-save tool, whichever one you use, is actually built to hold up over time. None of the questions below require any technical background. They're about what happens on the fan's end, and what happens to the data you collect.

Does it ask fans to leave your site to complete the action?

Some tools present a follow or save button that, once clicked, opens the Spotify app or a separate authorization page before the action completes. Others let the fan finish the action without leaving the page they're already on. The second version converts better, for the plain reason that every extra step between intent and completion loses some percentage of fans who intended to follow through. Sonikit's follow and save actions are embeddable directly on an artist's own website, not routed through a separate app switch, which is currently uncommon among pre-save tools.

What happens to a fan's data after they pre-save?

Ask directly: does the tool store the fan's email or phone number, or does it only handle the streaming authorization and nothing else? A tool that treats the pre-save purely as a mechanic, click, authorize, done, is leaving the most useful part of the interaction uncollected. You want a platform that captures contact information as part of the same flow, with the fan's consent, so the pre-save produces an asset you can use later, not just a completed action that evaporates once release day passes.

Does it handle an expired authorization gracefully, or does it just fail silently?

Ask what happens if a fan's authorization lapses before release day, whether because of Spotify's new policy or simple inactivity. A platform with no answer to this is a platform that hasn't thought about it. A good answer involves detecting the lapse and prompting the fan to reconnect, rather than the save quietly failing with nobody informed.

Does "future save" mean anything beyond the current campaign?

If you're evaluating a feature that promises to save every future release automatically, ask whether it requires a fresh opt-in tied to one specific pre-save campaign, or whether a fan can subscribe to future releases independent of any particular release being promoted. The first design is fragile under the new token policy. The second is more resilient, and it's also just a better experience for a fan who wants to support an artist ongoing rather than one release at a time.

Is the platform being straightforward with you about the actual change?

Some platforms are using this announcement to argue that pre-saves are broken across the board, which is a useful message if their own implementation was weak to begin with. A platform that gives you a clear, specific account of what changed and what it actually affects is telling you more about how seriously they've thought through the mechanic than one that reaches for "pre-saves are dead" as a talking point.

None of these questions are about Sonikit specifically, though Sonikit answers all five the way described above. They're the right questions to ask any pre-save tool, because the underlying policy change is the same for every platform built on top of Spotify's API. The tools that answer them well were built the right way before this update ever happened.