Attendees are synced as leads. We associate them with the event campaign as campaign members.
How attendees sync
When a user RSVPs to an event, Bevy sends their details to Salesforce and links them to the event's Campaign:
- We match the person to an existing Contact by email. If no Contact exists, we match an existing Lead; if neither exists, we create a new Lead.
- We create a Campaign Member on the event's Campaign, linked to that Contact or Lead.
- By default we send first name, last name, and email. Additional attendee fields (company, registration-form answers, etc.) can be mapped to your Salesforce fields on request — just tell us the Salesforce field names.
Tracking check-in
The Campaign Member's Status field reflects where the attendee is in their journey. You configure the three status values in settings:
- Registered — the user has RSVP'd
- Attended — the user has checked in
- Unregistered — the user cancelled
Enable and configure
- Log in to your Bevy admin dashboard
- Navigate to the General Settings at
/accounts/dashboard#/admin/settings/general/ - Locate the Salesforce section
- Check "Sync Bevy attendees as leads"
- Configure the following fields:
- Lead/Campaign status — registered
- Lead/Campaign status — attended
- Lead/Campaign status — unregistered
- Click Save Settings
By default, we send first name, last name, and email. For anything additional, we just need to know what the names field names are in Salesforce that correspond to what data you want us to send.