How Clari Capture and Salesloft Activity Logging Work Together?
A common question that comes up from our customers is: “Should we keep both Clari Capture and Salesloft activity logging enabled?” Clari Capture and Salesloft can both log emails and meetings to Salesforce, but if both systems write the same activity, duplicate Tasks or Events can be created unless the configuration is intentionally coordinated.
Clari Capture has a de-duplication feature that can be enabled for customers that also use third-party applications like Outreach to write back activity to Salesforce. The third-party application should be able to push a unique identifier back to Salesforce. Since the unique IDs are extracted from the email server, they are used in Clari Capture to identify whether the activity has already been written back to Salesforce or not.
Most common sales engagement platforms used for activity writeback:
| Tool | Email De-duplication | Meeting De-duplication |
|---|---|---|
| Salesloft | Supported | Not Supported |
| Outreach | Supported | Not Supported |
| Groove | Supported | Supported |
Note: As long as the other system supports writing back unique identifier to salesforce, Capture de-dupe can be configured.
Below are some practical ways to configure the two systems:
Option 1: Keep both systems enabled
In this model, both Clari Capture and the other systems activity logging remain on. You will see duplicates in salesforce for events and tasks.
Option 2: Keep both systems enabled and configure Capture deduplication
In this model, both Clari Capture and Salesloft activity logging remain on. Capture checks Salesforce for an existing activity before writing its own record. If existing activity is found, it skips the creating a new activity record.
Note: Cannot de-duplicate meetings as Salesloft cannot reliably write back unique meeting ID from Salesloft to salesforce.
Option 3: Keep Capture activity logging on and turn off Salesloft activity logging or vice versa
In this model, Clari Capture is the single system responsible for writing email and meeting activities to Salesforce. Salesloft can continue to support sales engagement workflows, but its CRM activity logging is disabled.
Option 4: Use team-based ownership: Capture for selected teams, Salesloft for SDR/BDR activity
In this hybrid model, configure Capture activity logging only for the teams whose activity should be written by Capture—for example, AEs, CSMs, or other selected customer-facing teams. Leave SDR/BDR activity logging owned by Salesloft.
Please reach out to your CSM to discuss the Clari Capture de-duplication feature.
