Release day

Release day: an artist drop that opens straight to the track

Turning a release-day link into installs that land on the track, crediting the channel that drove the stream.

Updated Jul 31, 2026

Who runs this

  • Growth marketers
  • Performance & paid

What it uses

  • Deferred deep linking
  • Smart routing
  • Per-link channel tagging
  • Match audit log (deterministic vs probabilistic)

Release day is a spike that doesn't come back. Fans tap a link from a story, a fan account, a playlist post — and if they don't have the app, the worst outcome is landing on a generic install screen while the moment passes.

What problem does this solve?

A new single drops across an artist's socials and partner accounts. Tapping the link should open the track in the app, and for new users, install and then open the track — crediting which surface drove the listen.

How do you set the links up?

One smart link to the track, distributed everywhere, with the source surface tagged so you can see which channels actually convert to streams.

{
  "deepLinkPath": "/track/midnight-signal",
  "customData": { "artist": "kestrel", "ch": "fan-account-ig" }
}

Why does release day need different link handling?

Because the traffic arrives in hours rather than weeks, and almost none of it is yours. A drop is amplified by fan accounts, playlist curators, the artist's own socials, and partner posts — dozens of surfaces you don't control, all sharing at once, all in apps with in-app browsers that handle links inconsistently.

That combination breaks the usual assumptions. You can't fix a bad link after the fact because the window has closed, you can't ask thirty accounts to update what they posted, and a meaningful share of the audience is meeting your app for the first time. One link that routes correctly everywhere and survives an install is the only version of this that works.

How do you credit the surface that drove the stream?

Tag the channel on the link rather than minting a different link per surface. Same destination, same payload, a different channel parameter — so the artist's team gets a per-surface breakdown without anyone having to manage a spreadsheet of URLs on release morning.

SurfaceChannel tagWhat it usually tells you
Artist's own storyartist-ig-storyBaseline — the existing fanbase
Fan accountsfan-account-igReach beyond the fanbase; often the highest new-install share
Playlist / curator postcurator-postIntent-heavy; smaller volume, better stream-through
Partner or label pushlabel-pushVolume; quality varies a lot by partner
Printed or venue QRvenue-qrSmall but almost entirely new users

The breakdown is worth more than the total. A surface that drove 10,000 taps and few first streams told you something different from one that drove 800 taps and mostly streams — and on the next drop, that's where the push goes.

Which metric should you watch?

First-stream rate from the link — the share of taps (and deferred installs) that resulted in actually playing the track, broken out by source surface. It tells the artist's team where to spend the next release-day push.

Measure it over 72 hours rather than on the day. New users who install on release night frequently stream on day two, and a same-day-only cut systematically under-credits exactly the surfaces that are bringing you new listeners rather than existing ones.

On release day, the homepage is where momentum goes to die.
Tagged#Music#Release

Related use cases

Every one of these depends on the same two things: link context surviving an install, and an honest answer to which click produced it. The scoring model is published in full on our methodology page, and you can check any domain's association files with our free link validator.