This article explains the process for setting up a Waterfall release strategy within the FUGA Interface. Users will learn how to incrementally build a multi-track product—such as an EP or album—while ensuring that streaming data and playlist placements are preserved through consistent metadata and track-linking on supported Digital Service Providers (DSPs).
The Core Concept
A Waterfall release is a strategy where you incrementally build an EP or album by releasing one new track at a time while including the previously released tracks in each subsequent product. For every new track added to the "waterfall," you must create and deliver a brand-new product. Once the new product is live on a DSP (Digital Service Provider) that offers track-linking (such as Spotify), you then issue a takedown for the previous version.
The 3-Track EP Example If you are building toward a 3-track EP, you will create three separate products in the FUGA Interface:
Product 1: Contains Track 1. Assign Consumer Release Date X and a unique UPC (Universal Product Code).
Product 2: Contains Track 1 and Track 2. Assign Consumer Release Date Y and a unique UPC.
-
Product 3: Contains Track 1, Track 2, and Track 3. Assign Consumer Release Date Z and a unique UPC. While creating Product 2 and Product 3, you can reuse the previously delivered assets from the FUGA Interface by adding their ISRC (International Standard Recording Code). This ensures you are not re-uploading audio files and instead correctly linking each track to its original master recording, maintaining consistent metadata and proper DSP track linking across all waterfall releases.
Metadata Consistency
The Golden Rule To guarantee that DSPs merge the tracks correctly and maintain play counts, the metadata for recurring tracks must be identical across every product version.
International Standard Recording Codes (ISRCs): Use the exact same ISRC for a specific track across all products (e.g., Track 1 uses the same ISRC in Product 1, 2, and 3).
Audio Assets: Select the exact same audio file for the recurring tracks.
Titles and Billing: Track titles, artist names, and product titles must remain consistent.
-
Universal Product Codes (UPCs): Every product version must have its own unique UPC, even if the tracks inside share ISRCs.
Execution Timeline
Managing the transition between releases is essential for a seamless experience.
Release Date X: Product 1 (Track 1) goes live. Fans see a single-track release.
Release Date Y: Product 2 (Track 1 and Track 2) goes live. Once you verify the product is live on Spotify and tracks have linked, you may issue a takedown for Product 1.
-
Release Date Z: Product 3 (Track 1, Track 2, and Track 3) goes live. Once live and linked, you may issue a takedown for Product 2.
Important Considerations
This method is intended for DSPs that offer track-linking features. For platforms that provide formal pre-order or "Instant Gratification" options, it is recommended to use those native features instead of a manual waterfall setup.
If the waterfall releases have also been delivered to UGC DSPs—such as YouTube, TikTok, and Meta—issuing takedowns can impact track availability. Consequently, redeliveries of the full release to these stores are required once a takedown is successful. Please review Important: YouTube & UGC Rights Things to Keep In Mind for more information.
Contact your FUGA representative or reach out via our support channel if you require further assistance with your release schedule.