How to track DJ support accurately
Maintain evidence-based records of plays, charts, radio, feedback, permissions, dates, versions, and campaign source.
DJ support is useful social proof only when it is accurate. A support log should distinguish private feedback, promo downloads, public charts, radio plays, and verified set use.
Use this guide as an operating brief, then adapt the sequence to your audience, catalog, distributor, and the current rules of every store or platform involved.
What matters
- Create separate support types with evidence requirements
- Record DJ, date, track version, source, and public URL
- Ask permission before publishing private messages
- Expire or update claims when context changes
Set the objective
DJ support is useful social proof only when it is accurate. A support log should distinguish private feedback, promo downloads, public charts, radio plays, and verified set use.
Write down the decision this work should improve and the person it is meant to help. A narrow objective makes the campaign easier to execute and easier to review.
A practical workflow
Complete the work in order. Each step should produce something another collaborator can verify instead of relying on an informal assumption.
- Create separate support types with evidence requirements
- Record DJ, date, track version, source, and public URL
- Ask permission before publishing private messages
- Expire or update claims when context changes
Quality check
Review these items before the page, message, or campaign goes live. Correcting them early is usually cheaper than repairing mismatched links and expectations later.
- Every public claim links to or stores evidence
- A promo download is not labeled as a play
- Names and affiliations are current
- Screenshots preserve date and source context
Measure useful progress
Record a small set of signals that connect activity to real audience behavior. Keep timestamps and source context so one release can be compared fairly with the next.
- Verified support by audience segment
- Traffic following public support
- Repeat support across releases
- Permission response time
Avoid common failure modes
Do not trade durable audience trust for a short-lived vanity result. These are the warning signs to catch during review.
- Turning private feedback into a testimonial
- Counting unplayed downloads as support
- Using outdated logos or affiliations