Meta ads to a Spotify release

This is the workflow for the campaign musicians actually run: an Instagram or Facebook ad, pointed at a Spotify release, where the tap currently dies in Meta's in-app browser because nobody is logged into Spotify on the web.

It takes about ten minutes. Step 1 is the one that changes your funnel, and step 6 is the one nobody warns you about — read both before you start.

Step 1 — point the Zippy link straight at Spotify

Zippy only acts on destinations it recognises. It matches on hostname. If your Zippy link points at hypeddit.com, submithub.com, distrokid.com/hyperfollow or any other smart-link landing page, Zippy sees a host it doesn't own, does a plain redirect, and the in-app browser trap is completely intact.

So the destination of your Zippy link must be the Spotify URL itself:

https://open.spotify.com/track/4cOdK2wGLETKBW3PvgPWqT

This is a real change to how you run ads, and it has costs:

• You lose the landing page, and with it the "choose your streaming service" chooser, the pre-save form, and whatever the landing page was capturing for you.
• You're now sending everyone to Spotify specifically, not to their own service of choice.

If the landing page is doing a job you need, keep it — and accept that Zippy can't help on that link. Some people run both: a Zippy link straight to Spotify for the Spotify-targeted ad set, and the landing page for everything else.

Step 2 — use a URL shape Zippy understands

Zippy opens track, album, artist and playlist URLs. It does not open episode, show, or spotify.link/… short links — those open the Spotify app's home screen with your release nowhere in sight, which is worse than doing nothing.

Copy the URL from Spotify's Share → Copy link on the release itself, and check that the path segment after the host is one of the four types. Full table: Streaming services.

Step 3 — check the URL in the debugger before you spend a cent

Paste your exact destination into the free Deep Link Debugger. It reads the same table the production engine uses, so it tells you up front whether this specific URL gets the app or the browser, and shows you the exact iOS scheme and Android intent it will fire.

If the debugger says your link doesn't get the app, no ad budget will change that.

Step 4 — create the Zippy link and tag it

Create the short link with the Spotify URL as the destination, then add UTM parameters so the tap is attributable on your side even when Meta's isn't. A campaign-per-ad-set convention is enough; the point is that you can tell your own traffic apart later.

Two optional additions worth knowing about:

• Fallback — where the link goes if something downstream is unavailable. A link never stops redirecting.
• A/B testing (Hero and up) — split the same short link across two destinations and compare app-open rate per variant, not just clicks.

Step 5 — use the Zippy link as the ad destination

Paste the short link into the ad's website URL field. Nothing else about the ad changes.

What an iOS visitor gets: a small page that fires Spotify's URL scheme immediately. If Spotify opens, they're gone in well under a second and never really see it. If it doesn't, after 1.5 seconds the page says so out loud and offers two things — Open in the spotify app (tapping again, because some webviews only allow the launch on a real user gesture) and Continue in browser. Zippy never auto-redirects an iOS visitor to the browser: a redirect a second and a half after the tap reads as a glitch, and it would throw away the slow app launches that do eventually land.

On desktop there's no interstitial at all — just a plain redirect, because there's no app to open.

Step 6 — expect your Meta pixel to look worse

This is the part that will make you think you broke something. You didn't.

When the tap succeeds, the listener leaves the webview and lands in the native Spotify app. Your pixel lives in the webview. So the person who converted is exactly the person your pixel can no longer see. Meta Ads Manager can report fewer conversions after you fix the problem, while your actual Spotify numbers go up.

A musician in r/musicmarketing described exactly this after switching landing pages:

"now it seems to work. The link opens the app!!! But although I added my metapixel to the submithub landing page i get no conversions in my meta add manager but the followers of my playlist are increasing. All in all it's an improvement"

— EmilyVibezNextDoor, r/musicmarketing, 2026-05-13

Plan for it rather than being ambushed by it:

• Judge the campaign on Spotify for Artists, not on Ads Manager conversions. Streams, listeners and saves are the real outcome; the pixel is a proxy that this fix deliberately breaks.
• Keep a control. Run one ad set on the old link for a week alongside the Zippy one. Same creative, same audience. Compare Spotify-side numbers between them, not Ads-Manager-side.
• Read Limits → the attribution tradeoff before you decide this is worth it. It's a genuine tradeoff, not a free win.

Step 7 — read the number, and read it as a trend

Your link's app-open receipt gives you the headline: the share of taps that opened the real app. The Hero-and-up dashboard splits it into opened / browser / broken.

Three things about that number, all of which are on the Limits page in full:

1. It is inferred, not observed. Zippy fires the scheme and watches whether its own page goes hidden. A phone lock inside that window reads as "opened"; an app that cold-starts slower than nine seconds reads as "browser".
2. It is sampled. Read the gap between two numbers, never the last digit.
3. Android's number is not currently trustworthy and Zippy does not publish one. The reason is a real bug in the interstitial, described in full at Limits → Android.

What to do if it isn't working

Go to Troubleshooting. It's organised by symptom — "opens in the browser, not the app", "they're not logged in", "works sometimes" — rather than by feature.

FAQ

How do I run an Instagram ad to Spotify without it opening in the in-app browser?

Point a Zippy link directly at your open.spotify.com/track|album|artist|playlist URL — not at a Hypeddit or SubmitHub landing page — and use that short link as the ad destination. On mobile Zippy fires Spotify's own URL scheme from inside Meta's browser, which launches the native app where the listener is already signed in.

Can I keep my Hypeddit or SubmitHub landing page and still use Zippy?

Not usefully. Zippy only fires the app-open for hostnames in its deeplink table, so a link pointing at a landing page gets a plain redirect and the in-app browser trap stays exactly as it was. The landing page has to come out of the chain for the escape to happen.

Why did my Meta conversions drop after switching to Zippy?

Because the fix works. A listener who lands in the native Spotify app has left the webview your Meta pixel runs in, so the successful conversion becomes invisible to Ads Manager. Judge these campaigns on Spotify for Artists numbers and keep a control ad set on the old link.

Does this work on Android too?

The Android path fires an intent:// URL with a built-in web fallback, so it degrades safely. But Zippy's Android app-open measurement is currently biased and no Android rate is published — see Limits.

Read more

• Streaming services — which services and URL shapes work.
• Troubleshooting — symptom-first fixes.
• Limits — the ceiling, in writing.
• Blog: Why links die in the in-app browser
• Blog: Broken pixels and attribution