Every nonprofit event needs more than a name and an email address. You need to know who wants a vegetarian meal, who requires accessibility accommodations, what size shirt to order, or which workshop track someone plans to attend. The usual result is a registration form that asks everyone every question, whether it applies to them or not, followed by a spreadsheet someone manually reconciles against your CRM afterward.
Salesforce custom fields in the Soapbox Engage Events app let you add nonprofit-specific questions directly to your registration form, tied to real Salesforce fields, and shown only to the registrants they actually apply to. The data lands in Salesforce the moment someone registers, with no separate import step.
This guide covers how the feature works for registrants, how to set it up, and best practices for building better event forms, whether or not you're using Soapbox Engage.
In This Guide
Why Event Registration Data Quality Matters
The information you collect at registration can make a big difference in how smoothly your event runs. Catering counts depend on accurate dietary data. Accessibility accommodations need to be known well before event day, not discovered at check-in. Program teams often need to know which session or track a registrant chose so they can plan staffing and materials. When that information lives only in a spreadsheet or a PDF export, someone on your team has to manually reconcile it against donor and constituent records, and mistakes creep in every time it's re-typed.
The other cost is registrant experience. A form that asks every question to every person, regardless of relevance, feels long and impersonal, and long forms are where registrants abandon. A parent registering for a walk shouldn't have to skip past workshop-selection questions meant for a conference attendee. Matching form length and content to what's actually relevant to that registrant keeps the process fast without sacrificing the data your team needs.
This is closely related to a challenge we've written about before: events with multiple sessions, tracks, or ticket types create very different data needs for different registrants. If your event has that structure, our guide on simplifying registration for multi-session nonprofit events covers the ticketing side of that same problem.
How Salesforce Custom Fields Work on the Registration Form
Soapbox Engage lets you add fields to a registration form that map directly to Salesforce, and control exactly when each one appears. Here's what that looks like from the registrant's side:
Registrants see questions specific to your event
Beyond standard name, email, and attendee details, the form can ask about dietary preferences, accessibility needs, t-shirt sizes, program interests, or any other question specific to your event. Each of these ties directly to a Salesforce field, so your team never has to manage that data separately after registration closes.
Follow-up questions appear only when relevant
Custom fields can be made conditional. If a registrant says they want a t-shirt, additional fields asking for size or color appear right away. If they don't select that option, those follow-up questions stay hidden entirely, keeping the form shorter for everyone who doesn't need them.
Fields can be scoped to specific ticket types
A question that matters for a VIP ticket, a volunteer registration, or a workshop attendee doesn't have to appear for every other registrant. Custom fields can be restricted to the ticket types they're actually relevant to.
The same approach works for contact-level questions
Custom fields aren't limited to attendee details. The same functionality is available in the Contact Information section, where you can collect information once for the person completing the registration rather than separately for each attendee. There, custom fields pull from Salesforce Lead and Opportunity data instead of the attendee record.
Why this approach works: Registrants only see questions that actually apply to them, so the form stays short and relevant, while your team still gets every piece of nonprofit-specific data it needs, already mapped to the right Salesforce field.
Watch: Feature Focus Demo
This short walkthrough from our team shows the registration form experience and the full Administrator setup for adding and configuring Salesforce custom fields.
Soapbox Engage Feature Focus: Salesforce Custom Fields
How to Set Up Salesforce Custom Fields
Adding a custom field takes place inside the event you're configuring in the Soapbox Engage Administrator.
Step 1: Open the Attendee Info tab
Open the event you want to configure, select the Attendee Info tab, and scroll down to Custom Salesforce Fields.
Step 2: Add and configure the field
Click Add Salesforce Element and choose the Salesforce field you want to use. From there, you can:
- Customize the label the registrant sees
- Choose whether the field is required
- Add a default value or a tooltip
- Control whether the field is displayed or hidden
- Choose which ticket type or types should include the field
Step 3: Add conditional logic if needed
If you want a field to appear only when another response meets certain criteria, such as showing size and color options only when a registrant opts into a t-shirt, add conditional logic to control when it displays.
| Field Location | Salesforce Data Source |
|---|---|
| Attendee Info section | Custom Salesforce fields, per attendee |
| Contact Information section | Salesforce Lead and Opportunity fields, per registrant |
The same concept applies in the Contact Information section, giving you the choice to collect information once for the person completing the registration, or separately for every attendee they're registering. Fields there pull from Salesforce Lead and Opportunity data rather than the attendee record.
Custom Salesforce fields are built into Soapbox Engage Events and sync registration data to Salesforce in real time, so your event records stay current without manual entry.
Best Practices for Event Registration Forms
Whether or not you're using Soapbox Engage, these principles apply broadly to building registration forms that collect the right data without frustrating registrants.
Only ask what you'll actually use
Every question on a registration form should map to a real operational need, catering, staffing, seating, or follow-up communication. Questions that exist "just in case" add length without adding value, and registrants notice.
Show questions only to the registrants they apply to
Use conditional logic and ticket-type targeting so a volunteer doesn't see sponsor-only questions and a general attendee doesn't see workshop-selection fields meant for a conference track. A shorter, more relevant form is easier for registrants to navigate than a long, generic one.
Map fields to your CRM before you build the form
Decide where each answer needs to live in your CRM before you start adding questions. Building the mapping first prevents a form that collects clean data with nowhere accurate to put it.
Separate person-level questions from attendee-level questions
Some information belongs to the person registering, like billing contact details, while other information belongs to each individual attendee, like meal choice or session selection. Keeping that distinction clear in your form design prevents duplicate or misapplied answers when one person registers a group.
Review your fields after every event
Treat your registration questions as something to refine, not something to set once. After each event, check which fields staff actually used on event day and which ones went unused, and adjust your next form accordingly.
If your event includes multiple sessions, tracks, or ticket tiers, pairing custom fields with well-structured ticket types makes an even bigger difference; see our guide on simplifying registration for multi-session nonprofit events. And if you're also using Live Displays or digital check-in on event day, our post on digital wallet tickets and check-in covers how registration data carries through to arrival.
Custom Salesforce fields won't make your event run itself, but they remove one of the more tedious parts of planning: chasing down accurate attendee details after the fact. Ask the right questions of the right people, and the data your team needs is already where it belongs before the event even starts.
Collect Better Data With Soapbox Engage Events
See how custom Salesforce fields work on your own registration forms.
Start a Trial See a Demo
Donations
Events
Petitions
Forms
Shop
Directories