Integrations · Salesforce

Salesforce event management.Attendee data synced to your CRM.

Salesforce event management with AirLST means Salesforce stays your system of record for contacts and campaigns, while AirLST runs the event: invitations, registration, guest list and check-in. The Salesforce connector turns campaign members into guests and writes invitation, RSVP, attendance and no-show back to Salesforce, so sales sees who came without waiting for a spreadsheet.

Book a demo All integrations

Connector · SalesforceCustomer Summit 2026CampaignLog

Guest	Account	AirLST	Salesforce
Anna Brooks	Northlight Events Inc.	Confirmed	Responded
Tom Lee	Skyline Conventions	Checked in	Attended
Ethan Brown	Harbor Live	Invited	Sent
Sofia Romano	Alpine Meetings	Declined	Declined

9:42 AMCheck-in Tom Lee · status “Attended” sent to Salesforce · connector
9:15 AMSalesforce 18 campaign members added · created as guests · connector

Salesforce stays in chargeContacts and campaigns live in your org.

Status goes backRSVP, check-in and no-show on the campaign member.

Mapped per fieldYou decide what syncs, and in which direction.

Trusted by leading event teams and enterprises

Your event results belong in Salesforce. Not in a CSV someone imports next week.

01Campaign in

Contacts and campaign members from Salesforce become the guest list, with no export in between.

02Status back

Invitation, RSVP, check-in and no-show return to the campaign member as status.

03One record

Your event team, the check-in app and Salesforce see the same guest, not three copies of a spreadsheet.

04Set up with you

Field mapping, testing and go-live with our Integration Services and your Salesforce admin.

01Contacts in

From Salesforce campaign to guest list, without a spreadsheet.

Your sales and marketing teams already build the invite list in Salesforce. The connector picks up the campaign members and creates them as guests in AirLST, with name, account, owner and the guest group you assign. The email invitation then goes out from AirLST in your design.

Contacts and campaign membersBecome guests in AirLST; the guest group follows a Salesforce field such as the campaign member status.
Field mapping per eventWhich Salesforce field fills which guest field, and which direction it syncs.
No second importThe guest list follows the campaign, so nobody re-imports a spreadsheet that has gone stale.
Objects and custom fields

Connector · SalesforceCustomer Summit 2026Field mappingSync

AirLST

Salesforce

First name

Contact.FirstName

Last name

Contact.LastName

Company

Account.Name

Host

Contact.Owner

Guest group

CampaignMember.Status → VIP, Customer

Campaign Customer Summit 2026: 186 members created as guests.

Sample mapping, illustrative: fields are defined per project

02Results back

Who registered, who came, who didn’t: visible in Salesforce.

Every step a guest takes in AirLST becomes a status on the Salesforce campaign member: invitation sent, registered, declined, checked in at the door, no-show. Account owners see it on the contact, and your campaign reports show event attendance next to pipeline, without anyone rebuilding the list after the event.

Sync logCustomer Summit 2026 · AirLST → SalesforceStatusErrors 0

Event in AirLST	Guest	Campaign member status	Time
Invitation sent	Chloe Vance	Sent	Sep 14, 10:02 AM
Registration confirmed	Chloe Vance	Responded	Sep 16, 3:47 PM
Declined	Sofia Romano	Declined	Sep 18, 9:20 AM
Checked in at the door	Chloe Vance	Attended	Oct 2, 9:41 AM
No-show after the event	David Shaw	No-show	Oct 2, 8:00 PM

Sample data, illustrativeStatus values:

Check-in at the door becomes “Attended” in Salesforce

No-shows are visible to sales, ready for follow-up

For sales

Account owners see on the contact whether their customer registered and showed up, and can follow up.

For marketing

Campaign reports show invited, registered and attended per event, next to the pipeline that campaign touches.

For the event team

The guest list, capacity, badges and check-in stay in AirLST, built for running the event itself.

The connector is a user. It has rights, and it has a log.

The Salesforce connector works through the roles and rights of the guest list, like any user, and every change it makes is recorded in the change log. Guest and event data stays with AirLST in Germany; what is stored in Salesforce is governed by your Salesforce contract, and you decide per field what crosses over.

Hosted in GermanyGuest and event data on servers in Germany.
GDPR compliantData processing in line with the GDPR, details in the Trust Center; authentication of the Salesforce connection:
TISAX assessedThe information security assessment standard of the automotive industry, passed by AirLST.

PermissionConnectorEvent manager

Create guests from campaign

Write status to Salesforce–

Send invitations–

Export guest list–

Example. You assign rights per connection; the connector can only do what its role allows.

Part of AirLST

Salesforce knows the customer. AirLST knows the event.

The connector links the two at the guest record: the same guest your team invites, the check-in app scans and reporting counts is the campaign member in Salesforce.

What should Salesforce own, and what the event software?

Salesforce event management works best when each system does its own job. Salesforce owns the customer: contacts, accounts, owners, campaigns and the pipeline. The event software owns the event: email invitations, registration forms, the guest list with capacity and waitlist, seating chart, name badges and check-in at the door. The connector keeps both in step at the guest record, so contacts come from Salesforce and results go back.

Without that link, the invite list leaves Salesforce as a spreadsheet, gets edited by the event team and an agency, and comes back weeks later as an import, if it comes back at all. Sales never sees who attended, and marketing can’t tie the event to the pipeline. With the AirLST Salesforce connector, the status on the campaign member is updated by the event itself.

Salesforce knows who the customer is. The event software knows whether they showed up. The connector makes sure both know.

InContacts and campaign members as guests

BackInvitation, RSVP, attendance and no-show as status

RESTAPI Access for everything else, from Professional

How does the setup work?

Agree on the roles. Salesforce is the system of record for contacts, AirLST for the event. Decide which campaign feeds which event.
Map the fields. Which Salesforce fields fill the guest record, which guest group follows which value, and which statuses go back.
Connect the org. Your Salesforce admin and our Integration Services connect AirLST to your org with the rights the connector needs.
Test with a sandbox event. Add test contacts to a campaign, register, check in, and read the result on the campaign member:
Go live. The connector runs for every event that uses the campaign; changes are logged and can be traced.

Connector or REST API?

The Salesforce connector covers the standard flow: campaign in, status back. When you need more, such as registrations from your own website, data for a BI tool, or a link to SAP or Microsoft Dynamics next to Salesforce, the AirLST REST API and other integrations take over. Both write to the same guest record, so Salesforce, the website and the check-in app never disagree.

Event CRM: attendee history across events, next to Salesforce
Integration Services: field mapping, testing, go-live
Trust Center: hosting, encryption, data processing
Event management software: many events, one standard, connected to your IT

FAQ

Salesforce event management: frequently asked questions

Does Salesforce have event management?

Salesforce is a CRM. It tracks who you invite and how they respond through campaigns and campaign members, and its “Event” object is a calendar activity, not an event. The work of running an event itself (registration pages, guest list, capacity, badges, check-in at the door) usually lives in dedicated event management software that is connected to Salesforce. With AirLST, that connection is the Salesforce connector.

How do I track event registrations and attendance in Salesforce?

Use a campaign per event and let the event software maintain the campaign member status. With AirLST, campaign members become guests, and invitation, RSVP, check-in and no-show are written back to Salesforce as status. Your reports and dashboards in Salesforce then show who registered and who actually came, without a CSV import after the event. Which statuses and fields are used is defined per project: .

Is Salesforce Event Monitoring the same as event management?

No. Event Monitoring in Salesforce is about technical events inside your Salesforce org, such as logins, API calls and report exports, for security and usage analysis. It has nothing to do with planning conferences, product launches or customer events. If you are looking for software to manage in-person or hybrid events alongside Salesforce, that is what this page is about.

Which AirLST plan includes the Salesforce integration?

API Access (REST) is included from the Professional plan. Custom integrations with Salesforce, SAP or Microsoft 365 are delivered as part of the Enterprise implementation, with our Integration Services handling field mapping, testing and go-live. Plan details are on the pricing page.

Is AirLST listed on the Salesforce AppExchange?

The Salesforce connector is provided by AirLST and set up together with your Salesforce admin and our Integration Services. Listing and installation details: . Until that is confirmed, ask us about the setup for your org.

Where is attendee data stored when it syncs with Salesforce?

Guest and event data in AirLST is hosted in Germany and processed in line with the GDPR; AirLST is also TISAX-assessed, the information security assessment standard of the automotive industry. What lands in Salesforce is stored according to your Salesforce contract. You decide per field which data travels in which direction, so the sync carries only what your teams need.