Bounties
Bounties are paid or points-based fan actions. Use them when you want fans to do a specific job: share a release, attend an event, add a song to a playlist, buy merch, or submit proof of another action.
Active bounties can be discovered on Bandruption's public bounty pages, and admins manage them from Admin → Bounties.
Good Bounty Examples
| Goal | Bounty setup | Suggested reward |
|---|---|---|
| Release-week sharing | Criterion: Share resource. Note: "Post the new single link to Instagram Stories, tag the artist, and upload a screenshot." | 100 loyalty points or a supporter badge |
| Drive ticket sales | Criterion: Purchase ticket. Target type: Event. Target ID: the event slug or ID. | Ticket upgrade raffle entry |
| Build playlist reach | Criterion: Add playlist. Target type: Song. Target ID: the song slug or ID. | Discount code or exclusive content |
| Reward street team work | Criterion: External verification. Note: "Put up one approved poster and upload a photo with location." | Merch item or custom perk |
| Grow social following | Criterion: Follow artist. Target type: Artist. Target ID: the artist username. | 50 loyalty points |
Field Guide
| Field | What to enter | Example |
|---|---|---|
| Title | A short fan-facing action statement | Share our new single on Instagram |
| Description | What the fan must do and what proof they should submit | Post the track link in a story, tag the artist, and submit a screenshot. |
| Genre | Optional discovery label | J-pop, punk, hip-hop |
| Completion logic | Whether all criteria must be met or any one criterion is enough | All criteria for multi-step tasks |
| Start Date | Optional first day claims can start | Leave blank for immediate launch |
| End Date | Optional last day claims can be submitted | Use a release-week or event deadline |
| Max Claims | Optional total claim cap | 50 for a limited campaign |
| Minimum Completion Time | Seconds a fan must wait before completion | 300 to require at least five minutes |
| Fraud Risk Limit | Optional score ceiling from 0 to 1 | 0.35 for a stricter review threshold |
Criteria
Criteria define what the fan must prove.
- Use Target type when the action is about a specific object, such as an event, song, merch item, playlist, artist, or venue.
- Use Target ID for the object's Bandruption ID, slug, or username.
- Use Instructions / note for fan-facing proof instructions and reviewer context.
Common pairs:
| Criterion type | Target type | Target ID example | Note example |
|---|---|---|---|
| Purchase ticket | Event | event_tokyo_release_party | Buy any ticket for the release party. |
| Add playlist | Song | song_new-single | Submit a screenshot showing the song in your playlist. |
| Share resource | No target | Leave blank | Share the campaign link and upload a screenshot. |
| External verification | Venue | venue_shimokitazawa-basementbar | Upload a photo of the approved poster at the venue. |
Rewards
Rewards define what the fan gets after approval.
| Reward type | Amount | Title | Code | Note |
|---|---|---|---|---|
| Loyalty points | 100 | Leave blank | Leave blank | Auto-awarded after approval. |
| Discount code | 10 | Street team discount | STREETTEAM10 | Applies to merch this month. |
| Perk voucher | Leave blank | Release-week supporter badge | Leave blank | Send voucher after claim approval. |
| Custom | Leave blank | Signed setlist raffle entry | Leave blank | Add approved fans to the raffle sheet. |
Review Workflow
- Create the bounty in Admin → Bounties → Campaigns.
- Fans claim it and submit proof.
- Review pending claims in Admin → Bounties → Claim Review.
- Approve only when the evidence matches the criterion notes.
- Reject claims with missing, unclear, or mismatched proof.
Avoid vague bounties like "support the artist." A good bounty has one visible fan action, one proof requirement, and one clear reward.