The Release Block lets you build a full service list on your Bio Link, either manually or by scanning a release. Add rescans and scheduled destination activation, all set per territory.

1. Add the Release Block

From your Bio Link editor, go to the "Contents" tab and select "+ Add Content Block". Choose "Release Block" from the list.

[Screenshot: block picker with Release Block highlighted]

Once added, you'll see two ways to build your service list: manually, or by scanning.

Top tip: if your board or workspace already has default service settings configured, the Release Block will use these as a fallback wherever it doesn't have a more specific match. Setting these up ahead of time means new Release Blocks start with sensible defaults rather than an empty list. See How Board Settings Are Inherited into Workspaces for how to set these up.

2. Build your service list manually

If you already know your destination URLs, you can add them one at a time.

1. Select "Add manually"
2. Choose the service (e.g. Spotify, Apple Music)
3. Enter the destination URL

This sets the Default for that service, the one destination that applies everywhere until you override it. To set a different link for a specific territory instead, add it under that territory rather than Default. Repeat for each service and territory you want to cover.

3. Build your service list by scanning

If your release already exists on streaming services, scanning builds the list for you.

1. Select "Scan a release"
2. Enter either a URL for the release on a major streaming service like Spotify or Apple Music, a UPC, or an ISRC.
3. Watch matches populate per service, live, as they're found

NOTE: if a service doesn't match, it's usually because the release isn't live on that service yet, or the identifier entered doesn't match what's listed there. Try again once the release is confirmed live, try scanning with a different identifier or add that service manually in the meantime.

Once scanning finishes, you'll see your full service list, organised by territory, with a Default set for each service alongside any territory-specific matches it found.

4. Rescanning

Keep your service list current as territories and destinations change, at whichever level you need.

From the Rescan tab:

• Rescan all services, across every territory, from a release URL, UPC, or ISRC
• Rescan a single service, across every territory, from the same tab

Scheduled rescan: set either of the above (all services, or one service) to run automatically on a recurring basis, so the block stays current without you checking back.

How scheduled rescan retries work: we schedule one rescan for the time you set, that's the only one queued. If it comes back incomplete (for example, the release isn't live everywhere yet), we schedule the next retry right after that scan finishes. There's only ever one rescan queued at a time. Each retry scans your full link again, not just the services that weren't matched before.

Retries follow this schedule:

• 5 minutes after the first scan completes
• 30 minutes after the second
• 1 hour after the third
• then every hour, up to 24 hours from your original scan time

We stop retrying when:

• Single-destination services (there's one global URL, nothing more to wait for): once at least one match has been applied
• Territory-specific services, like Apple Music or Deezer (regional versions can go live at different times): once all regional versions are matched
• 24 hours have passed since your original scan time, regardless of what's been found

For a single service in a single territory: open that destination's Manage menu, either from its row in the main territory list or from inside that service's Coverage view, and choose Rescan. This updates only that one service in that one territory; everything else stays unchanged.


NOTE: a destination that's scheduled to activate, or locked, is excluded from any rescan, whether block-wide, service-wide, or single-territory, until it's unlocked or activates.

5. Scheduled destination activation

Pre-load a destination and set exactly when it goes live, without needing to be online at the right moment.

1. Add or select a destination
2. Choose "Schedule activation"
3. Set the date and time you want it to go live


This works at any point in your release timeline, not just release day. For example, a vinyl store link that activates the moment stock arrives, or a deluxe edition destination that unlocks a few weeks after the initial release.

NOTE: once a destination is scheduled, it's locked until it activates, so a rescan can't override it in the meantime.

6. How territories work

Default is the single destination you set for a service that is shown to visitors from every territory, unless something more specific overrides it. 

Each destination is then resolved per territory, in this order:

1. Territory override — a URL set specifically for that territory, whether you entered it manually or it came from a scan
2. Default, localized — for services that have different storefronts per territory (Apple Music, for example), your default destination is automatically localized to that territory's storefront if there's no override, same release, local store. This only applies to services that work this way.
3. Default — the flat default URL, used for services without territory-specific storefronts, or where you've configured a territory-specific URL. 
4. None — if nothing applies, no destination is shown for that territory

This is why a service might show a different destination, or none at all, depending on where a fan is visiting from. See Service coverage view below to see and manage exactly what's set for every territory, per service. To turn a territory override back into the default, open that destination's Manage menu and choose Use Default.

Where the default comes from: your default destinations are drawn from your board or workspace's Service Settings, cloned into each new Release Block at creation. These aren't locked, so you can adjust them freely inside any individual Release Block afterwards, but setting them up once at board or workspace level saves you configuring the same defaults on every release. See How Board Settings Are Inherited into Workspaces for the full inheritance and cloning behaviour.

7. Service coverage view

Click on 'Coverage' from the 'Manage' dropdown for any service to see and manage its coverage across every territory in one place.

The view is split into three sections:

• Default — the link fans get anywhere you haven't set a specific link. 
• Territory overrides — territories you've set up yourself, either manually or via scan. Each shows the specific destination URL for that territory.
• Default, localized by territory — for services with territory-specific storefronts (Apple Music, for example), every remaining territory gets your default link automatically localized to its storefront (same release, local store). Services without this behaviour won't show this section. Each row has a "Use Default URL instead" toggle if you'd rather that territory use the flat default rather than its localized version.

Each destination also has its own Manage menu (Use Default, Coverage, Rescan, Schedule activation, Lock), so you can act on a single service in a single territory without touching anything else. See Rescanning for how the single-service, single-territory rescan works from here.

Bulk actions, available from the top of the view:

• Schedule activation for all — apply a scheduled activation date/time across every destination in this service at once, rather than setting each one individually
• Lock all — lock every destination in this service so rescans can't change any of them
• Clear all — remove every destination set for this service, across all three sections

Top tip: this is the fastest way to check whether a service is actually covered the way you expect before publishing, rather than checking territory by territory.

8. Direct-to-service links

If only one destination is configured for a fan's territory, they're taken straight to it rather than seeing a service list first.

You can also generate a link to a specific service (e.g. lnk.to/album/spotify) for use in campaigns where you want to track clicks to that service separately. To copy this link, click 'Get' from the link's card in in the main Link feed, click 'Direct to Service' and then select the service you wish to direct fans to. 

NOTE:  Where multiple service list blocks exist on a bio link, a direct-to-service link will take users to a destination configured in the top most block on the page.