1001Tracklists

What Stevin gets out of 1001Tracklists

In the dance world, 1001Tracklists is where track support becomes visible: who plays your record, in which set, on which stage. That is not invented authority, it is what the scene itself looks at. What it is not is a marketing tool. It records that a big name spun your track, and then does nothing further with it. That is where artists and labels get stuck: the validation sits in the profile, the action never comes. A sudden run of plays after a festival is exactly the moment to promote something, but that moment slips by while no one is watching. Stevin runs as a layer over 1001Tracklists, reads the support in via scrape or feed, and turns a spike in plays into a concrete proposal: turn on a region here, push the release there. The person decides, Stevin signals it in time.

What you pair it with

Choosing 1001Tracklists as a source means accepting that the connection is rough: there is no clean public API, so count on a scrape or a manual export and on data that is not real time. It tells you who is playing your tracks, but nothing about what that earns, so you need your streaming and social data alongside it to give a play spike meaning. On its own it is a nice scoreboard, not a steering tool. So the real question is not whether you see the support, but whether something is ready to act on a spike before the moment passes.

Common mistakes

• →Treating support as a goal in itself, when a big name spinning your track only has value once you tie promotion to it.
• →Relying on real-time data when the scrape can be delayed or incomplete.
• →Seeing a play spike but having no streaming data alongside it to know whether it earned anything.