Get your event in front of other organizers' buyers

The moment right after someone finishes buying a ticket is unlike almost any other moment in the relationship you have with them. They are still thinking about the kind of gathering they just committed to — a kirtan, a weekend retreat, a sound healing circle — and they are more open to hearing about something similar than they will ever be again once the confirmation email is closed and forgotten. Most ticketing systems waste that moment on a bare receipt. BrightStar does not. Related events appear right on the confirmation page and inside the confirmation and reminder emails, and because every organizer's buyers see the same module, the arrangement runs both ways: your event surfaces to someone who just bought from another organizer, and theirs surfaces to someone who just bought from you. Neither of you has to ask the other, arrange anything, or even know it happened — the exchange is built into the receipt itself.

You are not locked into one behavior. Auto lets BrightStar pick related events from other organizers on your behalf. Manual restricts the module to only the events you have hand-picked for that specific listing. Off turns recommendations off entirely, so nothing appears in that slot.

If you never touch the setting, BrightStar applies a default that depends on what you have already done: manual if you have hand-picked events for that listing, auto if you have not. That protects a curated set of picks from being silently replaced — an organizer who spent time hand-selecting a companion retreat will keep seeing exactly that, not a fresh batch chosen automatically. You can also set a default for your whole account and override it event by event, which matters if some of your listings suit cross-promotion and others don't.

In auto mode, BrightStar is not filling slots for the sake of it — it is looking for genuine adjacency. A shared teacher counts for the most, since a buyer who just booked a class with a particular facilitator is a strong candidate for another event with that same person. After that comes the same category, then shared tags, then proximity: the same city first, and otherwise something within a reasonable travelling distance. Popularity is only used to break whatever ties remain.

Every recommendation carries a short badge explaining why it was picked, and that badge tells the truth rather than dressing up a filler slot. A buyer sees the actual reason — same teacher, same city, same tags — rather than a vague "you might also like." That honesty is what keeps the module reading as a useful suggestion on a receipt instead of an advert bolted onto it.

Auto recommendations are also built to avoid embarrassing you or wasting the buyer's time. Sold-out, paused, hidden, draft, cancelled and past events are all excluded, because a link to something nobody can actually book helps no one. Your own events are excluded too — someone who has just bought a ticket from you doesn't need to be sold the rest of your catalogue on their receipt; that slot exists for the exchange with other organizers, not for a second pitch of your own.

You also have a say in the shape of what shows up. You can name the categories you're willing to have promoted alongside your event and the categories you are not, so a listing whose audience would be poorly served by a particular kind of event never has to carry that recommendation.

The confirmation page, the confirmation email, the reminder emails and the checkout page all pull from the same recommendation logic rather than each running its own version. That matters because a buyer who sees a suggestion on the confirmation screen right after checkout, then opens a reminder email a couple of weeks before the event, should be looking at consistent reasoning, not three implementations that have quietly drifted apart over time.

The number of recommendations shown is kept small by default rather than turned into a long list, on the logic that a receipt with a few well-chosen suggestions converts better than one crowded with twenty options nobody reads closely. If you want to see what the module has actually produced — rather than assume it's working — that reporting lives in the upsells report in your organizer dashboard.