Salesforce for events and webinars: registration to follow-up

Salesforce can run your events and webinars when each event is a campaign and every invitee is a campaign member. Member status then moves from invited to registered to attended or no-show. Registration forms, badge scans and webinar platforms write those statuses back. Flow or Engagement Studio then routes engaged attendees to sales and nurtures everyone else. Costs on the campaign record let you report return per event.

Why do event lists end up outside Salesforce?

Because registration, scanning and webinar tools each keep their own list, and nobody owns bringing them back. Spreadsheets fill the gap, and the record of who showed up never reaches the rep.

Marketing ops teams describe the same pattern after most shows and webinars:

• Registrants sit in the webinar tool, and only a CSV export reaches Salesforce, often days later.
• Booth scans land in a scanner app or on paper, with minimal detail about what the visitor wanted.
• Sales cannot see which of their accounts attended, so follow-up depends on marketing emailing a list.
• Spend is tracked in finance, so nobody can compare one show against another on cost per outcome.
• No-shows get the same generic follow-up as attendees, or nothing at all.

The fix is mostly design and discipline, not new software. Salesforce already has the objects you need.

How should events map to Salesforce campaigns?

Create one parent campaign per event and child campaigns for anything you want to measure separately. Then give each event type its own set of member statuses.

A trade show might have a parent campaign with children for the booth, a sponsored dinner and a speaking slot. A multi-session virtual summit might use one child per session. Hierarchy rollup fields then total members, responses and costs at the parent.

Keep the structure shallow. Two levels cover most event programs, and a third is usually a sign you are modeling tactics rather than events.

Use the campaign Type field consistently, with values such as Webinar, Trade Show, Field Event and Customer Event. Reports then group events by format without relying on naming.

Which member statuses should each event type use?

Define a status list per event type, decide which statuses count as responded, and apply it automatically when a campaign is created. Consistent statuses make every event comparable.

Every campaign starts with Sent and Responded. You can rename these and add your own values, mark one as the default, and flag which ones count as responses. Salesforce then tallies responders on the campaign.

A typical webinar list is Invited, Registered, Attended, Attended On-Demand and No-Show. A trade show list might be Pre-Booked Meeting, Visited Booth, Scanned and Met With Sales. Only statuses showing real engagement should be flagged as responded.

Statuses are set per campaign, not globally. Many teams use a record-triggered flow on campaign creation that adds the right statuses for the campaign type, so nobody sets them by hand.

When does an event need its own custom object?

Rarely in phase one. Add a custom event object only when you must track things a campaign member cannot hold cleanly, such as sessions, tickets, payments or room bookings.

Signs you have outgrown campaigns alone include paid ticketing, attendees picking multiple sessions inside one event, or speakers and sponsors needing their own records. Logistics like venues and catering budgets also point that way.

Even then, keep the campaign. The custom object should link to it, so attribution and campaign influence keep working. Event management apps on AgentExchange (formerly AppExchange) follow a similar pattern, and are worth comparing before you build.

How do registrations get into Salesforce?

Through a form that creates or updates the person and adds them to the event campaign with a Registered status. The form tool matters less than getting that campaign membership right.

• Account Engagement forms and form handlers can add prospects to a campaign and set status through completion actions.
• An Experience Cloud site suits customer or partner events where attendees already have a login.
• Webinar platform integrations register people on the platform and sync them to the campaign, often through a connector or AgentExchange package.
• Native Web-to-Lead works for simple cases but needs automation to attach the campaign and status.

Whichever path you choose, check for duplicates before creating records. Registrants are often existing contacts, and a new lead for each signup splits their history. Our web-to-lead guide covers form mechanics, spam controls and source fields in depth.

How do we capture trade-show leads at the booth?

Scan or capture visitors straight into the event campaign, with a short qualifying note, instead of collecting lists to import later. Speed matters because the conversation is freshest that evening.

Common options are the organizer's badge-scan export, a scanning app integrated with Salesforce, or a booth QR code that opens a short landing page. Whatever you use, capture a few qualifying fields: product interest, timeline and whether a meeting was requested.

An aircraft-engine maintenance firm we worked with had been entering leads from 14 trade shows manually. On Sales Cloud and Account Engagement, the project added QR-code landing pages and forms so booth leads were captured and routed at once. Parent and child campaigns tracked return for each show.

What attendance data should come back from webinar platforms?

At minimum, whether each registrant attended live, watched the recording, or did not show. Engagement detail is worth syncing if sales or scoring will actually use it.

Useful fields include minutes attended, questions asked, poll answers and whether the person requested a follow-up. Store numeric data such as duration in custom campaign member fields, so reports can filter on it.

Questions asked live are high-intent signals. Put the question text on the campaign member, or create a task with it, so reps can open the follow-up with something specific.

Decide when the sync runs. Some integrations update during the event, while others send attendance after it ends. Plan follow-up timing around whichever your platform supports, and test it on an internal webinar first.

Who follows up with attendees, and how fast?

Route attendees who meet your hot criteria to sales with an agreed follow-up window. Send everyone else into a nurture matched to what they did, including a separate path for no-shows.

Hot criteria might be a meeting request, a booth demo, a question on pricing or a strong fit score. A record-triggered flow on campaign member status can assign the lead and create a task with the event context. Our lead routing guide covers assignment logic and SLA timers.

For everyone else, Engagement Studio in Account Engagement can branch on member status. Attendees might get slides and a related case study, while no-shows get the recording. Without Account Engagement, Flow can still create rep tasks and queue simple follow-up.

Give reps one place to see event activity. A related list or report on the account showing recent event attendance helps them call with context.

What does the full event lifecycle look like in Salesforce?

How do we record event costs and measure return?

Put spend on the campaign record and pipeline will meet cost in the same report. The standard fields are there; the work is keeping them current.

Campaigns include Budgeted Cost, Actual Cost, Expected Revenue and Expected Response fields. Enter the budget before the event and the actual cost once invoices arrive. Use child campaigns if you want cost split by booth, sponsorship and hospitality.

Return on an event needs more than cost. It also needs opportunities connected to the people who attended, which depends on contact roles and an influence model. Our campaign attribution guide covers that side in detail.

A building-products manufacturer we supported had trade-show leads captured with minimal detail and no cost-per-lead view. Connecting Account Engagement to their Sales Cloud and Service Cloud org gave them campaign tracking, plus ROI reporting that covered trade shows.

Can staff check people in on a phone?

Yes, with a simple setup. The campaign's member list in the Salesforce mobile app, plus a quick action that sets status to Attended, covers small events.

For larger events, a scanning app or a check-in page built on Experience Cloud or a screen flow handles walk-ins and queues better. Test signal at the venue in advance, and confirm whether your chosen tool works offline.

Keep walk-in registration short. Name, email and company are enough to create the record; enrichment and duplicate checks can run afterwards.

What consent rules apply to event lists?

Treat event data as personal data under whatever privacy rules apply to you. Record what each person agreed to, and do not assume attendance means consent to marketing.

Purchased or organizer-supplied attendee lists deserve particular care, because the consent was collected by someone else. Capture consent on your own registration forms, store it in Salesforce consent fields or objects, and honor opt-outs in every follow-up. This is general guidance, not legal advice; confirm requirements with your counsel. Our data privacy guide covers consent storage.

Does Salesforce sell a dedicated events product?

Historically, most teams combined Campaigns with Account Engagement or Marketing Cloud and an AgentExchange events app. Salesforce has announced an Event Management capability, so check its scope and availability before buying elsewhere.

Salesforce's Marketing Cloud release page describes Event Management as part of Loyalty Management, so confirm scope, timing and licensing with your account team. Packaging, licensing and B2B event fit were not clear at the time of writing. Ask your Salesforce account team what is included before you build plans on it.

What should phase one of an events project include?

Standardize the campaign model, wire up one registration path and one attendance sync, and automate follow-up for attendees and no-shows. Leave custom objects and advanced scoring until the basics run cleanly.

• Agree event campaign types, the parent and child structure, and a naming pattern.
• Define member statuses per event type and automate them on campaign creation.
• Connect the main registration form and the webinar platform to campaign membership.
• Choose one trade-show capture method and test it before the next show.
• Build attendee routing with tasks for reps, plus a no-show nurture.
• Require actual cost on every event campaign and publish an events dashboard.