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. Web to Lead scenarios can 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 allows the ability to have auto-merge and auto-convert scenarios fire JUST for Web to Lead inserts. Scenario Filters can be created to subset based on a specific field in the Lead that identifies it as a web lead (e.g. Lead Source), and/or based on the current user that entered the Lead, assuming there is a specific user that creates web leads. Dual filters allow for triggering a scenario based on attributes of the incoming record allowing it to match to ANY existing record (e.g. Lead Source starts with Web will match to ANY record regardless of its' Lead Source value).
- More information on Auto-Merge can be found HERE
- More information on Auto-Convert can be found HERE
- More information on Filters can be found HERE
Special Handling of Web to Lead Inserts (overriding "Do Not Insert" and "Redirect to Existing")
Typically separate scenarios are created to handle Leads inserted from Web to Lead one way and all other Lead inserts another way using Scenario Filters as described above. For example, web Leads may be auto-merged, auto-converted, or simply reported as duplicates, whereas Leads inserted by users may be blocked with either an error message or a redirect to an existing record.
DupeBlocker can be configured to NEVER block Leads inserted from the web even when they trigger a scenario set to Do Not Insert or Redirect to Existing (Warnings are created in place of the block). In order to facilitate this special handling of Leads the Web Lead Sources Settings needs to be updated with the Lead Source assigned to Leads generated from the website. This is accessible from the DupeBlocker Settings tab. More information on Web Lead Sources in the DupeBlocker Setting Tab can be found here
- 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 Do Not Insert or Redirect to Existing.
- A Warning Task will be created for either the current user or scenario owner based the Create Task for Warning setting in the scenario
- 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 HERE.
Example Scenarios
Scenario 1: Auto-Merging the Lead, Current User Filter
Match new Leads created by the "designated" web user (the user that creates the web Lead) to ANY existing Lead. New Leads will be auto-merged into the existing Leads.
Scenario 2: Reporting the Duplicate, Dual Object Filters (Source Filter ONLY)
Match new Leads where the Lead Source contains "AppExchange" to ANY existing Lead. The new Lead will be inserted and a warning will be created alerting the Scenario Owner that a duplicate was detected.
Scenario 3: Auto-Merging the Lead, Dual Object Filters (Source AND Target Filters)
Match new Leads where the Lead Source starts with "Web" to existing Leads owned by a specific queue. New Leads will be auto-merged into the existing Leads.
Scenario 4: Auto-Converting the Lead, Current User Filter and Single Object Filter
Match new Leads created by the "designated" web user (the user that creates the web Lead) to existing Accounts where the Account Type = Customer.
Filter Option #2
Scenario 5: Block Leads NOT inserted via Web to Lead, Current User Filter
Match new Leads NOT created by the "designated" web user (the user that creates the web Lead) to ANY existing Lead. New Leads NOT created by the web user will be BLOCKED from insertion with an error message displayed showing a link to the matching record. This scenario would be for standard Salesforce users entering Leads directly within the Salesforce User Interface.
