When someone RSVPs to an event on Bevy, Bevy can update or create a Salesforce Lead or Contact and add them as a Campaign Member on that event’s Campaign. Status updates when they check in or cancel.
This page covers what happens when someone RSVPs, checks in, or cancels an event registration, and Bevy sends that person to Salesforce as a Campaign Member. Connection steps stay in Salesforce integration - Connect Bevy to Salesforce. Which path your community uses is in Salesforce integration - Introduction. How Bevy chooses a Contact versus a Lead, guest registrations, and duplicate emails are in Salesforce integration - Match Bevy records.
What Bevy sends when someone RSVPs
Bevy syncs the registration one-way to Salesforce:
- Bevy matches the person to an existing Contact or Lead by email, or creates a new Lead when neither exists. See Salesforce integration - Match Bevy records for the full match rules.
- Bevy creates or updates a Campaign Member on the event’s Campaign, linked to that Contact or Lead.
- The Campaign Member status reflects whether the person registered, checked in, or canceled.
The Campaign Member lands on the Campaign for that event. Event → Campaign sync is covered in Salesforce integration - Sync events as campaigns. If the event does not yet have a Campaign in Salesforce, Bevy can still update or create the Lead or Contact, and the Campaign Member is created when the Campaign is available.
Campaign Member status
Bevy updates the Campaign Member status from the attendee’s registration state:
| What happens on Bevy | Campaign Member status (default) | Native setting label |
|---|---|---|
| Someone registers (RSVPs) | Registered | Lead/Campaign status - registered |
| Someone checks in | Attended | Lead/Campaign status - attended |
| Someone cancels | Unregistered | Lead/Campaign status - unregistered |
On Integration Suite, you enter the status names in the setup wizard. On the native connection, you set them under General Settings → Salesforce. The Campaign in Salesforce must include each status name you use. If a status is missing on that Campaign, Salesforce stores Sent instead.
Guest registrations use the same status names as signed-in attendees. Details are in Salesforce integration - Match Bevy records.
When the sync runs
After someone registers, checks in, or cancels, Bevy queues the record. Salesforce usually shows the Lead or Contact and Campaign Member within about five minutes. On Integration Suite, only registrations created or changed after you connect are sent. Contact Bevy Support if you need existing registrations sent.
Turn on attendee sync
Which controls you use depends on your connection path.
Integration Suite (Settings → Integrations → Salesforce): after you connect and finish the setup wizard, Bevy sends registration updates as Campaign Members. There is no separate Sync Bevy attendees as leads checkbox on this path. Enter Campaign Member status names for registration, check-in (Attended), and cancel (Unregistered) in the wizard. Map at least last name and email for the person.
Native Salesforce integration (General Settings → Salesforce):
- Log in to your Bevy admin dashboard.
- Open General Settings at
/accounts/dashboard/#/admin/settings/general/. - Locate the Salesforce section.
- Check Sync Bevy attendees as leads.
- Confirm event Campaign sync is also on (see Salesforce integration - Sync events as campaigns) so registrations can attach to the event Campaign.
- Set Lead/Campaign status - registered, Lead/Campaign status - attended, and Lead/Campaign status - unregistered (defaults Registered, Attended, and Unregistered).
- Select Save Settings.
Note: If your community already uses the native connection, leave it in place while Bevy moves you to Integration Suite. Do not turn native sync off yourself.
Default field mapping
By default Bevy sends first name, last name, and email for the person. Company and other attendee or registration fields are included when they are mapped.
| Bevy field | Salesforce field | Notes |
|---|---|---|
| First name | FirstName | Sent on create and update |
| Last name | LastName | Required for new Leads. Map it in the Integration Suite wizard. |
| Used to match an existing Contact or Lead. Map it in the wizard. | ||
| Company | Company | Sent when mapped. On the native connection, empty company becomes N/A when Bevy creates a Lead. On Integration Suite, unmapped company becomes Bevy User. |
To send more fields (company, registration-form answers, Ticket Type, and similar):
- Native connection: Contact Bevy Support with each Salesforce field API name and the Bevy data you want mapped. You can also set create-only or update-only behavior per field.
- Integration Suite: Map fields in the setup wizard, including optional attendee or event fields onto Lead or Contact. On the Salesforce side you can type a field name, including a custom field. On the Bevy side you pick from the list. If a Bevy field you need is not listed, contact Bevy Support.
Native field maps do not carry over when you move to Integration Suite. Enter the mapping again in the wizard.
Check a test registration
- Register a test person on a published event that already syncs as a Campaign (or publish a new test event first).
- Wait about five minutes.
- In Salesforce, confirm a Lead or Contact for that email, and a Campaign Member on the event’s Campaign with the Registered status (or the name you configured).
- Optional: check the person in on Bevy, wait again, and confirm the Campaign Member status moves to Attended (or your configured name).
If nothing appears, confirm the connection in Salesforce integration - Connect Bevy to Salesforce, confirm attendee sync is on for your path, confirm the event has a Campaign, and confirm last name and email are mapped. For duplicate emails, converted Leads, or guest registrations, see Salesforce integration - Match Bevy records.