How Capture Matching Logic Works
Overview
Clari’s Capture Default is designed to log activity and create missing contacts from that activity for the Clari user assigned to the Account Owner or Opportunity Owner in Salesforce.
Clari uses Matching Logic to properly identify the account or opportunity, and then logs the activity to the account or opportunity, and creates missing contacts and/or contact roles. Below is a detailed walkthrough of the matching logic, as well as ways to expand on the activity and contacts captured.
Matching Logic
This is how Clari’s activity mapping logic works, in order. Please also refer to the diagrams, which provide a detailed walkthrough of the matching logic from an account and opportunity perspective.
1. Domain matching
Does the activity domain match the account website field on the Account record and/or any of the current contacts on the account?
2. Ownership
a. Account Owner (Default): By default, Capture matches to the user assigned to the “Account Owner” field in Salesforce.
b. Opportunity Owner (Default): By default, Capture matches to the user assigned to the “Opportunity Owner” field in Saleforce.
3. External participant/contact role matching
Capture looks at the current contacts on the account and/or the contact roles on the opportunity to properly match to the correct account or opportunity. If an existing contact/contact role is found on the activity and also found in Salesforce, then Capture will log the activity to this account/opportunity and create any missing contact/contact roles under that account/opportunity.
4. Tiebreakers (Default)
In the event Capture can’t single out an account/opportunity when matching, then Capture would rely on the following tiebreakers.
a. Account Level Tiebreakers:
- Select the account that has the largest number of contacts with a matching email domain.
- Select the account that has the opportunity that was most recently updated.
b. Opportunity Level Tiebreakers:
- Select opportunity that has contact on the activity that has an existing contact role on one of the opportunities.
Account Level Matching
Account Level Tiebreakers:
-
Select the account that has the largest number of contacts with a matching email domain (Default).
-
Select the account that has the opportunity that was most recently updated (Default).
Opportunity Level Matching

Opportunity Level Tiebreaker: Is there a contact on the activity that has an existing contact role on one of the opportunities? (Default).
This chart covers basic questions for when you have default settings in place.
| Activity Example | Will Capture write the activity back to SFDC? | Will Capture create the the missing contacts on the activity in SFDC? | How do I change the configuration to capture these activities and contacts? |
| Email Sent by Account/Opportunity Owner | yes | yes | NA |
| Email Received by Account/Opportunity Owner | yes | yes | NA |
| Emails sent by non Account/Opportunity Owner, but the Account Owner IS included on the email | yes | yes | NA |
| Emails sent by non Account/Opportunity Owner to a client, and the Account/Opportunity Owner is NOT included on the email | no | no |
For activity and contacts to be written back for these users, you will need to enable Custom Owner fields, Teams, or Non-Ownership in the Activity Logging Configuration and Contact Sync Configuration. By enabling one of these options, Capture will then look beyond the "Account Owner" when matching.
|
| Emails received from a Client and the Account/Opportunity Owner is NOT included on the Email | no | no |
For activity and contacts to be written back for these users, you will need to enable Custom Owner fields, Teams, or Non-Ownership in the Activity Logging Configuration and Contact Sync Configuration. By enabling one of these options, Capture will then look beyond the "Account Owner" when matching.
|
| Meeting Scheduled by Account Owner | yes | yes | NA |
| Meetings Received by Account Owner | yes | yes | NA |
| Meeting Scheduled by non Account Owner, but the Account Owner IS included on the Meeting | yes | yes | NA |
| Meeting Scheduled by non Account Owner, but the Account Owner is NOT included on the Meeting | no | no |
For activity and contacts to be written back for these users, you will need to enable Custom Owner fields, Teams, or Non-Ownership in the Activity Logging Configuration and Contact Sync Configuration. By enabling one of these options, Capture will then look beyond the "Account Owner" when matching.
|