Home > DupeBlocker Advanced Functions > Web to Lead

Web to Lead

Since DupeBlocker will work with any single insert it will trigger for Leads entered using the Web to Lead capability within Salesforce and will catch duplicate Leads as well as Lead to Contact and Lead to Account matches.

With the release of DupeBlocker 2 and the ability to auto-merge Leads and/or auto-convert Leads into existing Contacts or Accounts, Web to Lead scenarios can now be customized to not just create Warnings for duplicates (as described below) but also to auto-merge or auto-convert an incoming Lead.  The use of Scenario Filters, also new in DupeBlocker 2, allows the ability to have auto-merge and auto-convert scenarios fire JUST for Web to Lead inserts (i.e. by creating a filter based on Lead Source).

More information on Auto-Merge, Auto-Convert and Filters can be found via the following links:

DupeBlocker Advanced Functions -> Auto-Merge.

DupeBlocker Advanced Functions -> Auto-Convert.

DupeBlocker Step by Step Instructions -> Scenarios -> Creating/Editing Scenarios -> Scenario Filters.

Special Handling of Web to Lead Inserts (overriding "Do Not Insert" and "Redirect to Existing")

Leads inserted via Web to Lead WILL NOT block inserts, but rather will always create warnings instead.  In order to facilitate this special handling of Leads the "Web Lead Sources" tab needs to be updated with the Lead Source assigned to Leads generated from the website.  This is accessible from the DupeBlocker Settings tab.



Select "Web Lead Sources" on the bottom left of the screen.





The list is pre-populated with Lead Source values.  New values can be added by clicking "Add".  Existing values can be removed by selecting the value from the list and clicking "Delete".

Warnings will be created for all inserts that meet scenario matching criteria even if the "Match on Insert" setting in the scenario is set to something other than "Report Duplicate".



The warning will be assigned to the user that is assigned to Web to Lead inserts.  A task will be created for either the current user or scenario owner based the "Create Task for Warning" setting.



Example of a Lead to Contact warning generated from a Rigid scenario that is set to "Do Not Insert".  The "Triggering Action" does indicate "Duplicate found on Update" as Web to Lead inserts are classified as updates in Salesforce.



Duplicate records can be merged or converted in the same manner as all other DupeBlocker potential duplicates.  More information on merging/converting duplicates can be found in DupeBlocker Step by Step Instructions -> Warnings -> Merging/Converting Duplicates.


See also