Listening parties are live scheduled events on TrackGiant where music plays in order to a group of attendees. A host controls flow, moderates the queue, and (for many curator-hosted events) can enable paid queue tiers so people can pay to move up in line — those monetized sessions are often called Live Sessions in product copy.
This feature overview stays product-true; for tactics see run a successful Live Session (hosts) or host your first party (artists).
Core objects
Event — title, description, scheduled start, visibility rules, and queue configuration.
Host — runs the room, advances playback, enforces rules. Can be a curator, artist, or other supported account types depending on dashboard capabilities.
Attendee — joins, listens, may submit tracks to the queue per event rules.
Queue — ordered list of tracks waiting for airtime. Can be free-only or include paid skips.
Lifecycle
- Created — host configures the party in the dashboard.
- Scheduled — attendees see it on listings / profile surfaces as the product exposes them.
- Live — audio plays in order; chat or presence features behave per client version.
- Ended — queue closes; analytics and revenue (if any) settle.
Audio sources
Hosts should verify stable URLs or uploaded audio before going live. Dead links waste paid queue purchases and burn trust.
Free queue behavior
Attendees at the back of the line wait their turn. Hosts may:
- Cap submissions per person.
- Limit track length (“first 90 seconds only” for packed rooms).
- Rotate between fan tracks and host picks.
Paid queue tiers
When enabled, attendees purchase tiered jumps (Skip, Super Skip, Headliner — names in UI). Revenue shares subtract platform fees and processing; hosts receive the remainder after settlement.
Deep dive: paid queue tiers.
Listening parties vs. track submissions
| Feature | Listening party | Track submission | | --- | --- | | Format | Live group | Async 1:1 | | Output | Room reaction + optional notes | Written review inside 7-day SLA | | Money | Optional queue purchases | Fixed review price |
Parties are energy and community; submissions are decision documentation.
Discovery and profile
Hosts often link parties from their public profile — part of why TrackGiant behaves like a link-in-bio hub.
Moderation and safety
Hosts should plan for:
- Explicit lyrics warnings.
- Copyright prudence — only play audio you have rights to broadcast in your context.
- Harassment tooling as provided by the client — report paths exist for a reason.
After the party
Hosts: log what converted (queue revenue, new followers, downstream service inquiries).
Artists: log what you learned about mixes; follow up with paid reviews if you need curator-grade notes.
Glossary cross-link
Terminology index: TrackGiant glossary.
Listening parties are the live pulse of the platform — use them when time-bound feedback matters; use submissions when you need quiet, written judgment.