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 for Artists provides listening and audience reports, but a Meta click is not a Spotify playback receipt. A landing-page event cannot establish that a particular ad caused a stream. Keep the ad report, landing-page actions and the service’s own listening analytics separate.
Spotify counts a song stream after at least 30 seconds of playback and records its statistics in UTC. Align reporting periods before comparing trends; matching dates does not create person-level attribution.
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. Compare equivalent outbound-click and arrival measures over the same period. Consent, repeated clicks, filtering and failed loads can all contribute to a gap; it is not an exact count of people who bounced.
- 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 help compare recorded visits and service choices by ad set and creative. They do not identify which hook earned a verified stream.
Reading the three numbers together
A landing page gives you more evidence about where the journey may need attention. It does not explain every difference on its own.
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. Check whether the ad promise matches the page and whether the destination buttons work. Audience fit, consent and measurement can also affect the comparison; change one variable before drawing a conclusion.
Service taps high, streams flat. Check destination accuracy, dates and reporting freshness. A tap may never become a play. These totals cannot establish a conversion rate from clicks to verified streams.
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 | Provider-reported audience breakdowns | Page-reported breakdowns, subject to consent and available signals |
| Which creative drove taps to listen | No | Yes, with campaign tags |
| Optimisation toward recorded service choices | No landing-page event | Possible with an eligible, correctly configured event; not verified listening |
| 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.