Why a track is missing from your numbers, and how to fix it

There are two versions of this phone call. Either a single has been out for a week and it is nowhere in your reporting, or a track you re-released is showing a fraction of the streams it used to have, as though the first three years never happened.

Neither is a performance story. Both are questions of identity: the codes attached to the recording, and whether every system counting it agrees on which recording it is. Both are diagnosable in minutes, and both are almost entirely preventable at delivery.

The four things that cause it

No usable code on the recording. A track delivered without a proper ISRC is invisible to anything that counts by recording. It sits on the platform, it accrues streams, and nothing can attach those streams to your catalogue.

Two codes for one recording. Usually a re-release, a distributor change or a compilation appearance. One recording now has two histories, and every total is split between them. Nothing in the data gives this away, because two codes is exactly what two different recordings look like.

One code on two recordings. Rarer and more damaging, because two separate things merge into one and the numbers you are reading belong partly to something else.

The right code, not indexed yet. A track released on Friday can be genuinely unknown to the wider data supply chain for a few days. From the outside this looks identical to a broken code.

That last one is why the rule is to give a new release a few days before treating a gap as a fault. After that, a track that still has not appeared while the rest of the release has is an identity problem rather than a delay, and it is worth chasing immediately.

The codes, and which one you need

The ISRC is the one that matters to you. Twelve characters identifying a single recording, and the only code that travels between platforms, which makes it the thing every cross platform total is built on. A song recorded live and in the studio correctly has two ISRCs, because those are two recordings.

The UPC or EAN is the barcode on the release: the album, EP or single as a product. One UPC contains several ISRCs. It is the right code for release level and retail reporting and the wrong code for looking up a track.

Platforms and analytics providers then keep their own internal identifiers on top of both. Those are theirs to manage, not yours, and in Backline you never see them.

The checklist to hand your distributor

Before delivery, the four that prevent most of the trouble:

• Every recording carries an ISRC, and it is the one you intended.
• A re-release either keeps the original ISRC, if the recording itself is unchanged, or is deliberately treated as new and noted somewhere your reporting can read.
• The UPC is correct on the release and the track order matches.
• Featured artists and the primary artist are consistent across the release, because working out which act a recording belongs to depends on them.

Then in the first week after release:

• Every track has appeared. One that has not, while its siblings have, is a code problem.
• Cross platform totals are plausible against each other. One platform reading zero while the others report normally is almost always a matching failure rather than a performance story.

That second check takes about two minutes in Backline, because a project's tracked songs sit in one ranked list with per platform totals beside each other. A recording that has stopped reporting on one service while the rest keep moving is visible at a glance instead of after an export. The same review sits inside the wider release week data checklist.

When the history is already split

If a recording is carrying two codes and two histories, you have three moves, and all three are workable.

Sum them in your reporting and write the pairing down so it survives the person who spotted it. Pick one as canonical and treat the other as a separate item, which understates the recording but keeps the story simple. Or ask the distributor to consolidate, which does sometimes work, particularly soon after a re-release.

Whichever you pick, it only holds if it is recorded where the reporting lives. In Backline the catalogue is an explicit list you maintain, with streaming, audience and campaign data hanging off it, and every project has a context store that feeds Ask Backline AI. Note the pairing there once and both entries stay visible, the assistant answers with the same understanding of the catalogue that you have, and nobody has to rediscover the decision next quarter.

If the older history predates your current tools entirely, you can upload it from a Spotify for Artists export and Backline merges it into the same timeline, marked as historical so it is never confused with live data. Backfilling streaming history covers how far back that is worth taking.

What Backline takes off your desk

Three of these stop being your problem the moment a project is set up.

Tracks arrive already attached to their artist. Track level reporting needs to know which act a recording belongs to as well as the recording itself, because titles repeat across recorded music and the same track appears on compilations under other banners. Backline establishes that link as a project's catalogue is imported: you pick the artist, choose the songs, and every recording is stored attached to the act it belongs to. Lookups resolve from the project's first day, and songs added later inherit the same link.

A pasted barcode is named, not silently ignored. People paste what is to hand, and sometimes that is a twelve to fourteen digit barcode. Backline recognises the shape and tells you what to paste instead, so you get a usable answer in one step rather than an empty result you have to interpret.

The catalogue and its history stay in one view. Every song, every platform, and any older history you have uploaded, on one timeline per project, so a split or a gap shows up as an obvious break rather than as a number you half remember being higher.

The general rule with these codes has not changed: the cheap fix happens at delivery, and the expensive one happens in reporting, forever. What has changed is that you no longer need to understand the plumbing to catch it.