Root Cause Analysis
EnterpriseIdentify where duplicates come from to prevent them at the source, not just clean them up.
Overview
Root Cause Analysis examines your duplicate records to determine how they were created. By understanding the sources of duplicates, you can implement preventive measures upstream.
Source Types
True Record classifies duplicate sources into six categories based on signals in your Salesforce data:
How Source Inference Works
True Record infers the source of each duplicate record using multiple signals, processed in priority order. The first method to produce a result is used.
| Priority | Method | What It Checks | Confidence |
|---|---|---|---|
| 1 | LeadSource Field | Checks the LeadSource field value against known patterns for web forms, imports, integrations, and manual entry. | 80-95% |
| 2 | Owner/CreatedBy Patterns | Checks if the record owner or creator matches integration user patterns like 'api_user', 'automation', or tool-specific names. | 90% |
| 3 | Name Patterns | Checks if the record name suggests an import (starts with 'Imported', 'Test', 'Sample', or is purely numeric). | 70% |
| 4 | CreatedDate Clustering | Groups records created within 60 seconds. If 10+ records share a timestamp, they're classified as bulk import. | 80% |
| 5 | Default | If no signals are detected and the record has a CreatedDate, defaults to Manual Entry. Otherwise, Unknown. | 50-60% |
LeadSource Field Mapping
The LeadSource field provides the strongest signal for source classification. Here are example values that map to each category:
Tip: Standardizing your LeadSource picklist values improves source detection accuracy. Use consistent naming across your organization.
Bulk Import Detection
Even without explicit LeadSource values, True Record can detect bulk imports through additional signals:
Dashboard Features
The Root Cause Analysis dashboard in Analytics provides several views to understand your duplicate sources:
Improving Source Detection
To get more accurate source classification, consider these best practices:
Populate LeadSource Consistently
Ensure all lead/contact creation points set the LeadSource field. Use automation to set it based on the record's origin.
Use Descriptive Integration User Names
Name your API/integration users clearly (e.g., 'HubSpot_Integration', 'Marketo_Sync'). This helps identify which tool created records.
Configure Marketing Automation Sources
Set up your marketing tools (HubSpot, Marketo, etc.) to populate LeadSource with their name when creating records in Salesforce.
Frequently Asked Questions
Enterprise Feature
Root Cause Analysis is available on the Enterprise plan. Upgrade to identify where duplicates come from and prevent them at the source.
View Enterprise pricing