How to Segment Bandcamp Messages for a Music Release
A practical guide to choosing audience groups for Bandcamp release messages by location, support history, and the usefulness of the update.
The short answer
Segment Bandcamp release messages only when the recipient group has a genuinely different reason to receive the update. Start with the message's action, then choose all followers, a location group, or a support-level group if the current Bandcamp tools and your evidence support that choice. Keep a general release note broad, make local updates relevant to a place, and reserve purchase or thank-you messages for appropriate supporters. Review replies and available source signals without treating them as guaranteed outcomes.
Three things to know
- 01
Segment by message relevance, not by the desire to make a campaign look more sophisticated.
- 02
Location can make a show or local event update useful, while support history can shape a thank-you or product follow-up.
- 03
A broad release announcement and a targeted follow-up can coexist when each has a different job.
- 04
Bandcamp's current tools and the artist's available evidence should determine which audience groups are actually usable.
What is a Bandcamp message segment for?
A segment is a deliberately chosen group of followers or supporters for one message. It should answer a practical question: who needs this information, and why now? A release announcement may belong with the whole relevant follower base. A show reminder may fit listeners in a city. A thank-you or merch follow-up may fit people whose support history makes the note meaningful. Segmentation is useful when it changes relevance, not when it adds labels without a different message or action.
When should a release message go to everyone?
Use a broad message when the update applies to the artist's follower base and does not depend on geography or previous support. Examples include a new release, a substantial artist update, or a listening invitation that is open to everyone. Keep the note specific about what is available and what action helps. A broad send is not a failure of targeting; it is often the clearest choice when the news itself is broad.
When does location make a Bandcamp message more useful?
Location is relevant when the message depends on being near a place or route: a show, local collaboration, pickup detail, regional event, or tour announcement. Do not infer that a listener will attend because they appear in a region. Use location as a reason to make the invitation relevant, then give the person enough detail to decide. Bandcamp's Artist Guide describes artist messaging that can be targeted by fan location, but teams should verify the current tool behavior before building a workflow around a setting.
When does support history change the message?
Support history can help distinguish a thank-you, product note, or follow-up for people who have already bought or supported from a general announcement for followers who have not. The content should respect that difference: thank a supporter, explain a related item, or share a fitting update rather than assuming another purchase. Do not treat past support as permission to send unrelated messages, and do not describe a supporter group more precisely than the current Bandcamp tools and records allow.
How should a team choose the message and primary action?
Write the action before selecting the audience. For a release note, the action might be listen, buy, follow, wishlist, or share. For a local note, it might be check the date or reply about a city. For a supporter note, it might be read a thank-you, view a bundle, or learn about fulfillment. Keep one primary action, explain why it matters, and make another destination available when fans need a different path. This prevents a segment from becoming a generic sales blast.
How should artists sequence broad and targeted messages?
Use the broad announcement for the release fact, then send a targeted follow-up only when it adds new value. A short sequence might announce an EP to all relevant followers, share a location-specific show note with nearby fans, and send a supporter thank-you with a behind-the-scenes detail. Do not repeat the same request to every group. Pause when the next message has no new information, and keep a simple record of date, audience, action, link, and owner.
What should artists review after sending a segment message?
Review the signals available in the current artist tools: replies, follows, purchases, wishlists, clicks or visits where tracked, and source information. Compare those signals with the message's audience and action, but avoid claiming that one message caused every later result. Constructed example: an artist could send an album announcement broadly, a nearby-show note to a location group, and a thank-you to prior supporters. The groups and timing are illustrative, not a performance formula.
Frequently asked questions
- Should every Bandcamp release message be segmented?
- No. Segment only when location, support history, or another documented distinction makes the message more relevant than a broad release note.
- Can Bandcamp messages be targeted by location?
- Bandcamp's Artist Guide describes location-targeted artist messaging. Verify the current tools and available audience data before relying on a particular setting.
- Should artists message previous buyers about every new product?
- Not automatically. Use support history for relevant thanks or offers, and make the new message useful rather than assuming another purchase.
- Is a broad Bandcamp release announcement a bad idea?
- No. A broad announcement is appropriate when the release news and primary action apply to the relevant follower base.
- Does Bandcamp message segmentation guarantee more sales?
- No. Segmentation can improve relevance, but it cannot guarantee purchases, streams, replies, attendance, or audience growth.
- How often should an artist send segmented Bandcamp messages?
- Use a small sequence with new information, then pause when the next message would repeat the same request without added value.