Music industry terminology

Playlist analytics

Also called: Music share analytics, Listen analytics, Pitch analytics, Track play analytics

Playlist analytics is per-listener data on who opened a shared music link, which tracks they played, how long they listened to each one, and on what device. In the sync and pitching world, this data turns a sent link from a shot in the dark into an actionable intelligence report.

When you share a playlist link with a supervisor, agency, or client, playlist analytics tells you exactly what happened after they opened it. Which tracks played. How much of each one. Whether they came back. Whether they downloaded anything. This is the difference between following up blind ("just checking in") and following up with intelligence ("I saw you came back to track three twice, happy to send stems").

Why it matters

Most composers have no idea what happens after they hit send. Dropbox, WeTransfer, and Google Drive links have zero listener analytics. You get a yes, a no, or silence. Silence is the most common answer.

Playlist analytics transforms that silence into data. A supervisor who opens your link, listens to one track halfway through, and closes it sent you a signal. So did the one who listened to every track twice and came back the next day. You respond differently to each.

For sync agents and publishers representing large catalogs, analytics scales even further. You can see which composer's tracks are getting the most engagement across all your pitched playlists and allocate pitching resources accordingly.

Analytics also eliminates the ambiguity in follow-ups. "Did you get a chance to listen?" becomes "I saw you spent time on tracks two and four, happy to send alt mixes if those directions are useful." That follow-up converts at a higher rate than the check-in.

How it works

Modern playlist analytics platforms track plays at the track level, not just the link level. That distinction matters: knowing someone opened your playlist link is useful; knowing they played track three for 90 seconds and skipped the others is actionable.

The standard data points in a playlist analytics report:

Play count and listener count. How many times each track played, and how many unique listeners heard it. High play count from one listener means they came back. High listener count means the link got forwarded.

Listen duration. How many seconds of each track a listener heard, usually expressed as a percentage. Completing 80% of a track signals strong interest. Skipping after 10 seconds signals mismatch.

Device and location. What device the listener used (mobile, desktop, tablet) and their approximate city. Useful for understanding how supervisors are reviewing your music (mobile review on a commute means a different format than desktop review at a workstation).

Return visits. Whether the listener came back to the playlist a second or third time. Return visits are the strongest signal of genuine interest.

Most platforms attach these events to a per-recipient share link so you know which named contact did what, not just aggregated totals.

Examples

A composer pitches a trailer music supervisor with a five-track playlist. Analytics shows the supervisor opened the link on a Thursday evening, played 65% of track two, 100% of track four, and returned Saturday to play track four again. The composer emails Monday with "glad to send stems for track four if that direction is working for you." The supervisor replies that afternoon with a brief request for stems. The placement closes the following week.
A sync agent sends a 12-track catalog link to three streaming music supervisors. Analytics shows two of them never opened it, and one opened it, played three tracks halfway, and closed after seven minutes. The agent follows up with the third supervisor specifically about those three tracks. The other two get a different pitch next time.
A production library tracks analytics across 50 pitched playlists over a quarter. They discover that orchestral cues under 90 BPM get the longest listen durations across all recipients. They record 15 more of that style for the next session. The data-driven catalog expansion pays off in the following quarter's placement numbers.

Common mistakes

●Treating analytics as surveillance rather than signal. The goal is not to stalk supervisors. It is to understand what is working and follow up intelligently. One timely, relevant follow-up based on what someone actually listened to beats five check-in emails based on nothing.
●Acting on data too fast. If someone opens your link at 11 PM on a Tuesday, do not follow up at midnight. Read the data, wait for a reasonable window, and reach out with something useful. The data tells you what they listened to, not when they want to hear from you.
●Relying on aggregate totals instead of per-track detail. Knowing your playlist got 50 plays is not the same as knowing which two tracks are driving 80% of the engagement. Per-track listen data is where the pitch intelligence lives.
●Ignoring zero-play links. If someone opened your playlist and played nothing, that is a signal too. The subject line or playlist description did not match their expectations. Update your pitch copy and try a different angle next time.

How DropCue handles this

DropCue's playlist analytics show per-track listen duration, listener location, device, and return visits for every share link. Each recipient gets a unique tracking link so you know which named contact listened to what. Analytics are available on the Starter plan and above.