You cannot put a tracking pixel on Spotify. That single fact is why so many artists run Facebook and Instagram ads, watch money leave, and learn nothing. The fix is structural, not clever: stop sending ads straight to Spotify, and put a landing page you control in the middle.
Why Spotify cannot tell you if your ads worked
Meta measures an ad by what happens on the destination. On a normal website that means your pixel fires on arrival, on sign-up, on purchase — and Meta learns which people are worth showing your ad to.
Spotify is not your website. You cannot add a pixel to it, you cannot see who arrived from which ad, and Spotify for Artists will only show you total streams — with no way to split "came from the ad" apart from "found it anywhere else". Meta, meanwhile, can only report the click it sold you. Between the click and the stream sits a void neither side can see across.
So an ad sent straight to open.spotify.com produces exactly one number: cost per click. Whether those clicks became listeners, in which country, on which service — unknowable.
The landing page in the middle
Route the ad to a smart link instead, and the void gets a floor. The landing page is yours: your pixel fires there, your analytics run there, and the fan's choice of streaming service happens there — all before the handoff to Spotify.
What becomes measurable, step by step
- The ad click → landing. Meta reports clicks; your page reports arrivals. The difference is people who bounced before the page loaded — your first real quality signal.
- Landing → service choice. How many arrivals actually tapped through to a streaming service, and which one. This is the number that separates "the ad works" from "the page works".
- The pixel events. With Meta Pixel and the Conversions API firing on the landing page, Meta can optimise delivery toward people who actually tap through to listen — not just people who click ads.
- The tags. Campaign-tagged links split your traffic by ad set and creative, so two weeks in you know which hook earned the streams.
Reading the three numbers together
Once the page is in the middle, every underperforming campaign becomes diagnosable, because failure has a location.
Clicks high, arrivals low. Slow page or broken in-app browser handoff. Fix the landing experience — in-app browsers are usually the culprit.
Arrivals high, service taps low. The ad is over-promising or the page under-delivers — artwork, title clarity, too many buttons. The ad is fine; the page needs work.
Service taps high, streams flat. Rare, and usually an attribution window problem rather than a real one — streams lag clicks, and playlist adds surface days later.
What each setup can actually see
| Ad → Spotify directly | Ad → smart link → Spotify | |
|---|---|---|
| Cost per click | Yes | Yes |
| Arrivals vs clicks | No | Yes |
| Service the fan chose | No | Yes |
| Country and device split | Only what Meta guesses | Yes, measured on the page |
| Which creative drove taps to listen | No | Yes, with campaign tags |
| Meta optimising toward listeners | No — optimises toward clickers | Yes — pixel and Conversions API events |
| Email capture from the same traffic | No | Yes, if you add a sign-up step |
A note on scale and honesty
None of this makes a £3-a-day campaign behave like a label budget. What it does is make small budgets teach — a hundred clicks that tell you which creative, country and service worked are worth more than a thousand that vanish into Spotify unmeasured. Spend to learn first; spend to scale once the numbers say something.
If you are planning the ads themselves — objectives, budgets, creative — start with how to run music ads without wasting clicks, and manage the campaign alongside the release in Playloudr's Meta ads tools.