Definition
Matching Rules is a Setup page where administrators create rules that define the criteria used to identify duplicate records. Matching rules specify which fields to compare and what matching algorithms to use (exact match, fuzzy match, etc.). They work in conjunction with Duplicate Rules to detect and prevent duplicates.
Real-World Example
The admin at BrightWave Marketing creates a Matching Rule on the Contact object that uses fuzzy matching on First Name and Last Name, exact matching on Email, and fuzzy matching on Company Name. This rule catches duplicates even when names are slightly misspelled, like "Jon Smith" matching "John Smith" at the same company.
Why Matching Rules Matters
Matching Rules in Salesforce define the criteria used to identify potentially duplicate records. Administrators configure them on the Matching Rules Setup page, specifying which fields to compare and what matching algorithms to apply — options include exact match, fuzzy match (which catches variations like 'Jon' vs. 'John'), and acronym match. Matching Rules work in tandem with Duplicate Rules: the Matching Rule detects similarities, and the Duplicate Rule dictates what happens — block the duplicate, alert the user, or log it in a duplicate record set. This two-rule system gives admins granular control over duplicate prevention.
As an org accumulates data from multiple sources — web forms, imports, integrations, and manual entry — duplicate records become inevitable without proper Matching Rules. Bad data inflates marketing costs (sending the same email twice), confuses sales reps (who owns this lead?), and corrupts analytics. Poorly configured Matching Rules can be equally problematic: rules that are too strict miss real duplicates, while rules that are too loose flag false positives and frustrate users. Admins should test their Matching Rules using Salesforce's built-in duplicate job analysis tool, which scans existing records and shows how many matches each rule configuration would find before going live.
How Organizations Use Matching Rules
- BrightWave Marketing — BrightWave Marketing configured a Matching Rule on the Contact object using fuzzy matching on First Name and Last Name, exact matching on Email, and fuzzy matching on Company Name. The rule catches duplicates like 'Jon Smith' matching 'John Smith' at the same company. Within the first month, it identified 2,300 duplicate contacts that had been inflating their email campaign audience size by 12%.
- Apex Realty Group — Apex Realty Group imports 5,000 new leads monthly from Zillow and Realtor.com listing inquiries. Their Matching Rule compares Phone (normalized), Email (exact), and Street Address (fuzzy) to detect leads who inquired on multiple properties. Agents now see a unified view instead of working the same prospect from three different lead records.
- GreenLeaf Nonprofit — GreenLeaf Nonprofit uses Matching Rules on their Donor (Contact) records with fuzzy matching on Name and exact matching on a custom Donor ID field. During their annual giving campaign, the rule prevented 850 duplicate donor records from being created via their online donation form, ensuring accurate gift totals and preventing duplicate tax receipts.