Salesforce Duplicate Matching Rules can block Web-to-Lead submissions when a Duplicate Rule is set to "Allow and Alert." When a Web-to-Lead form submission matches an existing Lead record based on the Duplicate Rule criteria, the submission is blocked and the following error is returned to the submitter:
"Error: Salesforce could not create this lead because of the reason listed below. For more information about this error or help with Web-to-Lead, please contact Customer Support."
"Reason: You're creating a duplicate record. We recommend you use an existing record instead."
Note: In some cases, records may not be blocked even when the duplicate rule criteria are met. This typically occurs due to "dirty" records (records with data inconsistencies) or when several matched records are in the Recycle Bin. If you experience this behavior, empty the Recycle Bin and ask Salesforce Support to run a Physical Delete job on the object.
For Web-to-Lead form submissions, if a Duplicate Matching Rule is configured to either Block or Allow with Alert, any submission that matches the duplicate criteria is always blocked — even if the rule is set to "Allow." This is because Web-to-Lead operates as an automated process and cannot display the duplicate alert dialog to a user for confirmation. As a result, the default behavior is to block the submission.
Option 1 — Add a Condition to the Existing Duplicate Rule: Modify your existing Duplicate Rule to add a condition that excludes records where the running user is the default Web-to-Lead creator user. This prevents the Duplicate Rule from triggering on automated Web-to-Lead submissions while still evaluating duplicate matches for records created manually by sales users.
Option 2 — Create a Separate Duplicate Rule for Web-to-Lead: Create a second Duplicate Rule configured to run only when the running user is the default Web-to-Lead creator. Set this rule's action to "Allow and Report" (without the Alert option). This allows duplicate leads from Web-to-Lead to be created and logged in the Duplicate Record Report without blocking the submission.
Option 3 — Use Lightning Record Edit Form: Records added or edited using the Lightning Record Edit Form component bypass the duplicate alert behavior. Consider using this approach for use cases where leads are captured through custom Lightning components.
000387310

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.