Smart links that earn their keep
A link page is the only step in a music campaign you fully control and fully measure. What to put on it, what to record, and the fan privacy line worth holding.
Danny Angove
Co-founder, Backline · 25 July 2026 · 4 min read
In short
- The link page is the last point in a campaign you own. Everything after the click belongs to a platform that tells you nothing.
- Platform choice at the link page is a preference signal you cannot get anywhere else, and it is frequently not what the team assumed.
- Point every advert and every post at your own link page rather than straight at a service, or you lose the only measurable step in the chain.
- Country and device data comes free from edge headers with no cookie and no personal data.
- Never store fan personal details on a link page unless you are running the consent, the storage and the deletion properly. Aggregate counts do the analytical job.
A campaign is a chain: someone sees something, clicks, arrives somewhere, chooses a platform, maybe listens, maybe saves, maybe follows. You can see the first two steps in an ad platform. You can see nothing from the fourth onwards.
The third step is yours, and it is the only one where you control both the experience and the measurement.
What a link page is genuinely for
Removing a decision. A fan who uses Apple Music should not have to work out what to do with a Spotify URL. The page exists so the audience does not bounce off the wrong destination.
Measuring preference. Which platform people choose, by country, is the closest thing to first-party audience data most projects have. It routinely contradicts the assumption. Teams who think of themselves as Spotify projects often find a fifth of clicks going elsewhere, which changes where the pre-save, the pitching effort and the ad budget go.
One address that survives. A single link across socials, press, email and adverts means the campaign is measurable in one place and does not need re-pointing when a platform changes a URL format.
On the page, in the data, or nowhere
Illustrative| On the page | Recorded | Deliberately not recorded | |
|---|---|---|---|
| Platform buttons for every service the audience uses | Yes | Which one was chosen | |
| Country and city | Not shown | Country, from the edge header | Anything narrower than country |
| Device and operating system | Not shown | Type only | Any device identifier |
| Campaign parameters | Not shown | Source, medium, campaign | Anything identifying a person |
| Email capture | Only with a real programme behind it | Held by the email platform | Never in click analytics |
| Tour dates and a ticket link | Yes | Clicks |
What to record, and what not to
Record, per click: which platform was chosen, the country from the edge header, device type and operating system, and the campaign parameters on the inbound URL. All of that is aggregate, none of it identifies anyone, and it answers every question a campaign asks.
Do not record: names, email addresses, phone numbers, or anything that identifies an individual, unless you are genuinely running an email programme with consent, storage and deletion handled properly.
The privacy point here is practical, not decorative. Collecting fan details makes you the custodian of other people's personal data, with the obligations that follow. For measurement it buys nothing: every question a manager asks about a link page is answered by counts. Ours never stores fan personal details at all, which is a constraint we chose rather than one we inherited.
Doing the plumbing properly
Point everything at it. Adverts, bio links, press, email, socials. A campaign where half the traffic goes straight to a service has half the data and no way to compare the halves.
Tag inbound links consistently. Campaign parameters on inbound URLs are what let you separate the paid traffic from the newsletter from the bio link. There is a naming convention worth adopting in UTM conventions for music campaigns.
Check it on a phone. Most music traffic is mobile. Load the page on a real handset over a mobile connection, tap through to each service, and confirm each one opens in the app rather than a browser tab asking you to log in.
Include every platform the audience actually uses, which is a data question rather than a taste one. Your last release's platform split is the answer.
Watch the load time. A slow page loses people before the choice happens, and that loss shows up as a poor click-through rate that looks like a creative problem.
Asking what the link page revealed
IllustrativeWhat did the Vela Court release link tell us about platform preference by country?
Data readget_smart_link_statsget_audience_geography
The link recorded 24,300 clicks over the release window across five countries with meaningful volume.
Overall split: Spotify 64 percent, Apple Music 21 percent, YouTube 9 percent, others 6 percent.
Two countries diverge sharply from that. In Japan, Apple Music takes 47 percent of clicks. In Germany, Spotify takes 79 percent.
The Japanese split is the actionable one: the project has been pitching Spotify playlists only, and nearly half the intent in that market goes elsewhere.
Mobile accounts for 88 percent of clicks, so anything that is hard on a phone is costing most of the traffic.
I have no data on what happened after these clicks. No music service reports the source of a play, so the streams that followed can be compared against this window but not attributed to it.
Illustrative example using a fictional project.
Reading the numbers
Click-through from the page. Arrivals against onward clicks. Below about half, look at the page rather than the advert.
Platform split by country. The actionable one. If a country skews to a service you have not been pitching, that is a pitching decision made for you.
Traffic source split. Which campaign parameter delivered arrivals, and which delivered onward clicks. These are often different, and the second is the one that matters.
Device split. Mostly a diagnostic. A desktop-heavy split for a young audience usually means something is wrong with the mobile experience.
The consent line
If you operate in the UK or EU, browser-side analytics and any marketing pixels on a public fan page need consent before they run. The workable arrangement is to gate everything optional behind a clear notice for visitors in those regions, and keep only genuinely essential, cookieless measurement running for everyone.
That is what we do: the server-side click record, which holds no personal data and sets no cookie, is essential measurement and always runs. Browser analytics and any pixel waits for consent where consent is required. It costs a small amount of data from a subset of visitors and it is the correct trade.
What the page cannot do
It cannot tell you what happened after the click. Nobody can, because no music service passes back the source of a play.
So the link page gives you a clean, complete count of intent, and then the chain goes dark. Treat the streaming movement that follows as co-movement rather than as an attributed result, and you will keep the credibility of the numbers you can prove.
Common questions
- What data should a music smart link collect?
- Aggregate only: which platform was chosen, country from the edge header, device type and operating system, and the campaign parameters on the inbound URL. That answers every campaign question. Names, email addresses and phone numbers add nothing analytically and make you responsible for other people's personal data.
- Should adverts point at a smart link or straight at Spotify?
- At your own link page. It is the only step in the chain you can measure end to end, and pointing straight at a service means you can never see how many people arrived, which platform they preferred or which campaign delivered them.
- Do smart links need a cookie banner?
- Any optional browser-side analytics or marketing pixel does, for visitors in the UK and EU. A cookieless server-side click record that stores no personal data is essential measurement and can run for everyone. The practical arrangement is to gate the optional parts behind a clear notice in those regions.
Sources
- 1European Union, Reviewed August 2026. GDPR Article 28: processor obligations
- 2Music Ally, January 2026. 5.1tn annual music streams, but 120.5m tracks had 10 or fewer
Danny Angove
Co-founder, Backline
Danny Angove is a co-founder of Backline. He works on the music business side of the platform: what managers, labels and independent artists actually need to see, and which numbers are worth arguing about.
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
Marketing and campaigns
A UTM naming convention for music campaigns
Campaign tags are the cheapest analytics upgrade available and the easiest to ruin. A convention that survives three people, six months and a tour.
Danny Angove · 3 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 the three the platform shows you instead.
Danny Angove · 3 min read
Privacy and security
Building music analytics that never store fan personal data
Every question a manager asks can be answered with aggregates. The design decisions that keep fan personal data out of an analytics platform, including the uploads that try to smuggle it in.
Danny Starr · 3 min read

