Before creating a Contact, Lead or Account, Enginy tries to find an existing record. If it finds one, it uses that record for the export. If it finds no match, it tries to create a new one.
When an Enginy record is already linked to a Salesforce ID, Enginy uses that link. The rules in this article mainly apply to records that do not have a stored ID yet.
Enginy only searches within the target object. If you export as a Contact, it does not look for the same prospect among Leads, and vice versa.
How it searches for a Contact
With the standard identifiers, the professional email acts as a search alternative.
First name + Last name + Company name
Enginy can find the Contact if one of these conditions is met:
Contact.Emailmatches the professional email.First name, last name and company all match.
For the second option, Enginy compares the company with Account.Name or with the Account it has already identified for that contact.
If the first name, last name or company is missing, that combination is not used. The email can still find the record if it is available.
LinkedIn profile URL or First name + Last name + Company name
Enginy searches by any of these:
Professional email.
LinkedIn URL.
First name, last name and company.
When comparing LinkedIn, Enginy accounts for common variants of the same URL, such as http, https, and the presence or absence of a trailing slash.
To use this option, the Enginy LinkedIn field must be connected to the matching Salesforce field in Field Mapping.
Custom mapping
Custom mapping lets you decide which combinations should count as a match.
Within a group, every field must match. Across groups, one match is enough.
Custom Mapping for Contact
For example:
Group 1: Professional email + Company name
Group 2: LinkedIn profile URL
Enginy accepts the Contact if email and company match, or if LinkedIn matches.
If the Enginy record is missing one of the values in a group, that group is skipped. In the example above, group 1 would not be evaluated if Company name is missing.
The email stops working as an independent alternative once you include it inside a custom group. In that case it must satisfy the other conditions in that group too.
How it searches for a Lead
Lead matching follows the same general logic:
The professional email can find a Lead through
Lead.Email.The name option compares first name, last name and the
Lead.Companyfield.The LinkedIn option also accounts for URL variants.
Custom mappingsupports groups withANDconditions andORalternatives.
The main difference is the company. A Lead uses the Company text field; it is not associated with an Account through AccountId.
Configure Lead Identifier even if you have already configured Contact Identifier. They are independent rules.
How it searches for an Account
Enginy companies are matched against the Account object.
Domain
Enginy compares the company domain or website with Account.Website. The search accounts for common variants such as the protocol, www and language subdomains.
Domain or company name
Enginy uses two alternatives:
A domain match on
Account.Website.An exact match on
Account.Name.
Only one of them needs to be met.
Custom mapping
You can create custom field groups for Account. As with Contact and Lead, every field in a group must match, and different groups work as alternatives.
Custom Mapping for Account
If a value required by a group is missing, Enginy does not use that group to search.
What Check any domain does
Check any domain (e.g. .es, .com, .org) widens the search to try different extensions of the same domain.
For example, it can help match company.es with an Account whose Website is company.com.
This search can also connect different companies that share a similar root. Leave it off if the full domain identifies each company correctly.
What happens when there are several matches
If a search returns several records, Enginy sorts them by LastActivityDate and uses the most recently active one first.
Enginy does not show a picker to choose between candidates during the export. That is why it is worth using fields that identify each record precisely enough.
To reduce incorrect matches:
Map the LinkedIn field before using it as an identifier.
Include the company when a person's name may repeat.
Use custom groups built on stable data.
Avoid
Check any domainif you work with companies that have similar names or domains.Review existing duplicates in Salesforce before running a large export.
Note: Enginy's matching rules are independent of Salesforce Duplicate Rules. Letting Salesforce save a record despite a duplicate warning does not change how Enginy runs these searches.