Salesforce event registration: the complete guide

Setting up event registration in Salesforce requires a native app since Salesforce doesn’t include a built-in registration form. With Blackthorn Events, you can manage the full workflow of your event inside Salesforce – from the event landing page and registration form to ticketing, payments, follow-up emails, and event data – all in one place. Follow these steps:

1. Create your event page and registration form — choose ticket types, session options, and custom fields.
2. Publish the page on your website or to Salesforce Experience Cloud.
3. Collect registrations — each submission creates an Attendee record in Salesforce, matched to an existing Contact/Person Account or a new one created automatically.
4. Process payment through Blackthorn Payments, recorded directly on the Contact/Person Account record.
5. Send a confirmation email that pulls from the registrant’s record.
6. Update Campaign Member status from “Invited” to “Registered” in real time — no import, no sync.

Here’s everything you need to know to get there.

Getting event registration right isn’t just an operational detail — it’s foundational to your event’s success. Registration is typically an attendee’s first direct interaction with your organization, which means a clunky or error-prone process can damage their perception before the event even begins.

Done well, registration secures your attendee base, establishes a reliable revenue stream, and sets a positive tone that carries through the entire event experience. Done poorly, it creates friction that drives potential attendees away entirely.

Beyond first impressions, registration data powers everything downstream: attendance forecasting, personalized communication, on-site check-in, and post-event follow-up. That’s why the system you use to manage registration matters as much as the process itself — and why teams that run events in Salesforce have a significant advantage.

The registration challenge: why event data creates problems for Salesforce-centric teams

If your organization runs on Salesforce, you already understand the value of having everything in one place. Contacts, accounts, donations, pipeline — it’s all there. Then an event comes along, and suddenly you’re managing a separate system.

Registration data lives in your event platform. Attendee records have to be exported and imported into Salesforce. Payment data sits in a third tool. And if the sync between them breaks — which it does — someone on your team spends the next morning reconciling spreadsheets instead of following up with registrants.

This isn’t a minor inconvenience. Every registration that syncs late is a follow-up that goes out too slow. Every duplicate contact is a conversation that starts with the wrong context. And when leadership asks for an event ROI report, you’re building it by hand.

The fundamental problem: most event registration tools were designed for events, not for Salesforce. When you stitch two separate systems together, the seams show up exactly when you can’t afford them to.

Curious how to tackle this challenge: Download our guide on ‘The Hidden Cost of Disconnected Event Data.’

3 options for how to handle event registration with Salesforce

There are three ways Salesforce teams typically handle event registration. Here’s what each one actually involves.

1. Salesforce Campaigns (manual)

Salesforce Campaigns weren’t designed for event registration — they were designed for marketing attribution. You can create a Campaign, set up Campaign Member statuses like “Registered” and “Attended,” and manually add contacts. For a small internal meeting with 20 people you already know, this works fine.

For anything involving a public registration form, ticket sales, or more than a handful of attendees, it falls apart. There’s no registration form connected to Campaigns out of the box. No payment processing. No confirmation emails. No waitlist management. You’d be building each of those pieces yourself, or asking attendees to register somewhere else and then manually updating Salesforce afterward.

2. Third-party platform + sync

This is the most common approach — and also the one that generates the most support tickets. You pick an event registration platform (Eventbrite, Cvent, or similar), configure it for your event, and connect it to Salesforce via Zapier, a native connector, or a custom API build.

In theory, registrations flow automatically from the event platform into Salesforce. But, most teams find it’s rarely automatic, and they’re left struggling to sync data. The sync adds complexity without adding capability. Every hour your team spends maintaining it is an hour not spent on the actual event.

Challenges it creates?

• Syncs run on a delay — often hours later or overnight — so your Salesforce data is always behind.
• Field mappings break when either platform updates.
• Duplicate records accumulate because the matching logic between two separate systems is never perfect.
• You can’t run Salesforce reports on event data in real time because the data lives outside of Salesforce.
• When something breaks, you’re troubleshooting between two vendors who each point the finger at the other.

Sounds familiar? There’s a better way. You need a Salesforce-native app.

3. Salesforce-native app (Blackthorn Events)

A Salesforce-native app is an app or piece of software that lives inside the Salesforce platform — not connected to it, but actually built on it. There’s no separate system to sync data with because there’s only one system of record.

When someone registers through Blackthorn Events, the registration record is created in Salesforce the moment they submit the form. The contact is matched against your existing records or created fresh. Payment is processed through Blackthorn Payments and recorded directly on the contact. A confirmation email goes out through Salesforce. Campaign Member status updates in real time.

Nothing moves between systems because everything is already in the same place.

What you’ll need: build vs. buy

If you’re a Salesforce admin evaluating your options, here’s a practical checklist to help you decide whether to build something custom or buy a purpose-built app.

3 reasons to build, if:

1. Your registration needs are very simple (free events, internal-only, no payments)
2. You have a Salesforce developer with available cycles and ongoing capacity for maintenance
3. Your event volume is low and unlikely to grow

5 reasons to buy (Blackthorn Events), if:

1. You run paid events or need payment processing connected to Salesforce
2. You need real-time data — not synced data — for follow-up and reporting
3. You want session selection, waitlisting, or group registration without building it from scratch
4. Your team needs to manage events without relying on a developer for every change
5. You’re already using Salesforce for CRM and want events to live in the same data model

Evaluation Sheet to Decide if You Should Build or Buy

Feature	Build (Custom)	Buy (Blackthorn Events)
Registration forms	Manual build required (Salesforce developer needed)	Built-in, configurable without code
Payment processing	Custom integration required	Native via Blackthorn Payments
Attendee records in Salesforce	Requires custom data model and logic that counts toward your org’s object limits.	Auto-created on every registration, matched to existing Contacts
Real-time data sync	Possible, but complex to implement & hammers APIs	All data lives in Salesforce natively — no sync needed
Waitlisting, sessions & group reg	Must be built from scratch	Included out of the box
No-code admin management	Developer required for most changes	Admins can manage events without a developer
Ongoing maintenance	Requires additional dev capacity	Managed by Blackthorn
Time to launch	Months to years, subject to shifting internal priorities	Blackthorn customer success team can get you  live in a matter of weeks.

How to set up event registration with a Salesforce native app 

Here’s what a complete Salesforce event registration looks like, using a native setup.

Step 1: Registration form

Your event’s registration page is powered by Blackthorn Events and can be hosted on your own site or on a Salesforce Experience Cloud page. It captures the fields you need — name, email, company, custom fields specific to your event — along with ticket type selection and session choices. The form is configured inside Salesforce, so anytime someone completed the form, all responses will be saved directly in your database. 

Step 2: Payment processing

For paid events, attendees enter payment information directly on the registration form. Blackthorn Payments handles the transaction — credit card, ACH, or other payment methods depending on your setup. The payment record is created in Salesforce immediately and tied to the registrant’s contact and attendee record.

Step 3: Confirmation

The moment registration is complete, a confirmation email goes out. Because it’s a Salesforce email, it can pull in any data from the registrant’s record — the specific event and session they signed up for, the date, time, location, and the calendar invite — without a third-party email tool.

Step 4: Attendee record creation

The registration creates an Attendee record in Salesforce, linked to the contact. If the contact already exists in your org, the registration is tied to that record. If they’re new, a Contact record is created automatically. Either way, you have a complete, current picture of who registered and when.

Step 5: Campaign Member status update

If you’re tracking the event as a Salesforce Campaign — which most teams do for attribution — the Campaign Member status updates automatically: from “Invited” to “Registered” at signup, and later to “Attended” after check-in. No manual updates, no imports. Just clean, current data.

Advanced registration features

Once the core workflow is running, you have access to the following Blackthorn events features: 

Waitlisting. When an event or ticket type hits capacity, Blackthorn Events moves registrants to a waitlist and notifies them when a spot opens. Waitlist status is tracked in Salesforce like any other registration status — so you can report on demand, capacity, and conversion from waitlist to confirmed.

Session selection. For multi-track events, attendees can choose specific sessions during registration. Capacity, waitlisting, and check-in all work at the session level.

Promo codes. Discount codes can be configured as a percentage, a fixed amount, or a full waiver, with optional expiration dates and usage limits. Code usage is tracked in Salesforce, so you can see exactly which codes drove registrations and at what discount.

Group registration. One person can register multiple attendees in a single transaction — useful for team events, family memberships, or table purchases at galas. Each attendee gets their own Salesforce record, and the group relationship is tracked.

Custom fields. Capture anything you want to store in Salesforce: dietary restrictions, company size, how people heard about the event, T-shirt size, etc. Custom fields land directly on the registration record.

Registration page design: what actually drives conversions

Registration isn’t just a data collection step. It’s often the first real interaction a potential attendee has with your event brand, and a friction-heavy process will cost you sign-ups.  

Common issues include forms that ask for too much upfront, unclear confirmation flows, and mobile experiences that don’t function properly.

A well-designed registration page sets expectations — what the event covers, who it’s for, what’s included — and delivers immediate confirmation so attendees know their spot is secured. When those basics are handled well, no-show rates drop, and your team fields fewer “did my registration go through?” emails in the days before the event.

A good registration page should include the following essential elements: 

• Event name
• Event location
• Event start time and date
• Event end time and date
• Event ticket cost 
• What guests need to bring with them
• Event registration form
• Social media links (Facebook, Twitter, Instagram, etc.)
• Any other important details guests should know. 

4 landing page best practices to increase registrations:  

Your landing page is often the first thing potential attendees see — and first impressions matter. A well-built page keeps people moving forward instead of clicking away. Here are four elements that reduce drop-off and make the sign-up experience feel straightforward from start to finish.

1. Keep it short. 

Every additional field reduces completion rates. Capture what you need for the event and the follow-up — not everything you’d ever want to know. You can always collect more later.

2. Match the visual design to your event. 

A generic-looking form signals a generic event. If you’re using a Salesforce Experience Cloud page, you have full control over design. Make it look like it belongs to your brand.

3. Be specific about what’s included. 

Ticket descriptions, session overviews, and speaker information on the registration page reduce questions to your team and improve completion rates. People register more confidently when they know exactly what they’re signing up for.

4. Make confirmation immediate and specific. 

A confirmation page and email that spell out date, time, location, and what to expect reduce no-shows and post-registration support volume.

What to include on your event registration form

The questions you ask on your registration form shape both the attendee experience and the data you have for follow-up. Keep the form short — every extra field reduces completion rates — and focus on what you genuinely need to run the event and personalize follow-up. 

At minimum, capture name, contact details, and any logistical requirements like dietary restrictions, accessibility needs, or accommodation requests. For B2B events, adding a job function or company size field helps you understand your audience and tailor the session experience.

Use a “How did you hear about us?” question to evaluate which marketing channels are driving registrations. If you’re running a multi-session or multi-track event, include session selection on the form so attendees arrive knowing exactly where to go — and your team can plan room capacity in advance.

Check out our list of common questions to include on your registration form. 

How to track event registration performance inside Salesforce with Blackthorn

One of the clearest advantages of running registration natively is that you don’t need a separate analytics tool to understand how your events are performing.

Registration reports. Every registration is a Salesforce record, so you can build reports on volume, ticket type breakdown, promo code usage, and registrations over time using standard Salesforce reporting. No exports, no BI tool, no waiting on someone from data.

Attendee analytics. Cross-reference event attendance with any other Salesforce data. Which contacts attended two or more events in the past year? Which accounts have the highest event engagement? Which attendees moved into a sales opportunity within 90 days? These questions take minutes to answer when your event data actually lives in Salesforce.

Campaign attribution. Campaign Member data connects attendance to pipeline. If a contact attended your user conference and then entered an opportunity the following quarter, that connection exists in Salesforce and surfaces in attribution reports.

How to manage event check-in with Blackthorn 

When you use Blackthorn Events, the entire event process is easier and happens in one place. Every check-in is a Salesforce action. When a staff member scans an attendee’s QR code using the mobile check-in app, the attendee record updates instantly — no manual entry, no export later, no reconciling spreadsheets the next morning. 

The attendee’s status moves from “Registered” to “Attended” in real time, and every other Salesforce automation tied to that status fires immediately.

Here are the steps in our event check-in flow:

1. A personalized QR code is generated for each registrant and included in their confirmation email.
2. On event day, staff open the Blackthorn Events mobile app on any iOS or Android device.
3. The attendee presents their QR code (from email, phone, or printed ticket). Staff scan it in seconds.
4. The attendee record in Salesforce updates instantly — no import, no sync delay.
5. Any Salesforce automations triggered by attendance status fire in real time — follow-up emails, VIP alerts, internal notifications.

Blackthorn Check-in Methods: QR codes, manual search, and walk-ins

The mobile check-in app supports three approaches, so your staff can handle any situation on the day:

1. QR code scan. The fastest method. Each registrant receives a unique QR code in their confirmation email. Staff scan it with a phone or tablet and the check-in is complete in under a second. Works for group registrations too — one scan checks in the entire group. 

Manual search and swipe. If an attendee forgot their QR code, staff can search by name and swipe to check in. Keeps the line moving without turning anyone away.

2. Walk-in registration. Not everyone pre-registers. Staff can add a new attendee on the spot directly from the app, creating a Salesforce Contact and Attendee record in real time.
3. External ID scanning. For recurring groups — students, members, clients — you can assign a permanent QR code tied to a Contact record. They use the same code for every event without pre-registering each time.

Offline mode: check-in even when Wi-Fi fails

Venue Wi-Fi is notoriously unreliable — especially at large conferences where hundreds of people are connecting simultaneously. The Blackthorn Events mobile check-in app works offline. Check-ins are stored on the device and sync back to Salesforce the moment connectivity is restored.

This means the line never stops moving, your data is never lost, and attendees experience zero disruption — even if the hotel network goes down during peak arrival time.

Best practices for a smooth event check-in and arrival process

Check-in software is only part of the equation. The operational setup matters just as much. Consider adding these steps to your event check-in process. 

1. Train staff on the app before the event, not on the day. Run at least one practice check-in so everyone knows how to search, scan, and handle edge cases like walk-ins or unrecognized QR codes.

2. Plan your check-in area layout. Think about table placement, queue management, and how many scanning stations you’ll need based on expected arrival volume and timing.

3. Send QR codes in confirmation emails well in advance. Give attendees time to save their code, print it, or add it to a mobile wallet.

4. Test connectivity at the venue. Confirm the app is loaded with current registrant data before doors open. If Wi-Fi is unreliable, make sure staff know the app works offline.

5. Have a backup plan for walk-ins and issues. A designated problem-solving station with a staff member who knows the app thoroughly keeps the main check-in line flowing.

What check-in data unlocks in Salesforce

Because Blackthorn keeps all your check-in data directly inside Salesforce rather than a third-party tool, attendance becomes a first-class data point you can act on immediately and report on indefinitely. 

Here’s how you can use the data: 

• Real-time follow-up. A flow triggered by the “Attended” status can send a personalized post-event email the moment someone walks in the door.
• VIP alerts. Configure instant notifications via Slack, email, or SMS when a key contact checks in, so the right person on your team can greet them immediately.
• Session-level tracking. For multi-track events, staff can scan attendees into individual breakout sessions, giving you granular engagement data for each session, not just the event as a whole.
• Campaign attribution. Attendance status feeds directly into Salesforce Campaign Member data, connecting the event to pipeline and revenue reporting.
• No-show identification. Know exactly who registered but didn’t attend, and trigger a different follow-up sequence for them automatically.

Ready to see how Salesforce event management can streamline your team’s data? Book a meeting with a Blackthorn expert today. 

FAQs about event registration with Salesforce

Does Salesforce have built-in event management?

How do I create a registration form in Salesforce?

What is the best event registration app for Salesforce?

Can you do event registration in Salesforce?