Contact Lists, Campaigns, and Private Registration: The New Way to Run Invite-Driven Events

If you run events for the same group of people more than once — members, customers, partners, prospects — you already have a list problem. It lives in a spreadsheet, or three spreadsheets, or a CRM export that's two months stale by the time you build your next event. Every event, you rebuild the list, rebuild the emails, and manually figure out who gets the member price and who gets asked which questions. Event registration software was supposed to fix this. For most organizers, it hasn't.

Sunfish Events now ties five features together so you can manage a contact from first invite through post-event follow-up without leaving the platform: Contact Lists, Campaigns, Private/Invite-Only Registration, Request Access, and Group Assignment. This post is the overview — how the five pieces fit together — with links out to a deep-dive on each one.

Who this is for, and what "invite-driven" means

This is built for SMB corporate event teams, associations, nonprofits, and trade show organizers — the people running events where the audience is a known group, not an anonymous public. If your events are ticketed to the general public with no real concept of "who's supposed to be here," most of this won't apply to you, and that's fine. This isn't built for consumer events or Eventbrite-style public listings, and it's not trying to be.

"Invite-driven" is the category this post is naming: an event where you know who your audience is before registration opens, where different segments of that audience should see different prices or questions, and where you want to reach people more than once — before they register, if they stall out mid-form, and after the event ends. A member conference is invite-driven. A customer advisory event is invite-driven. A quarterly town hall for company employees is invite-driven. A public trade show with open ticket sales, run once with no real recurring audience, mostly isn't — though even then, Contact Lists and Campaigns still have a job to do, which we'll get to in the FAQ below.

The real problem with event registration software today

Most event registration software treats each event as a blank slate. You import a spreadsheet, build a form, send a Mailchimp campaign from a separate list that's already out of sync, and hope the person who registered as "staff" last quarter doesn't get charged the non-member rate this quarter. None of these tools talk to each other, so you're the integration layer — copying, checking, and re-checking by hand.

That's the gap Sunfish is closing. Instead of a registration form bolted onto a payment page, Sunfish now manages the relationship: who's on your list, whether they're invited or need to request access, what they pay and what they're asked, and every email they get before and after the event. One example makes this concrete.

Meet the association running this on Sunfish

Picture a mid-size professional association: a few thousand members, a handful of non-member prospects who attend occasionally, and one flagship annual conference plus a few smaller regional events each year. Today, their coordinator maintains a master member spreadsheet, exports segments for each event, and manually tracks who's paid the member rate versus the guest rate. Every event, that work starts over. Here's what changes when the same organization builds it on Sunfish instead.

Start with the list, not the event

The coordinator's first move isn't creating an event — it's building a contact list at the org level, once. Sunfish Contact Lists come in two flavors: "Attendee Updates" lists, for people already registered in an event, and "Invite and Promote" lists, for people not yet in the event who you want to invite. Invite and Promote lists are the ones that make multi-event organizations stop starting from zero — they're saved at the org level and imported into whichever event needs them, so the member roster the coordinator builds in January is still there, current, in April.

Attendee Update lists add another layer: they can be dynamic, manual, or both. A dynamic list automatically adds and removes people as they match or stop matching criteria you set — group, ticket type, registration status, custom question answers, domain, add-ons purchased, and more. A manual list is just the people you've explicitly put on it. You can mix both in the same list, which matters more than it sounds like — for a walkthrough of when each type earns its keep, see our post on dynamic vs. manual attendee lists. For the org-level, build-once approach itself, the deep dive is reusable invite lists for every event.

Decide who gets in: open registration or invite-only

With the list built, the coordinator has to decide how each event should be gated. A regional happy-hour meetup can stay wide open — anyone with the link registers. The flagship conference, which includes a private board strategy session and member-only pricing tiers worth protecting, is a different story.

For events like that, Sunfish lets you flip a toggle to make registration private, restricted to people on your invite lists. Pair that toggle with login, and people have to receive an invite email and log in before they can even see the registration form — a meaningfully higher bar than a guessable URL. This is the setting to reach for whenever an event has pricing, content, or attendee lists you don't want showing up in a search engine or getting forwarded around. Our invite-only event registration guide covers when to use the toggle alone versus pairing it with login, and how it changes the attendee's path through the form.

The person you forgot to invite

Invite-only registration solves one problem and creates another: what happens when someone who should be there isn't on the list? A new hire at a member company, a board candidate, a colleague who was referred late — these people exist at every association, and a hard invite-only wall turns them into a support ticket instead of a registrant.

That's what Request Access is for. It's a toggle you add alongside the private-event setting, and it lets people who aren't on an invite list submit their information and ask to be let in. The coordinator reviews requests, approves or rejects each one, picks which invite list to add an approved person to, and Sunfish sends the invite email automatically. Nobody is emailing the coordinator asking to be added manually, and nobody outside the list gets straight through to a form meant to stay private. The full mechanics — including how approvals interact with group assignment below — are in our request access for invite-only events post.

Everyone sees the right price and the right questions

Here's where the list starts paying for itself beyond just gatekeeping. On an invite list, the coordinator assigns each contact a group — member, non-member, staff, board, whatever categories matter to the organization. That group travels with the contact. When the list is imported into an event, or when a Request Access approval adds someone to the list, that person's group determines their pricing tier and which registration questions they see automatically.

No separate discount codes to distribute, no manually checking a membership database mid-registration, no one accidentally landing on the wrong price because they used the wrong link. A board member sees board pricing and board-specific questions; a first-time non-member guest sees guest pricing and a shorter form. This single feature is arguably the biggest time-save for associations specifically, and it's a big reason associations gravitate toward this kind of event attendee management instead of a generic ticketing tool — our post on automated member vs. non-member pricing goes deeper on setup, and registration for associations in 2026 covers the broader case for associations moving off spreadsheet-driven registration.

Turn the list into a campaign

None of the above matters if people don't know the event exists or forget to finish registering. This is where Campaigns close the loop. You build a campaign against any of your contact lists — dynamic, manual, or both — and send whatever the moment calls for: an initial invite, a save-the-date, a reminder as the deadline approaches, a post-event survey, or a general update about the agenda.

A few details make this more useful than a generic mass-email tool bolted next to your registration form. You can send invite links and see conversions — who opened, who clicked, who registered — directly against the list you sent to. You can filter a send so it only reaches people who haven't registered yet, which turns "email everyone" into "email everyone who still needs to act." And like Contact Lists, you build these emails at the org level once and bring them into whichever event needs them, instead of rebuilding a template from scratch every time. That includes a standard abandoned-cart-style email that goes automatically to people who started registering but didn't finish — the single highest-leverage email most organizers forget to send. Our guides on event email marketing campaigns, abandoned-registration emails, and using registration data to drive campaigns each dig into a piece of this.

Back to the association: the coordinator now sends the flagship-conference invite to the full Invite and Promote list, a reminder two weeks later filtered to non-registrants only, an automatic nudge to anyone who starts the form and abandons it, and a post-event survey to everyone who checked in — all against lists that update themselves as people register, get approved through Request Access, or change groups. None of it required exporting a CSV.

Year two: where the reuse actually pays off

The real payoff of this system doesn't show up the first time you set it up — it shows up the second time. Fast-forward twelve months. The association is planning next year's flagship conference, and the coordinator's starting point looks completely different from where they were a year ago.

The org-level invite list from last year is still there, and it's not stale — members who joined or lapsed over the year already reflect their current group, because that list has been quietly maintained as an Attendee Updates list attached to ongoing membership data, not frozen at last year's export. The coordinator imports it into the new event in a few minutes instead of rebuilding a spreadsheet from three different sources. The email templates — invite, reminder, abandoned-registration nudge, post-event survey — are also sitting at the org level from last year, so instead of writing four emails from scratch, the coordinator opens last year's campaign, updates the dates and a couple of details, and sends.

The Request Access approvals from last year already updated people's groups, so the new hire who got approved as a "non-member guest" last spring is already sitting in the right segment with the right pricing this time, with no re-approval needed unless their status changed. And because private registration and login were already configured for this event type last year, turning them back on for the new event is a toggle, not a rebuild. What used to be a few days of list-building, template-writing, and pricing-logic double-checking before registration could even open is now closer to an afternoon. That's the difference between event registration software you configure once per event and one that compounds in your favor the longer you use it.

All five features at a glance

Frequently asked questions

Do I have to use all five features together?
No. They're built to work as a system, but each one stands on its own. You can use Contact Lists and Campaigns without ever turning on private registration, or run an invite-only event without touching Group Assignment. Turn on whichever pieces match how your events actually work, and add the rest later if your needs change.

What if I don't run invite-only events at all?
Contact Lists, Campaigns, and Group Assignment are all still useful for a fully open, public event. You can build a promotional list and run invite and reminder campaigns against it without restricting who can register, and Group Assignment still handles member versus non-member pricing even when anyone can access the form. Private/Invite-Only Registration and Request Access are the two features that specifically assume a gated event — skip them if that's not your situation.

Does setting up group assignment take a long time the first time?
It takes some upfront thought about which groups you actually need — most organizations land on somewhere between two and five — but it's a one-time setup per group, not per event. Once a contact's group is set on your list, it carries forward into every event you import that list into, which is exactly the point.

Key takeaways and next step

The five features work as one system, not five separate settings. Build the list once at the org level, decide whether the event should be open or invite-only, let Request Access catch the people you missed, let Group Assignment handle pricing and questions automatically, and run campaigns against the same list through every stage of the event lifecycle. That's the difference between event registration software that manages a form and one that manages the relationship with your audience.

If you're currently maintaining this by hand across a spreadsheet, a separate email tool, and a registration platform that doesn't know about either one, start with your next event's invite list — build it once, and see how much of the rest falls into place. Reach out to the Sunfish team if you want a walkthrough of how this maps to your specific event calendar.