The Contact List You Actually Own

When a kirtan wraps and the last car leaves the lot, or a retreat closes its gate for the season, what you're left holding isn't just that event's ticket revenue — it's the list of everyone who came, and everyone who almost did. BrightStar collects every opt-in through one path, so a person who bought a ticket, a person who joined your newsletter from your profile page, and a person who asked to be told when you announce the next date all land in the same place, keyed on their email address. What BrightStar knows about each person accumulates as they interact with you again, rather than being overwritten each time they show up in a new context. That list belongs to you, independent of which event or ticket source produced any single entry on it.

Not every name on your list arrived the same way, and BrightStar keeps track of which door each person came through rather than flattening that history. Broadly, contacts arrive in four situations, and knowing which one applies to a given person is part of what makes the list useful later rather than just long.

BrightStar treats consent as something that has to be recorded, not something that can be inferred just because a person is on your list. Someone who ticked a box to hear from you carries an explicit marketing consent, along with the moment it was given. Someone captured through a purely transactional step — clicking through to an external ticket page, for instance — is on your list but is not marked as having agreed to marketing. On top of that, the list carries an unsubscribed state and a suppressed state, and both are honoured at send time regardless of what any earlier consent said. That layering matters at a check-in table or a kirtan door: the fact that someone is in your system because they bought a ticket doesn't automatically give you standing to add them to a newsletter, and BrightStar's records keep that distinction visible instead of quietly merging it away.

Contacts are deduplicated on a normalised form of the email address, so the same person arriving through three different doors — a newsletter signup last spring, a ticket purchase this summer, a waitlist place for the sold-out date after that — does not turn into three separate records. What changes with each arrival is the context attached to that one row: the sources they came through accumulate, and so do the categories, cities, artists and events they showed interest in. Over time that is what turns a plain list of email addresses into something you can actually segment. Writing only to the people whose interest was in a particular city, or who showed interest in a particular artist, is possible because that context built up on a single record over time rather than being scattered across duplicates you'd otherwise have to merge by hand.

Capture on BrightStar is built never to interrupt what the person was doing. If a write to the contact list fails for any reason, the person's signup or purchase still completes — they are not shown an error over a background record that didn't save. That is the right trade-off for the person at the point of sale, but it does mean a contact list is a record of opt-ins rather than an audit log of every transaction. When you need a definitive count of who actually bought — for a door list, for accounting, for anything that has to be exact — reconcile against your orders, not against the contact list.