Bevy matches each person to a Salesforce Contact or Lead by email, then links them to the event or chapter Campaign. The same match covers duplicate emails, guest registrations, campaign dates, Ticket Type, and a change of Salesforce organization.
After Salesforce is connected, Bevy matches people by email and links them to a Campaign. Which connection you use is covered in Salesforce integration - Introduction. Connection steps are in Salesforce integration - Connect Bevy to Salesforce.
Match a person to a Contact or a Lead
You can sync to Contacts instead of Leads. On the native Salesforce integration, Bevy looks up a Contact with that email, then a Lead, and creates a Lead only when neither record exists.
| What Bevy finds | What Bevy does |
|---|---|
| One Contact with that email | Updates that Contact, then creates or updates the Campaign Member. |
| No Contact, and one Lead with that email | Updates that Lead, then creates or updates the Campaign Member. |
| No Contact and no Lead | Creates a Lead, then creates the Campaign Member. |
After the first successful match, Bevy stores the Salesforce record ID and uses that ID on later syncs. Email is the lookup when no stored ID exists, or when that stored record is gone.
Important: If Bevy is set to create a Contact, and a Lead with that email already exists, that person may not sync. Ask Bevy Support to keep the order Contact, then Lead, then create a Lead.
On the native connection, a Lead that Salesforce has already converted to a Contact is skipped unless you turn on Follow converted leads to contacts under Admin dashboard → General Settings → Salesforce. With that setting on, and Contact fields included in the mapping, Bevy updates the Contact the Lead was converted to.
On Integration Suite, an existing Lead or Contact is updated by email. Otherwise a new Lead is created. Map last name and email in the setup wizard, as described in Salesforce integration - Connect Bevy to Salesforce. If a converted Lead stops updating, contact Bevy Support.
Choose a record when two share an email
If Salesforce has two records with the same email, Bevy does not update them and does not create the Campaign Member for that chapter member or attendee.
Two Contacts with one email, or two Leads with one email, are a conflict. Bevy stops syncing that person.
On the native connection, turn on Force sync with the last modified lead under Admin dashboard → General Settings → Salesforce. Bevy then uses the Contact or Lead with that email that Salesforce modified most recently.
That control is part of the native connection. On Integration Suite, contact Bevy Support if two records share an email.
Sync a guest registration
When guest registration is enabled, Bevy syncs that guest registration by the email the guest entered. If a Contact or Lead with that email exists, Bevy uses it. Otherwise Bevy creates a new record. You do not need Salesforce to create the Contact first.
Guest registrations use the same Campaign Member statuses as a signed-in attendee: Registered, Unregistered, and Attended, unless your community has chosen different statuses.
Send a campaign date without the time of day
Can the dates include date and time in Salesforce? Not on the standard Campaign Start Date and End Date fields. Those fields store the calendar day only.
For an event, Bevy sends the date the event was published as Start Date, and the event’s end date as End Date. For a chapter, Start Date is the date the chapter was created. A time of day on those standard fields is not kept.
To keep the event’s start or end time:
- In Salesforce, create custom Date/Time fields on Campaign.
- On the native connection, contact Bevy Support with each field’s API name and the Bevy date you want mapped.
- On Integration Suite, map the field in the setup wizard when it is listed. If it is not listed, contact Bevy Support.
The custom fields then hold the date and time. The standard Start Date and End Date fields still hold the calendar day.
Sync Ticket Type
You can sync Ticket Type as part of the integration. It is not sent until you map it to a Salesforce field.
- Native connection: Contact Bevy Support with the Salesforce field API name you want Ticket Type mapped to.
- Integration Suite: Map it in the setup wizard when Ticket Type is listed. If it is not listed, contact Bevy Support.
Check how Bevy prepares values
Bevy prepares values before sending them so they match what Salesforce accepts:
- Dates and times: Sent as ISO text with fractions of a second removed, for example
2025-09-22T10:30:00. - Decimal numbers: Sent as ordinary numbers.
- Empty fields: Left out.
- Campaign names: Names longer than 80 characters are shortened and end with
.... - Campaign Type: Bevy adds a prefix. The defaults are Bevy Event for events and Bevy Group for chapters. On the native connection, change them with Campaign type for Bevy events and Campaign type for Bevy groups under Admin dashboard → General Settings → Salesforce. If another type value is mapped, Bevy sends the prefix, a colon, and that value.
Connect one Bevy instance to each Salesforce organization
Can you connect more than one Bevy instance to the same Salesforce organization? No. Each Bevy instance needs its own Salesforce organization. A shared organization is not supported, and it can overwrite data.
Bevy finds people by email. Each instance also keeps its own copy of the Salesforce IDs it has created. A second instance cannot see the first instance’s IDs, so it can treat those records as its own.
- Data is overwritten. If the same person exists in both instances, each instance updates the same Salesforce record. Names, company, and mapped fields become whichever instance synced most recently.
- Syncing can stop. If both instances create a record for the same person at about the same time, the organization can end up with two records that share one email. Bevy treats that as a conflict and stops syncing that person.
- You cannot tell which community a record came from. Bevy does not write a community name onto the Salesforce record. Leads, Campaigns, and Campaign Members from different communities look the same, and campaign reporting is wrong.
- Communities can see each other’s members. A shared Lead collects Campaign Members from both instances.
- API limits are shared. Both instances draw from the same Salesforce daily API limit.
- A deletion in one community does not clear the shared record. The other instance can still update it.
Cleaning this up is manual work in Salesforce. If you have more than one Bevy instance, choose one of these:
- A separate Salesforce organization per Bevy instance. This is the supported setup.
- Connect one Bevy instance only. Leave the integration off on the others.
- Use a single Bevy instance when the communities can share one. Contact Bevy Support before you consolidate.
If none of these fit, contact Bevy Support and describe the setup before you connect.
Switch to a different Salesforce organization
Can you switch to a different Salesforce organization after the integration is already running? Only after the stored Salesforce IDs are updated. Do not disconnect and connect a new organization on your own.
Bevy stores the Salesforce ID for each linked Campaign, Lead, Contact, and Campaign Member. Those IDs point at records in the current organization. A new organization uses different IDs. If the stored IDs stay as they are, syncs can fail or write to the wrong records.
Contact Bevy Support before you switch so they can:
- Re-link Bevy records to the matching records in the new organization
- Update the stored Salesforce IDs
- Check the mappings before syncs resume
Choose the organization before you connect. Connection steps stay in Salesforce integration - Connect Bevy to Salesforce.