Connected DSPs & integrations
When you paste a link into any DSP field on a release, BCKSTG uses that link to autofill the other DSPs, so you don't have to copy your release link from six services. This article covers which platforms are connected, how the autofill chain works, and what data leaves BCKSTG when these integrations run.
How the autofill chain works
Paste a link in any DSP field (Spotify, Apple Music, Tidal, SoundCloud, Audiomack) and BCKSTG:
- Resolves the canonical record at the source, reads back the title, primary artist, cover art, and (when available) UPC/ISRC.
- Searches every other DSP in parallel for the same record using that resolved title + artist (plus UPC/ISRC when present, which is much more accurate).
- Fills only empty fields, manual entries are never overwritten.
The release-day Green Room link ladder (Tier 1 UPC/ISRC → Tier 2 verified title+artist → Tier 3 web search confirmation) is a separate, scheduled pass that runs from your release date and is documented in How the DSP link autofill ladder works. This page covers the manual-paste chain that runs while you're editing a release in the dashboard.
The connected DSPs
| Platform | What we use it for | Source data |
|---|---|---|
| Spotify | Pre-saves, release autofill, library-add on release day | Public catalog + per-fan OAuth (scoped to library-modify only) |
| Apple Music | Pre-adds, release autofill, library-add on release day | MusicKit catalog + per-fan MusicKit tokens (expire ~6h) |
| YouTube | Channel autofill, official video lookup | API key only, no OAuth |
| Tidal | Release autofill, link lookup | Public catalog API |
| SoundCloud | Release autofill, link lookup, high-res artwork | App-token catalog API |
| Audiomack | Release autofill (title/artist/cover), cross-DSP search from an Audiomack link, UPC/ISRC lookup | 2-legged OAuth via the Onelink Search API |
YouTube specifically: the autofill only accepts a result that's either on the artist's {Artist Name} - Topic channel (auto-generated by YouTube for distributed music) or on a channel whose name contains the artist's name AND whose title contains the song title. Without one of those signals, the field is left empty rather than filled with a guess, a wrong YouTube link sends fans to a cover or reaction video, and we'd rather leave you to paste the right one than ship the wrong one.
What data leaves BCKSTG
For release autofill, only the metadata of the release you're editing is sent (title, artist, UPC/ISRC, the source URL itself). No fan data is ever transmitted to any DSP during autofill.
For pre-saves and pre-adds, the fan grants Spotify/Apple Music permission directly in their browser; the token returned to BCKSTG is scoped to library-add only and is used once on release day. See How Spotify pre-saves work and How Apple Music pre-adds work for the full mechanics.
Quiet Hours & tour radius routing (Google Maps Platform)
When a fan submits their city/state on a fan-page form, BCKSTG sends that text to Google Maps Platform's Geocoding API (to get an approximate latitude/longitude) and Time Zone API (to get the IANA time zone). Those two values are stored on the subscriber row and used only to:
- Hold messages until 8 AM in the fan's local time zone (Quiet Hours, 10 PM to 8 AM, fan-local).
- Route tour-stop alerts to fans within a configurable radius of each show.
Only the city/state the fan already typed is sent, no IP address, no device-level location. If the fan didn't enter a city, we skip the lookup entirely and they receive sends at the artist's local time. This is also disclosed under "Third-party services" in the Privacy Policy.
Related articles
- How the DSP link autofill ladder works, the release-day Tier 1/2/3 cron that finishes filling links after release.
- How BCKSTG Green Room works, the unified release/tour/announcement system, including Quiet Hours.
- Your release smart link, the public
/{slug}/releases/{lp-slug}landing page that shows all your DSP buttons.