Enginy works with contacts and companies. In Salesforce, that data can live in three different objects.
In Enginy | In Salesforce |
Contact |
|
Company |
|
This configuration defines which object Enginy uses and how it looks for existing records before creating a new one.
Choosing Contact or Lead as the default object
Open the Salesforce configuration in Enginy and go to Sync Configuration. Under Default object when exporting, choose one of these options:
Contact: use it if your Salesforce contacts are usually associated with an Account.Lead: use it if you work with prospects before converting them into Contacts.
This choice applies whenever an action does not ask you to pick the object. It also determines whether Enginy imports Contacts or Leads, where it updates the Campaign Mapping fields, and which record Tasks are associated with.
In a manual export you will still be able to choose Contact or Lead for that operation, even if you set a different default.
Note: If you work with both objects, configure both Contact Identifier and Lead Identifier. Each identifier is only used when searching for records of its own type.
Configuring Contact Identifier and Lead Identifier
Contact Identifier tells Enginy how to look for an existing Contact. Lead Identifier does the same for Leads.
You can choose between:
First name + Last name + Company nameLinkedIn profile URL or First name + Last name + Company nameCustom mapping
The professional email can also be used to find an existing record. The full logic is explained in the article about Salesforce matching.
Contact Identifier configuration in Salesforce
If you choose the LinkedIn option, make sure you map the Enginy LinkedIn field to the corresponding Salesforce field in Field Mapping.
Configuring Company Identifier
Enginy companies are stored as Accounts in Salesforce. Under Company Identifier, you can choose:
Domain: looks for the Account through its Website field.Domain or company name: searches by domain or by the exact Account name.Custom mapping: lets you define your own field combinations.
Company Identifier configuration in Salesforce
The Check any domain (e.g. .es, .com, .org) option lets you search the same domain name with different extensions. It can be useful when a company uses several domains, but it also widens the search. Turn it on only if those variants really belong to the same company.
Configuring associations
In the General section you will find two options:
When exporting contacts, associate them with companies in Salesforce: when exporting a Contact, Enginy can also look for or export its company as an Account and link them.When exporting companies, associate them with contacts in Salesforce: when exporting a company, Enginy can also include its contacts and link them to the Account.
Salesforce stores a Contact's primary association in Contact.AccountId. This has two consequences:
The integration does not add several Accounts to the same Contact.
If Enginy associates the Contact with a different Account, the previous
AccountIdvalue is replaced.
A Lead works differently. Salesforce stores its company in the Company text field, not through AccountId. That is why exporting as a Lead does not create the same relationship that exists between Contact and Account.
Important: Salesforce has no Association Type selector. The integration always uses the primary Contact.AccountId relationship, so it never creates additional ones. If you have seen those options elsewhere, they belong to the HubSpot integration.
Which setup to choose
Choose Contact if you need every person linked to an Account in Salesforce.
Choose Lead if your prospects should enter as Leads first and be converted later following the Salesforce process.
Before saving, check that:
You have configured the identifier for the object you are going to use.
Company Identifiermatches the quality of the domains and names in your data.The LinkedIn field is mapped if you want to use it to identify records.
Associations are enabled only if you also want to export the related records.