Skip to content

0c – Setup Lead Matching

Jim Hubert edited this page Sep 29, 2021 · 11 revisions

Note: This is optional functionality, if your organization does not use Leads or does not want to match Summit Events Registration records with Leads then you can stop reading and skip this step. If you are looking for Contact Matching instead click here

When a Summit Events Registration record is created several fields about the person registering are populated. These values only exist in the Summit Events Registration object unless you select a Contact or Lead Matching Rule on the Summit Events record. If you select a Lead Matching Rule on the Summit Events record this rule will check to see if a Lead record exists in Salesforce for this person:

  • If the Lead Matching Rule finds a Lead record that matches the rule logic, it matches this Lead with the Summit Events Registration record.
  • If the Lead Matching Rule does not find a Lead record that matches the rule logic, it will create a new Lead record and match this newly created Lead with the Summit Events Registration record.

Matching Rules

Lead Matching Rules in Summit Events utilizes native Salesforce Duplicate Rules and Custom Matching Rules. This allows an organization to create their own matching logic. You can learn more about this at Salesforce Duplicate Rule and Matching Rule documentation

Note that any fields mapped using Custom Metadata (as detailed in the "Adding Additional Field Values When Matching Rules Create New Lead" section below) are also available to be included in your Salesforce Duplicate Rule.

Note that when using a Salesforce Duplicate Rule it is important that you set the "Record-Level Security" field value to "Bypass sharing rules" so the guest user profile used for registration can see the Leads in the org, and also that the "Alert" checkboxes are unchecked so the registrant does not receive alert messages:

Lead Duplicate Rule Settings

How to Set Fields on Summit Events record to Use Lead Matching Rules

Option 1: Contact Matching first, then Lead Matching if Contact match not found

Both Contact Matching and Lead Matching setup on an event record

Option 2: Lead Matching only

Lead Matching only setup on an event record

Field Values Automatically Added to Leads When Matching Rules Create New Leads

When a new Lead is created by the Lead Matching Rule the following fields from the Summit Events Registration record are automatically added to the Lead record:

Hardcoded values mapped from Summit Events Registration to Lead

Adding Additional Field Values When Matching Rules Create New Leads

If you want additional field values to be added to the Lead record you can use the "Custom Metadata Lead Matching Method" on Summit Events to do this. Custom Metadata Types is the Salesforce tool that allows an admin to create field mappings that are read by the code in the managed package - for details take a look at More Info On Custom Metadata Types.

To setup your custom field mappings:

  1. Select a "Custom Metadata Lead Matching Method" value on the Summit Events record
  2. Follow the instructions here to access the Custom Metadata records in Setup to Add or Edit Custom Metadata Records
    • Go to "Setup", then in the Quick Find box at the top of the setup menu type "Custom Metadata Types
    • Click on the "Custom Metadata Types" link and find the "Summit Events Lead Matching Mapping" section
    • Click on "Manage Records" link before this section (don't click on the Summit Events Lead Matching Mapping" link)
  3. Create a Custom Metadata record for each field value you want to be added to the Lead record. Note that you have the option to either map values from the Summit Events Registration record or add hardcoded values that will be added to the Lead record.
    • If you are mapping field values from Summit Events Registration make sure you use the field API name, not the field label.

Here is an example of what the Custom Metadata records look like for Leads:

Summit Events Custom Metadata example

Clone this wiki locally