How does Contacts Sync work?
Contacts Sync helps event and field marketers capture all of the leads and meetings from their events and sync them to Salesforce.
This article goes over:
- Required fields and mapping
- Optional fields and mapping
- Sync direction
- Duplicate prevention
- Company<>Account link
- Lead & Customer Tags
- Campaign Members
- API call frequency
If you haven't done so already, first learn how to enable the Integration for your Org. You can also read about what Campaigns are and how you should be using them.
Contacts sync with Salesforce based on their tag. If they are tagged as a Lead, they will sync to Salesforce as Leads. If they are tagged as a Customer, they will sync to Salesforce as a Contact. (Somewhat confusingly, Salesforce has both Leads and Contact record types.)
Contacts in EventGeek belong to your Org and can be added to multiple events and meetings. If a Contact is added to an event and the event is connected to a Salesforce Campaign, then the Contact will appear in Salesforce as a Campaign Member. This is the key step to tracking event ROI in your CRM.
Required fields and mapping
The following fields are required to sync a Contact from EventGeek to Salesforce:
- First name
- Last name
- Company (see Company<>Account link below)
- Lead or Customer tag (see Tags below)
If these fields are not present, you can still create the Contact in EventGeek. If they are tagged as a Lead or Contact, a "Missing Field" error message will be provided.
Optional fields and mapping
The following fields and a few others including social media links and address information can be optionally set up to sync with Salesforce Leads and Contacts:
- Main Phone
- Mobile Phone
- Note (maps to Description in Salesforce)
- Owner (EventGeek user have same email address as Salesforce user)
These field mappings can be enabled, disabled or mapped to other fields on Leads or Contacts in Salesforce. See Salesforce integration settings.
Contacts Sync can run from EventGeek to Salesforce. If new Leads or Contacts are added to Salesforce, they will not automatically appear in EventGeek. If updates are made to Leads or Contacts in Salesforce, those updates will not be reflected on the synced Contacts in EventGeek.
If the Lead or Contact already exists (email match) in Salesforce, then the sync will not create a duplicate.
The sync will update the mapped fields on the existing Lead or Contact with any new values, including overwriting any existing values on the Notes<>Descriptions or Owner field. If you do not want to overwrite the description of Owner value on Leads or Contacts in Salesforce, please disable the sync on those fields.
Note that if there are two or more Leads or Contacts in your Salesforce with the same email address, the sync will only update the first Lead or Contact found.
A Salesforce ID, which links to the record, Sync Status and a Last Sync timestamp are provided under the Contacts tab of an event connected to Salesforce for ease of identification.
Contacts must have a Company to sync with Salesforce, whether they are tagged as a Lead or Customer.
When adding a Contact to an event, you can create a new Company or select an existing one from your Salesforce Accounts. The 🔄 icon is shown next to Companies linked with Salesforce Accounts.
Company is set automatically when you add a Contact via Leads Inbox, though it can be updated at any time.
Lead & Customer tags
Contacts with the Lead or Customer tag are synced to Salesforce as Members of Campaigns connected to events.
- If tagged as Lead, the Contact syncs as a Lead
- If tagged as a Customer, and Company is linked to an Account, then the Contact syncs as a Contact in that Account
- If tagged as a Customer, and Company is not found, then the sync shows an "Account not found" error message
EventGeek purposefully has Read-Only Access to Accounts (see Permissions) and does not create new Accounts in your Salesforce.
To add a synced Contact as a Member of a Campaign, connect the event with the Campaign on the Event Info > CRM tab.
Note that a Contact does not need to be associated with a Campaign-connected event for the sync to run. The sync will run as long as the Contact has the required fields and a tag (see above).
If the Contact is subsequently added to a Campaign connected with an event, then the sync will re-run, adding the Contact to the Campaign.
API call frequency
The sync happens immediately, with every update to a Contact in EventGeek. If there are frequent updates in a short timespan, the updates are batched to send a single API request.