City data, country data, and which one to trust
Audience geography arrives at two granularities that will never reconcile. Which one to trust for which decision, and how Backline keeps both in one view per project.
Danny Starr
Co-founder, Backline · 24 June 2026 · 3 min read
In short
- City data and country data are separate measurements with different methods, so they will not reconcile exactly and are not meant to.
- City granularity is for live decisions. Country granularity is for market and rights decisions. Using one for the other is the common mistake.
- Compare current against peak per market. A large current number sitting at a fraction of a peak set two years ago is a historic market, not an opportunity.
- Different platforms genuinely disagree, and that disagreement tells you which audience is on which platform rather than being an error to average away.
- Backline holds listener cities and countries per project next to ticket sales, campaign spend and press, so a routing question and a market question are answered in the same place.
Audience geography looks like one dataset and is several. Knowing which one you are reading decides whether the decision you make from it holds up.
Backline keeps both granularities on one project dashboard, sitting next to that artist's ticket sales, campaign spend and press coverage. That matters more than it sounds. Most geography questions are really two questions at once: where is the audience, and what has already happened there.
Two granularities, two purposes
City data arrives as a list of top cities with a current and often a peak listener figure. It exists because streaming platforms carry a location signal per listener, and city is the finest granularity anyone publishes.
Use it for live decisions. Which rooms, which regions, where the audience is dense enough to fill a venue.
Country data arrives per platform, produced by a different method and covering a different population.
Use it for market decisions. Which territories to service, where to prioritise press and radio, which language and timezone assumptions to make, which rights and distribution questions to ask.
Which granularity for which decision
Illustrative| Use it for | Do not use it for | Watch out for | |
|---|---|---|---|
| City | Routing, venue size, local press and radio | Territory strategy or rights questions | Top N truncation, weaker attribution |
| Country | Market priorities, language, timezone, distribution | Choosing which room to book | Hides whether an audience is concentrated or diffuse |
| Per-platform country | Deciding which platform's tools to use in a market | A single blended audience figure | Different units per platform |
The mistake runs in both directions. Using city data for a market decision over-weights whichever city happens to be measured well. Using country data for routing tells you Germany is strong without telling you whether that means Berlin, Cologne, or a diffuse audience with no venue anywhere.
They will not reconcile, and that is fine
Sum a project's top cities, compare the result against its country totals, and the numbers will not match. There are three legitimate reasons.
Top cities is a top N, so everything below the cut is missing. City attribution fails more often than country attribution, because it needs a finer location signal. And the two figures are frequently produced from different measurements over different windows.
Treat them as two views rather than one dataset, and do not build a plan that requires them to agree. Backline shows them as two views for exactly that reason: a city panel for routing work and a country map for territory work, each labelled with what it counts.
Platforms disagree, informatively
The same project can look concentrated in one country on one platform and spread across several on another.
That is not an error to average away. Platforms have different user bases by region and by demographic, so a divergence is telling you something real: which audience is on which platform, and therefore which platform's own tools to use to reach a given market.
The one thing to avoid is blending them into a single audience-by-country figure. A follower on one platform, a monthly listener on another and a subscriber on a third are different units, and a weighted average of them means nothing. Backline keeps the units separate and prints them, so nobody has to guess whether a number is people or plays.
Reading it well
Current against peak, per market. The single most useful comparison. A market sitting at a third of a peak set two years ago is history, not opportunity.
Share, not count. A market growing as a share of your audience is more informative than one growing in absolute terms while your total grows faster.
Over-index, not rank. Divide your share of a market by that market's expected share. The ranking that produces is the one worth acting on, as covered in finding core markets from your own data.
Wait after a placement. During and immediately after a large placement, geography reflects the playlist's audience rather than yours. Re-read three weeks later.
Asking the geography a question
Geography gets more useful the moment it is read alongside what you have already sold. That is the job Ask Backline AI does: it answers from the project's own connected data, names which source each claim came from, and says so plainly when the data does not support an answer.
Reading city and country geography together
IllustrativeWhich UK cities should we look at for a spring run, and does the country picture agree?
Data readAudience geographyLive shows and ticket pacingStreaming
Manchester, Glasgow and Bristol are Nine Mile Tide's three densest UK cities by current listeners, and all three sit close to their own peak, so that audience is present rather than historic.
London is much larger in absolute terms but sits at roughly half its peak. Treat it as a market to re-earn rather than a safe room.
The country view agrees that the UK is the strongest territory, but it cannot see the split above.
Ireland ranks fourth by country with no city above the reporting floor, which usually means a diffuse audience rather than one bookable room.
You have sold tickets in Manchester and Bristol before, both with strong sell-through. Glasgow would be the untested room of the three.
Illustrative. The assistant read Nine Mile Tide's connected geography and its own past ticket data, and separated what each source could support. It gave no Irish city figure, because none was above the reporting floor.
What geography locates, and what it leaves to you
It locates an audience without holding a record of any individual. Aggregate counts by city and country answer every question a manager has about where an audience is, which is why Backline stores no fan personal data at all.
What it will not do is explain why a market is strong. Data locates, people explain. The answer is usually a support slot, a station, a scene or a sync, and finding it takes a phone call rather than another query. Geography tells you which call to make.
Common questions
- Why don't my top cities add up to my country totals?
- Because they are different measurements. Top cities is a truncated list, so everything below the cut is missing, city-level location attribution fails more often than country-level attribution, and the two figures are often produced over different windows. They are two views rather than one dataset.
- Which is better for tour routing, city or country data?
- City data, because a venue serves a region and country data cannot tell you whether a strong country means one dense city or a diffuse audience with no obvious venue. Country data is the right granularity for market priorities, language, timezone and distribution decisions.
- Where can I see listener cities and countries for a project in one place?
- Backline puts both on the same project dashboard: a top-cities view with current and peak listeners for routing decisions, and a country map with per-platform breakdowns for territory decisions, alongside that project's ticket sales, advertising and press coverage on a shared timeline.
Sources
- 1Spotify for Artists, Reviewed August 2026. Data in Spotify for Artists
- 2Music Business Worldwide, 2026. Half of all paid music streams globally still take place in just 4 countries
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
Audience
Finding a project's core markets from its own data
Your biggest cities are usually just the biggest cities. A method for separating markets where you genuinely over-perform, and how to run it in Backline against your own audience data.
Danny Angove · 5 min read
Audience
Deriving audience segments without any personal data
Backline derives named, actionable audience segments for a music project from aggregate data, each with a size, a confidence level and recommended actions, and no fan-level records anywhere.
Danny Starr · 4 min read
Live and ticketing
Routing a tour with streaming data, carefully
Streaming geography is the best routing input most artists have and the easiest to over-trust. How to use it alongside the signals that actually predict who turns up.
Danny Angove · 4 min read