Every link tool shows numbers. Fewer say what the numbers are. Since decisions get made on them — which channel gets the ad budget, which service goes first on the page — it is worth being precise about what a link page can and cannot know.
What a link page can measure directly
- Human visits: the page was loaded by what appears to be a person. Honest tools subtract known bots, link-preview fetchers, and browser prefetches first; those can be a large share of raw requests.
- Sessions and unique visitors: estimates built from short-lived identifiers. Good ones rotate and never follow a person across long windows — treat "uniques" as an estimate, because that is what it is.
- Destination clicks: a fan chose a service. This is the page’s conversion event and the most decision-worthy number it owns.
- Click-through rate: clicks divided by human visits. Meaningful only when the denominator excluded the bots.
- Attribution: which campaign variant, country, device, and referrer each visit carried.
- Fan signups: emails given with consent — the only number on this list you can contact.
What it cannot measure
The moment a fan lands on Spotify, the link tool’s visibility ends. It cannot see whether they pressed play, streamed for four seconds or forty minutes, saved the track, or came back tomorrow. Those events live with the streaming provider and reach a third-party tool only through an explicit provider integration — which is rare, partial, and always labelled when real.
So when a link tool reports "streams" without naming a provider integration, it is renaming clicks. The difference is not pedantry: click-to-stream drop-off is real, it varies by service and audience, and a decision made on renamed clicks is a decision made on a number that does not exist.
Why two tools report different numbers for the same page
Put a link page behind both its own analytics and Google Analytics and the totals will disagree — reliably, and for reasons worth knowing rather than worrying about. Server-side counting (how DropRoute records visits) sees every request including fans whose in-app browser blocks scripts, then subtracts known bots and previews; script-based counting sees only visitors who ran JavaScript and got past ad blockers, which silently drops a real slice of a music audience. Neither is lying; they are answering with different rulers.
The practical rule: pick one source of truth per question. Page performance questions (visits, clicks, CTR) belong to the tool doing server-side counting on the page itself. Ad attribution questions belong to the ad platform’s pixel. Cross-site behaviour questions belong to GA. Reconciling their totals to the decimal is not a solvable problem, and chasing it wastes evenings that release weeks do not have.
What does "good" look like?
Ranges, honestly labelled as rough: release pages reached by people who chose to tap (a story, a bio, a QR scan) commonly convert somewhere between 40% and 70% of human visits into destination clicks, because the visitor arrived already wanting the song. Paid and cold traffic converts far lower — 10% to 30% is unremarkable — because the click that brought them was cheaper to give. Bio pages sit lower still, which is not failure; a bio visitor came to browse.
Treat those bands as orientation, not judgment. The number that deserves your attention is your own trend: this release’s CTR against your last one’s, this channel’s signups against that channel’s, week two against week one. Cross-artist benchmarks flatten genre, audience temperature, and traffic source into one misleading average.
The question each metric can answer
- Human visits answer: did the promotion move anyone at all?
- Click-through rate answers: did the page and its ordering do their job for the people who arrived?
- The service split answers: where does this audience actually listen — and what should be first on the page?
- Campaign comparison answers: which channel earned the next dollar or hour?
- Fan signups answer: how much of this attention did I get to keep?
- No link metric answers: how much was streamed. Only the provider knows, and only your distributor reports it.
Reading the numbers like they matter
Compare like with like: campaign variants of the same release against each other, not a release page against a bio page. Watch click-through rate over raw clicks — traffic you paid for should convert, and a falling CTR with rising visits usually means the wrong audience. And weigh a signup as worth many clicks: the click is rented attention on someone else’s platform; the email is a relationship you keep.
DropRoute’s dashboard labels every metric with exactly what it measures, keeps non-human traffic out of the defaults, and uses the word "stream" only when an authorized provider returned one. We think that should be table stakes; read any tool’s numbers — including ours — with these definitions in hand.