The artist manager's data stack, by job

Most stack advice is a list of products. That is the wrong shape, because two managers with identical logins can have completely different weeks. What repeats is not the software, it is the jobs: six of them, month after month, whatever the roster looks like.

So here is the stack arranged by job. For each one: what the job genuinely requires, what the free native dashboards hand you, and what a project data layer adds on top.

The stakes are not small. Global recorded music revenues grew 6.4 percent to 31.7 billion United States dollars in 2025, an eleventh consecutive year of growth, with streaming at 69.6 percent of income and 837 million paid subscription users. More money moving through more channels means more places a manager is expected to have an answer.

Job one: knowing what your audience is doing

The job requires a current read on size, direction and location. How many people are listening, is that rising or falling, where are they, and which platforms carry them.

The native tools do the first part well. Spotify for Artists gives you listeners, followers, saves and playlist placement for that service. Each social platform gives you followers and post performance for itself. All of it is free and all of it is accurate about its own platform.

Where the job gets hard is the join. An audience does not live on one service, so a read on the audience means opening six dashboards, each with its own date defaults and its own definition of a period, then holding the differences in your head.

A project data layer does the join for you. Backline puts streaming and catalogue performance, listener cities and countries, and social across Facebook, Instagram and TikTok on one project view under one date window, with a direct TikTok connection covering the artist's own account and their own posts. One window, one set of definitions, one answer to the question of whether the audience grew.

Job two: running and measuring a campaign

The job requires knowing what you spent, what it delivered, and what happened to the artist afterwards.

Meta Ads Manager and Google Ads report spend, impressions, clicks and cost per outcome for their own inventory, in detail. Google Analytics reports what happened on your site. Google Search Console reports the organic search demand that arrived without you paying for it. These are strong tools and they are free.

The gap is the last clause of the job. Ad platforms can tell you what an advert did on the ad platform. They cannot tell you what the release did afterwards, because the release is not their data.

Backline holds advertising alongside the outcome. Meta Ads and Google Ads, including several ad accounts on one project, sit on the same timeline as streaming, smart link clicks, website analytics and Search Console, so spend in a market and response in that market are read together rather than reconstructed from screenshots. Your own smart links are measured in the same place, which means the click data on your landing pages belongs to the project.

Job three: selling tickets

The job requires knowing, per date, whether you will sell out, and knowing it early enough to act.

Ticketing back ends report sales for their own shows. That is the raw material, and it is usually accurate.

What the job actually needs is sell-through against capacity, the shape of the curve between on sale and show day, and the same picture rolled up across a tour so a run of dates can be judged as a run. Backline holds shows on a map with capacity, tickets sold and a pacing curve per date, rolls them up to tour level, and takes an automatic box office feed where a ticketing partner is connected. A date that has not moved in nine days is visible while there is still time to spend against it.

Job four: reporting to a label or an investor

The job requires a document that survives being challenged. Numbers somebody else can check, a window stated up front, and the same shape every month so the comparison is real.

No native dashboard produces this, because each one describes a fraction of the story and none of them knows what you promised. Which is why this job is usually a Sunday evening in a slide deck, copying figures out of tabs.

A data layer collapses that. Backline generates branded downloadable reports from the project's own connected data, and scheduled AI email reports go out on a cadence you choose, with a custom prompt and named recipients, so the monthly arrives without anyone building it. The figures in it are the figures on the dashboard, which is what makes it defensible in the meeting.

Job five: keeping an owned channel

The job requires a route to your audience that no platform can reprice or throttle. In practice that means an email list and your own landing pages.

Mailchimp reports sends, opens and clicks for a campaign. Your link tool reports clicks. Both are fine in isolation.

The value appears when a send is read against what it produced. Backline brings newsletter performance and subscriber counts in next to smart link clicks, streaming and press coverage on the same timeline, so a campaign is judged by what moved after it rather than by its open rate alone. All of it is aggregate measurement: Backline holds no personal data about fans, by design.

Job six: keeping the whole thing in one place

This is the job that decides the stack, and it is the one nobody has time to do by hand.

Every question worth asking crosses a boundary. Did the money we spent in Manchester show up in the box office. Did the press cluster in June move streaming or follow it. Are the cities driving listening the cities we are routing through. Each of those needs two private sources, for one project, on one date axis. No native dashboard can answer them, because each one holds a single side of the question.

Backline is built for that job specifically: one dashboard per managed artist or project, joining streaming and catalogue, audience geography, social, advertising, website analytics, Google Analytics, Search Console, smart links, live shows and ticket pacing, press coverage and newsletter on one shared timeline. On top of it, Ask Backline AI answers questions in plain English from the project's own connected data, audience pools describe the segments that data implies with sizes and recommended actions, and anomaly and milestone alerts tell you when something moved before somebody else notices it.

Putting the order together

For a manager starting from tabs and a spreadsheet, a workable sequence looks like this.

Keep the native dashboards. They are free, they are authoritative about their own platform, and Spotify for Artists in particular is worth opening for the release detail it publishes about its own service.

Then add the layer that joins them, at the point where you are explaining performance to somebody else more than once a month, or the moment a tour is large enough that pacing matters. That threshold arrives earlier than most teams expect, because the explaining starts long before the roster grows.

Everything after that is optional. If you want a checklist for the evaluation itself, what to look for in a music data platform sets out the questions worth asking, and all-in-one management software or a data layer covers the other product category aimed at the same buyer.