Matching

Creating and matching lead and contact records

When attendees register for your event and their information matches an existing Contact, Lead, Person Account, or Account they will be related. If no match occurs, then a record will be created.

See below for more information...

Initial Configuration (Leads and Contacts)

By default, Salesforce automatically enables duplicate logic for Leads and Contacts. However, they do not include cross duplication logic.

For example, if you want matching logic for Contacts with Duplicate Leads or vice versa, those rules will need to be enabled manually.

  • Navigate to the Duplicate Rules setup page and activate the two rules shown in the image below:

Attendee Matches Existing Contact, Lead, or Person Account

If the registered attendee matches an existing contact or lead, the two records will automatically relate. Defined by Salesforce's matching rules.

  • The standard Salesforce rule matches on first name, last name, and email.

Custom Duplicate and Matching Rules

If you have custom matching rules for the Contact or Lead object, that will be used instead of the standard rule.

New Lead, Contact, or Person Account Record

If the duplicate rule does not relate the Attendee to an existing Contact, Lead, or Person Account than a new record will be created.

  • Define if a Lead, Contact, or Person Account record should be created if there are no matches on the Event Setting record.

New Leads

If you want new lead records created and have paid events, you need to update the Payment Method relationship. Navigate to the Blackthorn | Payments Setup Wizard and go to the Relationship Step. Under Payment Method Parents type in a select the "Lead" object.

Person Account

On the Event Settings record define

  • Registration Entity Type = Person Account
  • Entity Record Type (Optional) - Recommended
  • Update the Event Settings lookup on Event to reference the settings

For Person Accounts, setting the Record Type is important. Otherwise, the first Person Account Record type is used to create a person account.

Validation: The Registration Entity Type = Person Account is only allowed when the org has person accounts enabled.

Matching logic order:

  1. Attempt to match on existing Contacts as defined by Salesforce Contact Matching Rules (which starts with identical email matching)
  2. If there is a match, set the Attendee to the matching Contact.
  3. If there is no match, attempt to match on existing Person Account by Salesforce Lead Matching Rules.
  4. If there is a match, set the lookup on Attendee to the matching Account.
  5. If there is no match, attempt to match on existing Leads by Salesforce Lead Matching Rules.
  6. If there is a match, set the lookup on Attendee to the matching Lead.
  7. Finally if there is no match, a new Person Account will be created and associated with Attendee

Disable field mapping

Name, email, and salutation will still be automatically added to the Lead and Contact records.
If you don't want the Title, Phone or Company Name automatically added to the related Contact or Lead record, check the Disable Attendee/Contact/Lead fields custom setting.

Navigate to Setup | Type Custom Settings in the quick find | click "manage" next to the Blackthorn | Events Settings | and check the Disable Attendee/Contact/Lead/fields setting.

Bucket Account for New Contacts

Version 2.46 +

The Bucket Account For Individuals field is no longer required. Navigate to the Event Setting page layout and uncheck the field requirement. It will only be required if the Account Handling = Bucket Account.

All new contacts will be added to the Bucket Account For Individuals. Allowing you to access all the new Contacts created from your event. Later you can either link them to an existing Account or create a new Account.

  • Create an Account then define that Account on the Event Settings record.

Entity Record Type

If the Registration Entity Type is Contact, you can define the record type. If the Entity Record Type is blank, the default Record Type will be used.

If the Registration Entity Type is Lead, you can define the record type. If the Entity Record Type is blank, the default Record Type will be used.

  • Enter the Record Type name on the Event Setting record.

Account Matching

Coming soon...

This feature will be available in the middle of June 2019

New Account: When capturing the Company that the Attendee is registering for at checkout, if no matching Contact is found, the Account will be auto-created with this Account name.

HEDA-NPSP-Other: If you're using a version of Salesforce that auto-creates Accounts, an Account will be auto-created for this model. If you're using NPSP or HEDA, set this value.

Bucket: A new Account will not be generated if no match is found. The new Contact will be related to the Bucket Account.

Updated 6 months ago

Matching


Creating and matching lead and contact records

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.