Workflow
How to track who listened to your music
Tracking who listened to your music means sending playlists through a platform with per-recipient analytics, checking the dashboard after sending, identifying which supervisors spent real time on which tracks, and using that data to prioritize follow-up conversations.
Most composers send a pitch and then guess. Did they open it? Did they actually listen? Which track landed? Analytics on shared music playlists answer those questions precisely. A supervisor who listened to 4 minutes of your horror track is a warm lead. A supervisor who opened but played nothing is a cold one. Knowing the difference before you follow up changes your entire outreach strategy.
Who does this
Composers and sync agents who send music to supervisors, labels, or clients and want to know whether it was actually heard. Also relevant for music libraries sharing catalogs with licensing teams, and for labels tracking which A&R contacts engage with demo links.
Anyone who has ever sent a pitch email and wondered "did they even listen" needs this workflow.
Step by step
- 1
Choose a sharing platform with per-track analytics
Not all sharing tools give you the same data. A platform that shows "link opened" is not the same as one that shows "listened to track 3 for 2 minutes 45 seconds and skipped track 4 entirely." You need per-track listening data to run a useful follow-up strategy. Email open tracking and basic link click tracking are not enough.
- ✓Per-track play time: essential. Tells you which tracks land.
- ✓Listener identity: essential. Tells you who to follow up with.
- ✓Geographic data: useful. Confirms the right person opened it.
- ✓Download events: useful. A download is a strong buying signal.
- 2
Build your playlist and enable analytics before sending
Set up the shareable link through your analytics platform before sending the pitch. Most platforms generate a unique link per playlist. Some generate per-recipient links so you can see exactly which supervisor listened versus a generic "someone from Los Angeles listened." Per-recipient links are significantly more useful than aggregate playlist stats.
- ✓Use per-recipient share links when possible for precise attribution
- ✓Confirm analytics are active on the link before sending
- ✓Set link expiry if the material is time-sensitive or embargoed
- 3
Send the pitch and note the time
Log the send time in your pitch tracker. Many supervisors review pitches in batches early morning or late afternoon. Knowing when you sent versus when they listened tells you something about their review habits. A pitch opened at 7 AM the day after you sent it means you are in the morning review queue. That is useful to know for your next send.
- ✓Log: supervisor name, send time, playlist name, link
- ✓Do not check analytics obsessively in the first 48 hours
- ✓Allow at least 5 to 7 business days before drawing conclusions
- 4
Review the analytics dashboard at 7 days
Give the pitch a full week to breathe before your first analytics review. Check who opened the link, which tracks they played, how long they spent on each, and whether they downloaded anything. This gives you a clear picture of which recipients engaged and which did not.
- ✓Classify each recipient: engaged (2+ min total), skimmed (played but brief), unopened
- ✓Note which specific tracks got the most time
- ✓Downloads are the strongest engagement signal
- 5
Build a warm leads list from the data
Any recipient who listened to more than 2 minutes of your playlist is a warm lead. Any recipient who downloaded a track is a hot lead. Build a tiered follow-up list from this data: hot leads get a tailored follow-up referencing the specific tracks they listened to. Warm leads get a standard follow-up. Cold leads (no engagement) get deprioritized or re-targeted with different tracks.
- ✓Hot: downloaded a track or listened to 4+ minutes
- ✓Warm: played multiple tracks, 1 to 4 minutes total
- ✓Cold: opened but played nothing, or never opened
- 6
Follow up with hot and warm leads referencing the data
When you follow up with a supervisor who spent 3 minutes on track 2, you can reference that specifically: "I saw you spent some time on the hybrid orchestral piece — I have three more in that direction if you want them." This shows you are paying attention without being creepy, and it immediately makes the follow-up more relevant than a generic "just checking in."
- ✓Reference the specific track they engaged with, not the whole playlist
- ✓Offer to send more in the same direction
- ✓Do not say "I can see you listened for exactly 2:47" — the specificity crosses into surveillance vibes
- 7
Archive the data and use it to improve future pitches
After 30 days, review the analytics across all your recent pitches. Which tracks consistently get the most time? Which get skipped? Which generate the most downloads? This aggregate picture tells you which tracks should lead your future playlists and which might need to come out of rotation. Analytics are not just follow-up intelligence. They are product feedback on your music.
- ✓Top-performing track = lead track on your next pitch to similar supervisors
- ✓Consistently skipped track = remove from pitch rotation or rework it
- ✓Zero engagement across 10 sends = wrong audience, not bad track
What can go wrong
- ●Using a platform that only shows aggregate stats. "347 plays" across all listeners tells you nothing useful. You need to know which specific recipients engaged.
- ●Following up too quickly based on partial data. A supervisor who opened on day 1 but played nothing may come back on day 6 when they have more time. Wait the full 7 days.
- ●Over-reading the data. Analytics show behavior, not intent. A supervisor who listened to all 8 tracks might have been auditing format, not genuinely considering. A download does not guarantee a placement. Use the data to prioritize, not to predict.
- ●Referencing the data too explicitly in follow-up emails. Saying "I can see you listened to track 3 at 2:47 PM yesterday" is accurate but unsettling. Reference the track, not the timestamp.
- ●Not building a warm leads list after reviewing. The analytics are only useful if they change your behavior. If you check the data and then treat all recipients the same anyway, you might as well not have the data.
Pro tips
The supervisor who downloads a track without replying to your email is not ignoring you. They are keeping their options open. A download is a genuine buying signal. Follow up warmly, not urgently.
Track open patterns over time to learn each supervisor's habits. If a specific person always opens your emails Tuesday morning, send to them Monday night. Tiny optimization, but across 50 pitches it compounds.
Use the "which track got the most time" data to inform your next album or EP. If hybrid orchestral consistently outperforms your cinematic ambient tracks with supervisors, that is a market signal worth paying attention to.
Share your analytics summary with a sync agent when you are pitching them for representation. Showing them "this playlist has been opened 23 times with 14 minutes of average listening time" demonstrates professionalism and market traction. Most composers bring a playlist. You bring a playlist with receipts.
Tools that help
DropCue
DropCue shows per-track listening time, per-recipient analytics when you use unique share links for each contact, geographic data, device type, and download events. The analytics dashboard surfaces your hottest leads automatically. You can see at a glance which supervisor spent the most time, on which tracks, and when.
DISCO.ac
Offers playlist analytics with open and play data. Used widely in the sync industry. Interface is familiar to many supervisors which helps with adoption. Analytics depth varies by plan.
Dropbox or Google Drive
No listening analytics. You can see if the link was clicked but not whether anyone actually played the audio files. Not suitable for pitch analytics.
Email open tracking (Mailtrack, HubSpot)
Shows email opens but not music listening. Useful as a first-layer signal but tells you nothing about whether anyone pressed play once they clicked through.