Definition
Duplicate Rules is a Setup page where administrators create and manage rules that detect duplicate records when users create or update Leads, Contacts, Accounts, and custom objects. Each rule references a Matching Rule and specifies the action to take when duplicates are found: alert the user, block the save, or report the duplicate.
Real-World Example
The admin at Velocity Partners creates a Duplicate Rule on the Lead object that uses a fuzzy matching rule comparing Company Name and Email. When a sales rep tries to create a Lead with the same email as an existing Lead, the system blocks the save and displays the existing record. The rep can then choose to view the duplicate instead of creating a new one.
Why Duplicate Rules Matters
Duplicate Rules is the Setup page in Salesforce where administrators create, manage, and configure the full set of duplicate detection rules across their organization. Each rule on this page defines the target object (Lead, Contact, Account, or custom object), the Matching Rule it references for comparison logic, the action to take (block or alert), and optional conditions like record types or user profiles that control when the rule activates. The page provides a centralized view of all active and inactive rules, making it easy to understand the organization's complete duplicate prevention strategy at a glance.
Managing Duplicate Rules at scale requires a thoughtful governance approach. Organizations often start with a single rule on Leads and gradually expand to cover Contacts, Accounts, and custom objects as their data quality program matures. The Setup page allows administrators to activate and deactivate rules without deleting them, making it safe to experiment with new configurations. A common pitfall is creating overlapping rules on the same object that conflict with each other — for example, one rule that blocks and another that only alerts on similar matching criteria. This causes unpredictable behavior and user confusion. Best practice is to maintain one primary rule per object with clear, documented matching criteria.
How Organizations Use Duplicate Rules
- Velocity Partners — Velocity Partners' admin manages five Duplicate Rules across three objects from the Setup page. The Lead rule uses fuzzy matching on Company Name and exact matching on Email; the Contact rule matches on Email and Phone; and the Account rule uses fuzzy matching on Account Name combined with Billing State. Each rule's configuration is documented in the description field so any admin can understand the rationale behind the matching logic.
- NovaStar Financial — NovaStar Financial's compliance team requires duplicate prevention on their custom Loan Application object. The admin creates a Duplicate Rule that blocks applications with matching Social Security Number and Applicant Name, preventing the same person from submitting multiple applications. The rule is configured to apply only to the 'New Application' record type, allowing amendment records to be created freely.
- Brightfield Education — Brightfield Education manages separate Duplicate Rules for their Student, Parent, and Staff objects. Each rule references a different Matching Rule tailored to the data patterns of that object — students are matched on Name and Student ID, parents on Email and Phone, and staff on Employee Number. The admin uses the Setup page to monitor which rules are generating the most blocks and alerts across the organization.