MusoSoup campaign result tracking Templates
MusoSoup campaign result tracking
MusoSoup campaign results require systematic tracking across multiple touchpoints — playlist adds, blog coverage, curator responses, and social shares. Unlike platforms with built-in analytics, MusoSoup depends on manual data collection and curator-reported outcomes. These templates help you consolidate results, identify campaign patterns, and present outcomes to stakeholders with clarity and evidence.
Campaign Results Overview Sheet
Use this at the end of a MusoSoup campaign cycle to capture all trackable outcomes in one document
Campaign: [TRACK TITLE] | Period: [START DATE] - [END DATE] Curation Results: • Blog features secured: [NUMBER] across [PLATFORMS] • Playlist adds: [NUMBER] total curators, [AGGREGATE PLAYLIST FOLLOWERS] • Estimated playlist reach: [NUMBER] • Playlist editorial notes received: [YES/NO] - [IF YES: NOTABLE FEEDBACK] Curator Engagement: • Total curators reached: [NUMBER] • Response rate: [PERCENTAGE]% • Positive responses: [NUMBER] • Rejections/No response: [NUMBER] Follow-up Actions Logged: • Curators interested in future releases: [NUMBER] • Blog contacts for next campaign: [NUMBER] • Playlist placements likely to convert: [NUMBER] Notes: [QUALITATIVE OBSERVATIONS ABOUT CURATOR BEHAVIOUR, GENRE-SPECIFIC TRENDS, OR RESPONSE PATTERNS]
Keep genre and mood tags from your original submission alongside these results to spot which tag combinations attracted the strongest curator response. If using a spreadsheet, add columns for curator names and playlist URLs so you can revisit playlists later and check for sustained placement.
Blog Feature Tracking Log
Record every confirmed blog feature separately to build a portfolio of coverage and extract promotion data
[FEATURE DATE] Blog: [PUBLICATION NAME] URL: [LIVE LINK] Author/Contact: [NAME + EMAIL] Content type: [REVIEW / INTERVIEW / PLAYLIST FEATURE / NEWS] Audience size: [FOLLOWER COUNT / MONTHLY READERS IF KNOWN] Social shares generated: [TWITTER / INSTAGRAM / LINKEDIN MENTIONS] Article highlight: [QUOTE OR KEY CLAIM MADE ABOUT YOUR TRACK] Next step: [THANK THEM / SHARE LINK / PITCH NEXT RELEASE] Notable outcome: [DID THIS FEATURE RESULT IN MEASURABLE ENGAGEMENT? LISTENER UPTICK? FOLLOW REQUESTS?]
Use this to build a media list for future campaigns. Bloggers who've covered you once are significantly more likely to cover you again. Flag 'repeat' contacts in a separate section and prioritise them in future MusoSoup campaigns or direct pitching.
Playlist Placement Report
Track playlist additions at the curator level to understand which playlist types drive listens and build curator relationships
Curator Name: [NAME] Playlist Title: [EXACT NAME] Follower Count (at add): [NUMBER] Playlist Type: [EDITORIAL / ALGORITHMIC / CURATOR PERSONAL / NICHE COMMUNITY] Genre Focus: [PRIMARY GENRE] Track Position: [ADDED DATE + ESTIMATED PLAYLIST POSITION] Playlist URL: [LINK] Curator Contact: [EMAIL / TWITTER] Curator Notes: [ANYTHING THEY SAID ABOUT YOUR TRACK] Follow-up tracking (update weekly for first month): • Week 1 follower count change: [+/-NUMBER] • Listener engagement visible: [YES / NO / UNCLEAR] • Playlist stability: [STILL ACTIVE / REMOVED / MOVED] Future opportunity: [WOULD THIS CURATOR TAKE A SECOND TRACK? WILLING TO SHARE?]
Revisit these playlists 2-4 weeks after placement. Curators who've added you and seen engagement are more likely to take future submissions. Create a separate 'hot curator' list from playlists that grew followers or showed visible listener activity.
Campaign Performance by Genre/Mood Tag
Analyse which genre and mood combinations attracted the most curator interest to refine future tagging strategy
Campaign Title: [TRACK] Submission Tags: [LIST ALL GENRE AND MOOD TAGS USED] Tag Performance: [TAG 1] — Curators attracted: [NUMBER] | Responses received: [NUMBER] | Conversion rate: [PERCENTAGE]% [TAG 2] — Curators attracted: [NUMBER] | Responses received: [NUMBER] | Conversion rate: [PERCENTAGE]% [TAG 3] — Curators attracted: [NUMBER] | Responses received: [NUMBER] | Conversion rate: [PERCENTAGE]% Best-performing tags: [RANKED LIST] Weakest-performing tags: [RANKED LIST] Curator feedback on genre fit: • Tags that matched curator expectations: [OBSERVATIONS] • Tags that caused confusion or rejection: [OBSERVATIONS] Recommendation for next release: [ADJUST TAGS / REMOVE WEAK PERFORMERS / ADD RELATED TAGS BASED ON INTEREST SHOWN]
MusoSoup's tagging is critical because it determines which curators see your submission. Track which combinations worked, which attracted unqualified interest, and which failed to generate curator views. This data directly improves your next campaign's reach.
Curator Relationship & Resubmission Pipeline
Maintain a working list of curators open to future submissions, enabling smarter targeting on your next MusoSoup campaign
Curator: [NAME] Initial Feature: [TRACK TITLE + DATE] Curator Type: [BLOG OWNER / PLAYLIST CURATOR / BOTH] Platform: [SPOTIFY / APPLE MUSIC / INDEPENDENT BLOG / MULTI-PLATFORM] Follower Base: [ESTIMATED SIZE] Genre Preferences: [NOTED INTERESTS] Response Quality: • First response time: [FAST / MODERATE / SLOW] • Tone: [PROFESSIONAL / CASUAL / ENTHUSIASTIC] • Feedback given: [YES / NO] Resubmission status: ☐ Open to pitching new tracks ☐ Expressed interest in next release ☐ Requested to be contacted for future submissions ☐ Unlikely to respond again Notes: [ANY PERSONALISATION CLUES / SPECIFIC GENRES THEY SEEK / BEST CONTACT METHOD] Action: [CONTACT VIA MUSOSOUP / DIRECT EMAIL / HOLD FOR LATER / REMOVE FROM PIPELINE]
Curators who've engaged once are gold for future campaigns. Tag this sheet for easy filtering so you can quickly identify which curators to target when your next track is ready. Direct outreach to proven curators often yields faster results than waiting for MusoSoup discovery.
Campaign ROI & Listening Data Snapshot
Connect MusoSoup campaign results to actual streaming outcomes to measure campaign effectiveness
Track: [TITLE] Release Date: [DATE] MusoSoup Campaign Period: [DATES] Campaign Activity: • Curators contacted: [NUMBER] • Confirmed placements: [NUMBER] • Blog features: [NUMBER] • Estimated combined reach: [NUMBER] listeners Listening Data (during campaign period + 4 weeks after): • Spotify streams: [STARTING COUNT] → [CURRENT COUNT] (+[CHANGE]) • Apple Music plays: [CHANGE] • Other platform activity: [CHANGE] • New followers gained: [NUMBER] • Save rate: [PERCENTAGE IF KNOWN] Estimated conversion: • Streams per curator placement: [CALCULATE: TOTAL NEW STREAMS ÷ NUMBER OF PLAYLISTS] • Blog feature impact: [ESTIMATED LISTENER UPLIFT PER FEATURE] Learnings: [WHICH CURATOR TYPES DROVE MOST LISTENS? DID BLOG FEATURES CONVERT? DID PLAYLIST ADDS SUSTAIN?] Next campaign adjustment: [DOUBLE DOWN ON WHAT WORKED / SHIFT FOCUS / EXTEND CAMPAIGN WINDOW]
This template requires patience — you won't have reliable data until 2-4 weeks after campaign launch. Use Spotify for Artists or similar tools to isolate the campaign period's performance. Track this quarterly to build a statistical picture of what MusoSoup actually delivers for your genre and sound.
Rejected & Non-Responsive Curator Analysis
Extract useful signals from rejections and silence to improve future submissions and avoid wasting curator slots
Curator: [NAME] Playlist/Blog: [PUBLICATION] Submission Date: [DATE] Status: [REJECTED / NO RESPONSE / REMOVED AFTER ACCEPTANCE] Rejection feedback (if provided): • Reason given: [EXACT QUOTE OR SUMMARY] • Implied issues: [GENRE FIT / PRODUCTION QUALITY / AUDIENCE MISMATCH / ARTIST STAGE] Context: • Why was this curator targeted: [TAGS USED / MANUAL SELECTION] • Playlist follower count: [NUMBER] • Curator's stated taste/focus: [WHAT THEY SAY THEY LOOK FOR] Analysis: ☐ Valid rejection — this curator was poor fit, avoid in future ☐ Possible timing issue — curators were selective that week ☐ Tag mismatch — our genre tags didn't match their actual scope ☐ Production/vocal issue — feedback suggests remastering or remix worth exploring ☐ Unexplained silence — likely automated or very selective curator Action: [REMOVE FROM PIPELINE / ADJUST TARGETING FOR THIS CURATOR / REVISIT IN 3 MONTHS / IGNORE]
Don't ignore rejections — they contain information. If multiple curators reject on the same grounds, your tagging or positioning needs adjustment. Keep this log separate from successes so you can spot patterns (e.g., does your subgenre attract only 2% response rate across MusoSoup?).
Campaign Post-Launch Checklist & Results Handover
Use this as a final validation step before closing out a MusoSoup campaign and handing results to management or collaborators
Campaign: [TRACK TITLE] | Curator contact phase: [DATES] Data Collection Complete: ☐ All blog features logged with URLs and publication details ☐ All playlist placements recorded with curator contact info ☐ Curator response rates calculated ☐ Blog vs. playlist performance compared ☐ Genre/mood tag performance analysed ☐ Resubmission-ready curator list created ☐ Listening data snapshot collected (minimum 2 weeks post-campaign) Results Validated: ☐ All blog links tested and live ☐ Playlist additions verified (still active or noted as removed) ☐ Curator contact info backed up or noted for future use ☐ Any social shares or mentions logged Report Prepared: ☐ Campaign overview with headline figures ☐ Key wins and lessons documented ☐ Curator pipeline updated for next campaign ☐ Recommendations for next release recorded Stakeholder Handover: • Report recipient: [NAME] • Key metrics they care about: [STREAMS / COVERAGE / ENGAGEMENT / REACH] • Summary headline: [ONE-LINE RESULT] • Next action: [WAITING FOR NEXT TRACK / DIRECT FOLLOW-UP WITH CURATORS / ADJUST STRATEGY]
Use this as your closing checklist. If data is missing, chase curators for confirmation before submitting results. A complete, verified campaign report is far more valuable than one padded with assumptions. This also ensures nothing falls through the cracks between campaign cycles.
Frequently asked questions
How do I know if a MusoSoup playlist placement actually resulted in real listens?
Check the playlist URL directly 1–2 weeks after placement — if it's gained followers, your track likely contributed. Cross-reference with your streaming platform's analytics during the placement period to see if there's a corresponding listener uptick from that curator's follower base or region. Some curators will tell you upfront if the playlist is active and growing; ask them directly if unsure.
Should I track every single rejected or non-responsive curator?
Only if you see patterns — track rejections where feedback was given, or from curators in your target niche, because that signals a positioning problem. Don't waste time logging every silence; instead, focus on high-profile curators or those with specific rejection reasons that might affect your next campaign. After a few campaigns, you'll notice which curator types ignore you systematically.
What's a realistic timeframe to see MusoSoup campaign results?
Blog features typically publish within 2–4 weeks; playlist additions happen immediately but need 2–4 weeks to show listening impact. Don't judge campaign success until at least 4 weeks post-launch — early silence doesn't mean failure, and late placements from slower curators can still drive real streams. Set your measurement window to 6–8 weeks to capture the full tail.
How should I prioritise MusoSoup results against other PR activity in my campaign report?
Isolate MusoSoup placements separately from your other PR efforts so you can measure its specific contribution. If you ran MusoSoup alongside email pitching, radio plugging, or social campaigns, track each channel's results independently — this is the only way to know whether MusoSoup is worth repeating or repositioning in future campaigns. Some tracks might get 10 times more value from direct outreach; MusoSoup data will prove it.
What should I do if a curator adds my track but it disappears within a week?
Early removals usually mean the curator was testing placement or your track didn't fit audience expectations — note it and move on. If it happens repeatedly across multiple curators, your audio or positioning is likely off-target; use that as a signal to adjust genre tags or reconsider the track's fit for MusoSoup. One-off removals are normal; patterns of removal signal a bigger issue.
Related resources
Run your music PR campaigns in TAP
The professional platform for UK music PR agencies. Contact intelligence, pitch drafting, and campaign tracking — without the spreadsheets.