Troubleshooting music links

Organised by what you're actually seeing, in the words people actually use. Every entry says what causes it and whether Zippy can fix it — including the ones where the honest answer is no.

"It opens in the browser instead of the app"

The single most common report. Work down this list in order.

1. Your Zippy link doesn't point at Spotify. Zippy matches on hostname. If the destination is hypeddit.com, submithub.com, a DistroKid HyperFollow page or any other smart-link landing page, Zippy does a plain redirect and nothing about the in-app browser changes. Repoint the link straight at open.spotify.com/…. This is step 1 of the campaign workflow and it's the fix roughly half the time.

2. Your URL isn't a shape Zippy understands. Only track, album, artist and playlist open the app. See "it opens the app but on the home screen" below for what an episode, show or spotify.link URL does instead.

3. The service isn't supported. SoundCloud, Bandcamp, Deezer, Tidal and Amazon Music have no entry in the deeplink table. Those links redirect and count taps, but no interstitial runs and no app opens. Full table: Streaming services.

4. The tap came from a desktop browser. Zippy only serves the interstitial to mobile user agents. On a laptop it's a plain redirect, by design — there's no app to open.

5. Spotify isn't installed on that phone. On iOS nothing happens and the page sits there until it tells the visitor the app didn't open. On Android the intent fails and the browser follows the built-in fallback to your https URL. Both are the intended safe degradation, and both look identical to "it's broken" from the outside.

6. Meta blocked the launch. In-app browsers change their rules and sometimes suppress a scheme navigation that wasn't triggered by a tap. On iOS, Zippy renders an Open in the spotify app button for exactly this case — a second tap is a real user gesture and often gets through where the automatic one didn't. (The button text really is lowercase "spotify"; it's built from the platform key.) On Android there is no button and no page: Zippy fires the intent:// URL immediately and, if nothing takes it, the intent's own browser_fallback_url sends the visitor to your web URL. So an Android device that lands on Spotify web is the expected behaviour today, not a misconfiguration. This one is not fully fixable; see Limits.

"They land on Spotify but they're not logged in"

This is the same problem as above, seen from the listener's side, and it's why the failure costs money rather than just being ugly. Meta's in-app browser has its own cookie jar. Whoever is signed into Spotify in Safari or Chrome is not signed in inside Instagram's browser, so they get a logged-out web player, a 30-second preview, no save button, and they leave.

Run the checklist above. If the app opens, the login problem disappears with it — the native app has their session.

"My ad dies at the landing page"

If the chain is ad → landing page → Spotify, the trap is at the second hop and Zippy cannot reach it. Zippy acts on the destination of its own link. A landing page's outbound buttons are that page's code, not ours.

The fix is to take the landing page out of the chain for that ad set and point the Zippy link directly at Spotify. That has real costs — you lose the service chooser and whatever the page was capturing. The workflow page covers the tradeoff.

"It works sometimes and not other times"

Almost always genuine, and usually one of these — not randomness:

• Different OS. iOS and Android take completely different code paths. A link that works on your iPhone can behave differently on an Android tester's phone.
• App installed or not. Same link, two phones, two outcomes.
• Different source app. Instagram, Facebook, TikTok and Threads all ship different webviews with different rules, and they change them without announcement.
• Cold start timing. Spotify launching from cold can take several seconds. The app still opens; it just opens late, which affects what the measurement records (below) more than what the listener experiences.
• Meta changed something. This is cat-and-mouse and always has been. Zippy is not immune to it and doesn't claim to be.

If you want to know what a specific URL does before you test it by hand, the Deep Link Debugger shows the exact forms Zippy will fire.

"It opens the Spotify app but on the home screen, not my song"

Your URL is a shape Zippy matches as Spotify but can't extract an item from. Three known cases:

Zippy claims the hostname, fires the scheme with no item attached, and Spotify opens on the listener's own home feed. The web fallback is never reached, because the navigation has already happened — so this is worse than a plain link would have been.

Fix: use an open.spotify.com/track|album|artist|playlist URL. If you're promoting a podcast episode or show, use a plain link for now and accept the browser — that's the better of the two bad options until Spotify's podcast types are supported.

"My YouTube Music link opened YouTube"

Correct, and it's a bug on our side. music.youtube.com is currently listed as a host on the YouTube entry rather than having one of its own, so it produces youtube://watch?v=<id> and the YouTube app takes it. Treat YouTube Music as unsupported and don't route a music campaign through it.

"Meta Ads Manager shows zero conversions since I switched"

Expected, and not a Zippy fault you can configure away. A listener who reaches the native Spotify app has left the webview your pixel runs in, so your successful conversions are the exact ones Meta can no longer see. Attribution can get worse while real outcomes get better.

Judge these campaigns on Spotify for Artists, and keep a control ad set on the old link so you have something to compare. The full explanation and what we can and can't prove is at Limits → the attribution tradeoff.

"My app-open rate looks too good to be true"

If it's an Android number: trust that instinct. Zippy's Android measurement is currently biased toward reporting success, because of a real bug in how the interstitial registers its listeners on that platform. We don't publish an Android app-open rate for that reason, and you shouldn't act on one either. The mechanism is written out at Limits → Android.

If it's a blended number, remember Android is inside it and inflating it.

"My app-open rate looks too low"

Possible causes, in rough order of likelihood:

• Slow cold starts. The measurement stops waiting after nine seconds. An app that takes longer is recorded as "browser" even though it opened.
• Sampling. The counts come from Cloudflare Analytics Engine and are sampled. Small volumes are noisy.
• Your audience doesn't have Spotify installed. No amount of routing fixes that; the web fallback is doing its job.
• The link genuinely isn't matching. Check it in the debugger.

"I don't know whether Zippy caused the app opens at all"

Fair, and we can't fully answer it. Zippy measures its own page going hidden, which correlates with an app launch but is not proof Zippy caused it — somebody who backgrounded Instagram to open Spotify themselves looks identical. The honest test is a controlled comparison: same creative, same audience, two ad sets, one on a Zippy link and one on your old link, judged on Spotify-side numbers. See Limits → what the number cannot tell you.

FAQ

Why does my Spotify link open in the Instagram browser instead of the Spotify app?

Most often because the Zippy link points at a landing page (Hypeddit, SubmitHub) rather than at open.spotify.com directly — Zippy only fires the app-open for hosts in its deeplink table. Other causes: an unsupported URL type, Spotify not installed, a desktop tap, or Meta suppressing the launch.

Why are my listeners not logged in when they reach Spotify?

Because the in-app browser has a separate cookie jar from Safari or Chrome, so their Spotify session isn't there. It's a symptom of the link staying in the webview rather than opening the native app, not a separate problem — fixing the app-open fixes the login.

Why does my Zippy link work on my phone but not my friend's?

The two most common reasons are a different operating system (iOS and Android take different code paths) and whether Spotify is installed at all. Different source apps — Instagram vs Facebook vs TikTok — also ship different in-app browsers with different rules.

My Spotify link opens the app's home screen instead of my track. Why?

Your URL is an episode, show, or spotify.link short link. Zippy recognises the host but can't extract an item from those shapes, so Spotify opens with nothing to display. Use a track, album, artist or playlist URL instead.

Read more

• Streaming services — the supported table.
• Meta ads to a Spotify release — the workflow.
• Limits — what none of this fixes.
• Deep Link Debugger — test a URL yourself, free, no login.
• Blog: In-app browser: logged out and gone