Correlation is the honest answer in music marketing
There is no passback linking a stream to the advert that caused it. What you can measure is whether signals move together, and how to report that without overclaiming.
Danny Starr
Co-founder, Backline · 29 July 2026 · 4 min read
In short
- No streaming platform passes back the source of a play. Any tool claiming to attribute streams to a specific advert is inferring, not measuring.
- What can be measured properly is co-movement: two independently collected series aligned on the same dates, with a stated strength. Backline puts spend, streams, clicks and ticket sales on one project timeline, so that alignment is already done.
- Co-movement is genuinely useful. It rules things out, it sizes effects roughly, and it survives being questioned in a meeting.
- Three guards make it honest: align on dates only, correct for reporting lag first, and phrase every finding as moved together rather than caused.
- A high correlation on eight data points is noise. Require a minimum overlap before you report a number at all.
A manager asks the only question that matters after a campaign: did it work. The truthful answer is that nobody can tell you exactly, and the reason is structural rather than a gap in the tooling.
When someone hears a track on Spotify, Spotify does not tell your ad platform, your link shortener or your analytics tool that this play came from that advert. There is no passback. The click on your landing page and the stream that may have followed it live in two systems that never exchange identifiers, and for good privacy reasons.
So every claim of the form "this campaign drove 40,000 streams" is a model, not a measurement. Some models are reasonable. None is a receipt.
The useful part is that the honest version of the answer is more persuasive than the invented one, and it is entirely reachable with data you already have.
What you can actually measure
Two things, and they are worth more than a fake receipt.
Direct outcomes inside one system. Clicks on your own landing page, by platform, country and campaign parameter. Ad platform outcomes as the ad platform counts them. Email opens and clicks. Ticket sales through your ticketing partner. Each of these is measured end to end within one system, so each is real.
Co-movement between systems. Take ad spend per day, streams per day and ticket sales per day. Align them on one date axis. Ask how strongly each pair moves together. That is a correlation, and reported carefully it is defensible.
This second one is what Backline is built for. Streaming, advertising across Meta and Google, smart link clicks, press coverage, newsletter sends and ticket sales all land on a single project timeline, already aligned on dates. The comparison becomes a view you open rather than a spreadsheet you assemble on a Friday afternoon.
Three independently measured signals on one axis
IllustrativeHow to do the co-movement properly
Three things have to be right or the number is worse than no number.
Align on dates, and only on dates
Resist the temptation to build a join on anything cleverer. If you find yourself matching a click to a listener because both were in Manchester within an hour, you have invented attribution and given it a technical veneer. Country-level scoping is defensible: comparing clicks from Germany against listener movement in Germany is still date-and-place alignment rather than person matching.
Fix the lag before you correlate
If your streaming series is running two days behind reality and your ad spend is same-day, then every correlation you compute is comparing Tuesday's spend to Sunday's streams. On a short campaign that alone can invert the result. Shift the series by the known reporting lag first, or accept that the answer is meaningless.
This is the most common silent error in the category, because the correlation still produces a confident-looking number. Backline corrects for the known lag on each source before anything is charted, so the series you are comparing are dated to the day the activity happened rather than the day the figure arrived.
Require enough overlap
Pearson correlation on eight points will happily return 0.8 for two unrelated series. Set a floor on the number of overlapping days before you report anything, and when you are below it, say so rather than reporting a weaker number.
How much overlap before you report a number
IllustrativePhrasing that survives a meeting
The difference between a useful finding and an overclaim is usually one verb.
- Weak and unfalsifiable: "The campaign drove a 22 percent lift in streams."
- Honest and useful: "Spend and streams moved together closely through the campaign window, and streams stayed above the pre-campaign level for nine days after spend stopped."
The second sentence is more persuasive to anyone who knows the data, and it does not collapse when someone asks how you know. Backline's correlation insights are always phrased as movement together rather than cause, because the data cannot support the stronger claim.
Where correlation earns its keep
Ruling things out. If a market's listener numbers were flat through a campaign that spent heavily there, the campaign did not move that market. Negative findings are cheap, reliable and frequently the most valuable thing in a review.
Sizing. Loose bounds are still bounds. Spend of a few thousand alongside a movement of a few hundred thousand streams tells you something about magnitude even without a causal claim.
Sequencing. Which signal moves first is often more interesting than how strongly they move. In live music particularly, recognition and airplay signals tend to lead ticket sales rather than follow them, and knowing the order of arrival shapes an on-sale plan.
Finding the thing you forgot. A cluster of press coverage explains a week that otherwise looks like an algorithm gift. Because Backline keeps news coverage on the same timeline as streams and spend, the mysterious week usually explains itself as soon as you look at it, which is most of what a busy team needs from correlation.
The one thing to refuse
If a tool tells you a specific number of streams came from a specific ad set, ask how. If the answer involves modelled attribution, fine, ask for the assumptions. If the answer is a confident restatement of the claim, stop trusting the number, because the passback that would make it true does not exist.
Backline will tell you what moved with what, over which window, and how much data sat behind the answer. That is a claim that holds up in the room.
Common questions
- Can you attribute streams to advertising?
- Not directly. Streaming platforms do not pass back the source of a play to advertisers or analytics tools, so there is no identifier linking an advert to a stream. You can measure clicks on your own landing pages end to end, and you can measure whether ad spend and streaming moved together over the same dates, which is correlation rather than attribution.
- Is correlation useful if it does not prove causation?
- Yes, in four ways: it rules out claims when a signal did not move, it puts rough bounds on the size of an effect, it shows which signal moved first, and it reminds a team of the press or radio activity that explains an otherwise mysterious week.
- What ruins a correlation between ad spend and streams?
- Uncorrected reporting lag. Third-party streaming figures typically trail the real day by around two days, so an uncorrected comparison lines up Tuesday's spend against Sunday's streams. On a short campaign that can reverse the conclusion while still producing a confident looking number. Backline applies the known lag per source before charting, so the dates line up.
Sources
- 1Google, Reviewed August 2026. Analytics Data API: report basics
- 2Meta, Reviewed August 2026. Graph API insights reference
Danny Starr
Co-founder, Backline
Danny Starr is a co-founder of Backline and builds the platform. He writes about the data engineering behind music analytics: ingestion, identity, honesty in charts, and the AI layer on top of it.
Backline does this for the projects you run
Streaming, audience, social, advertising, website, search, ticketing and press data in one dashboard per project, with an AI assistant that answers questions about your own connected data. Invite-only.
Keep reading
Data engineering
Why two tools show different numbers for the same artist
Open two analytics products on the same project and the streaming figures rarely match. Here is what causes the gap, which number deserves your trust, and how to test any tool in a demo.
Danny Starr · 4 min read
Marketing and campaigns
What to measure when you run ads for a release
Ad platforms report on themselves and report generously. The five numbers that tell you whether music advertising worked, and how to read them next to streams and tickets.
Danny Angove · 4 min read
Live and ticketing
Putting live and online data on the same page
Streaming teams and touring teams look at different dashboards and reach different conclusions about the same project. What happens when both sets of numbers share one timeline in Backline.
Danny Angove · 4 min read