At found.ee, getting your music into fan libraries the moment it’s released is our top priority. Our Pre-Save pages are designed to automatically add your track or album to each fan’s streaming library on release day — but occasionally, someone may report that it didn’t show up as expected.
Here’s a detailed overview of how the Pre-Save system works and the most common reasons a save may appear delayed or missing.
🚀 How Pre-Saves Work at found.ee
Our system begins scanning for your release 30 minutes before the scheduled release time you input when creating your Pre-Save page. We connect directly with major DSPs (like Spotify and Apple Music) through their APIs to locate your release and deliver it to fan libraries.
Here’s how we match your release:
UPC Match (Most Accurate) – We first attempt to locate your release using the UPC. If a match is found, we consider it verified and begin delivering it.
Artist Name + Album Name – If a UPC match isn’t found, we then try to identify a match using metadata like Artist Name and Album Name.
Fallback Strategy – If a match is found on some DSPs but not others, we use those verified results (e.g., artist name and album name) to assist in a second round of matching.
Pre-Save Delivery Analytics – After release, your found.ee dashboard will show real-time delivery stats that help you monitor performance:
🟢 Delivered: The number of pre-saves that were successfully delivered to fan libraries.
🟡 Awaiting Delivery: The number of pre-saves that are queued to be delivered based on release timing.
🔴 Failed: The number of pre-saves that could not be delivered (due to missing permissions, unmatched metadata, or platform-side delays).
💡 Important to Know: Even if your release is live on a DSP, it may not yet be available via their API — which is why our system keeps checking repeatedly.
The system continues to rescan every 3 minutes for any unresolved DSP links — and will continue doing so for up to 24 hours after the release time. Even if the music appears to be live on a DSP, it may not yet be available via their public API, which is why this repeated scanning is necessary.
Since most releases are scheduled for midnight, we typically see that by the time release traffic increases later that morning, all DSP links have been resolved & all pre-saves saves have been fully processed.
🔍 Common Reasons a Pre-Save Might Not Appear
1. Spotify App Didn’t Refresh (Most Common)
In many cases, the save has occurred, but it doesn’t yet appear in the Spotify mobile or desktop app. The Spotify web player often updates faster.
Solution: Ask fans to log out and back in or wait a few hours for Spotify to refresh their data.
2. Territory-Specific UPCs
If your release uses different UPCs for different regions, fans in certain territories may not have access to the version our system tried to save.
Solution: We have a workaround for this — reach out to our team if you anticipate multi-territory issues.
3. Fan Didn’t Complete the Pre-Save Process
If a fan clicks “Pre-Save” but doesn’t connect their streaming account or approve permissions, we can’t process the save on release day.
Solution: If you collected emails, check your Pre-Save list. If the fan isn’t listed, they didn’t finish the process.
4. Saved as Album vs. Track
Even for singles, DSPs create both album and track entries. Depending on the link you used for the Pre-Save, the music may appear under “Albums” or “Liked Songs.”
Solution: Ask fans to check both “Albums” and “Songs” in their library.
5. Time Zones & Processing Time
Pre-Saves are processed at the release time you input (usually midnight US Eastern Time). Processing for all fans can take up to 20 minutes.
Solution: If it’s only a few minutes past release, give it a little more time. Most saves are finalized by early morning.
6. Fan Removed Permissions
If a fan removes found.ee’s access to their streaming account before release day, we won’t be able to complete the save.
Solution: The fan can manually add the release or reauthorize permissions through a new Pre-Save.
7. Missing or Invalid UPC/ISRC
Without a valid UPC or ISRC, we won’t be able to find or match your release in DSPs.
Solution: Ensure your codes are accurate in your found.ee dashboard. We’ll alert you in advance if something looks off.
Still Need Help?
If you've gone through this checklist and are still seeing issues, reach out to our support team — we’re happy to help troubleshoot and ensure your fans get the experience they expect.