Advanced Contact Sync Settings in Capture

This article covers Advanced Contact Sync Settings in Capture. If you're looking for a specific set of Contact Sync Settings in Capture, click the article you need from this list: 

1. Contact Sync Settings in Capture 
2. Advanced Contact Sync Settings (that's this article, read on)
3. Salesforce Integration Settings
4. Matching Logic Settings


These settings allow you to get more Advanced—and fine-tune your standard Contact Sync Settings. Check out this page to learn more about standard Contact Sync Settings. Read on for details on Advanced Contact Sync Settings.  👀
 

1. Generate Multiple Contacts With The Same Email Address

When set to Yes, this setting allows for multiple contacts of same email address. It's best practice to set this to No if you don't want duplicates.

This is set to No by default. Contact your Clari CSM if you want this updated. 
 

2. Check For Duplicates Across Accounts

If a contact already exists on a potential matching Account and this setting is set to Yes, Capture will skip creating the contact because the contact was found on another Account. If this setting is set to No, Capture will add the contact to all matching Accounts. 

This is set to Yes by default. If duplication isn’t a concern and you would rather have all contacts on all matching accounts, then it might make sense to change it to No. 

3. Convert Leads to Contacts

If enabled, leads detected in sales rep activity will automatically be converted into contacts. Additional Salesforce setup is required.

This setting is disabled by default. This feature allows Capture to automate your lead conversion process. 


How does Clari treat leads? 

Leads are treated similarly to contacts, with the exception they don’t live under an opportunity or account. Clari offers the ability to see the full picture with leads, given activity can be associated with leads. This means when a lead is converted to a contact, all the activity that took place with the lead also gets converted. 


How does the Clari lead conversion functionality work? 

If a contact captured by Clari does not match an existing CRM contact, Capture will also look for an existing lead record with a matching email address.

If a matching lead is found, Capture looks for matching Accounts/Opportunities with the same domain. If an account/opportunity is located, Capture will convert the lead to a contact and associate to the account/opportunity. Clari does not convert a lead to a contact until an account or opportunity with the same domain is added to SFDC. 


How is Lead Conversion configured? 

To enable lead conversion, you'll need to confirm that you have set up the Apex Trigger needed to support lead conversion in Salesforce. Check out this page on adding an Apex Class to Salesforce.
 

4.Enrichment

Clari uses ClearBit as part of the standard Capture license. ClearBit gets contact information when it can’t be determined from email metadata (like the contact's title). 

This is enabled by default. We strongly suggest having ClearBit enabled so you get as much data for each contact as possible. 

For more info, check out this article on ClearBit for Clari.
 

5. Conditional Filters

This setting is disabled by default. It allows you to create conditional filters to filter out the data you don’t want to sync back to your CRM. Like contact title-based conditional filtering (e.g., only create contacts that have CEO, CTO, CFO, CIO titles). 

Check out some use cases
 

• As a marketing manager, I want to run campaigns for executives who are above a certain level in the org hierarchy so that I can effectively nurture the contacts.
• As a Sales Ops team member, i don’t want to log the contacts where opportunity association was not found.

Supported Conditional Filters

 

 

5. Custom Fields

This setting is disabled by default.

The goal of this feature is to expand the capabilities of custom fields within Contact Syncing and Activity Logging. It also creates write-back values to event, task, and contact objects in SFDC from email and meeting objects.

Using dynamic fields in their configurations, you can better tie activity data to its relevant CRM data at the points in time that the activities took place. 

Check out some use cases
 

• As a marketing ops team member, I want to see the lead sources for all my contacts in order to track how I am creating contacts from different sources.
• As a sales ops manager, I want to be able to mark contacts that are already engaging with the sales team in order to exclude them from campaigns meant for net new prospects.
• As a sales manager, I want to see the breakdown of my rep’s meetings by Opp Stage to see in what stages my reps need to be engaging more with the prospect. I want to see the difference in deal sizes between meetings to see which meetings made an impact on the scope of the deal. 
• As an SE, I want to see the breakdown of meetings by Opportunity type to see if I’m getting over-indexed in a certain deal type.

Check out these definitions of the fields from the images below.

Field Type: The type of field—Dynamic or Static. For example, task “Status" is a static field, whereas Opportunity “Stage” is a dynamic field.
Destination Field: This is the field you would like Capture to update in SFDC.
Field Value (Only Static Fields): The value you want the destination field in SFDC to get updated with.
Entity Object (Only Dynamic Fields): The source entity which will be used to derive value.
Source Field (Only Dynamic Fields): The value with which the Destination Field is updated is obtained from the Source Field.

 

6. Required Fields For Contact Creation In The Configured CRM

Capture can make the contact’s title, First Name, and Last Name mandatory for a new contact to be created. 

By default, First Name and Last Name are required fields. Keep in mind Clari is also enriching Contacts with ClearBit, and these three fields (First Name, Last Name, and Title) are the standard fields we enhance via ClearBit. 
 

7. Create Tasks Or Events In The Same Order As The Emails And Meetings Are Processed

This option is enabled by default—and it writes all the emails and meetings data to SFDC in the order that they were created or completed.

Pro: You see the order of event creation.

Con: It can be slower because you're recording 1 at a time. Basically, the data going to SFDC has to wait in a line—instead of all the data just jumping in at the same time.

But the best choice for most companies is to have this option enabled.