Matching and Field Mapping serve different purposes:
Matching decides whether a Record already exists.
Field Mapping decides which values are written.
Note: A correct Field Mapping does not prevent duplicates if matching has no LinkedIn, email or domain to work with.
Opening the configuration
Open Integrations.
Find Attio and click Configure.
Review Sync configuration.
Open Field mapping.
Save your changes with Save Changes.
Matching People
Attio's standard matching follows this order:
It looks for a match by LinkedIn.
If it finds none, it searches by email.
If it still finds no match, it creates a Person record.
Even though the selector may show a Names-based option, do not use the name as a unique identifier. The current standard flow does not match by name.
Important: For standard LinkedIn matching, use Attio's native LinkedIn Attribute. If you work with a different custom Attribute, validate the matching with a single contact.
Custom matching for People
Use Custom mapping when you need other identifiers.
Fields within one Condition are combined with AND.
Several Conditions work as alternatives.
Each chosen field needs a valid mapping.
Choose stable values that are unique enough. Country, industry or job title do not usually work on their own.
Matching Companies
Domain
Looks for a Company with the same domain. It is the most reliable option when the value is available.
Domain or Company Name
Searches by domain first. If it finds no match, it tries to locate the Company by name.
Names can be ambiguous. Use this option only when some companies have no domain.
Any domain extension
The option that includes any extension lets you compare the same base domain with different endings, such as .com or .es. Use it carefully, because it can widen the search too much.
Custom matching for Companies
You can create Conditions with domain, name, LinkedIn or other mapped fields.
If Attio returns several matches
For People, Enginy uses the most recently updated Record. For Companies, an exact domain match takes priority, and then the most recent Record is used.
If several matches come up often, clean up the duplicates in Attio and review the identifiers.
Configuring Field Mapping
Open the Contacts tab for People or Companies for Companies.
Click Add field.
Choose the Enginy field.
Choose the Attio Attribute.
Select the rule for existing values.
Save with Save Changes.
Available sections
Field Mapping connects standard fields.
Custom fields manages additional data.
Fixed value fields always sends the same value.
Manual export fields asks for a value during a manual export.
Engagement fields uses values related to compatible activity.
Rules for existing values
Enginy overwrites Attio
Enginy can replace the existing value during an update. Use it when Enginy should be the source of truth for that field.
Sync with Attio
Enginy keeps the value Attio already has and can fill the Attribute in if it is empty.
This name does not mean Attio sends the value back to Enginy. It also does not turn on bi-sync.
Type compatibility
Connect equivalent types wherever possible:
Value | Recommended Attribute | Watch out for |
Text | text | Check limits and required fields |
Number | number | Do not send text into a numeric Attribute |
The standard email-address | Use a valid email format | |
Phone | The standard phone-number | Check the prefix and the format |
Domain | The standard domain | Send the domain without a web path |
Select or multiselect | The equivalent type | The options must exist and the format may need testing |
Test select, multiselect, record-reference, actor-reference, location, interaction and any complex custom Attribute with a single Record.
List Attributes
A List's Attributes are configured separately, after choosing a List in the export modal. Those values belong to the Entry, not to the Person or Company record.
Validating before a large export
Export a Person that already exists.
Check the matching and the updated values.
Export a new Person.
Repeat the test with a Company.
Review Activity and the Attio Record before scaling up the volume.
Which records Enginy may create
Two settings decide whether Enginy creates a record in Attio that it could not match. They are the most common reason a person "never arrived".
The creation toggles
In Sync configuration you will find two switches, both on by default:
Create contacts in Attio when no match is foundCreate companies in Attio when no match is found
Turn one off and Enginy updates what it matches and skips the rest. Nothing new is created for that entity.
Required fields for creation
Each row in the Field mapping table has a checkbox in the Required column. Tick it and a record missing that field is skipped instead of created.
Good to know: This never blocks an update. A record that already exists in Attio keeps being updated as usual, because the rule only gates creation.
Three things worth knowing before you use it:
One configuration covers every CRM. The check runs on the Enginy values, before they are translated into Attio attribute names. If you connect a different CRM later, the same rules apply.
0andfalsecount as filled in. A field is only missing when it is empty, contains nothing but spaces, or is an empty list.Turning creation off does not erase your selection. The list stops applying while the toggle is off, and comes back untouched when you turn it on again.
The checkbox is disabled while creation is off for that entity. Enable the matching toggle in Sync configuration first.
The rule that always applies
Always: A contact with no email, no phone, no LinkedIn URL and no CRM ID cannot be exported at all, whatever you configure here. Enginy would have no way to match or identify it in Attio.
Where you see the effect
Export to CRM checks your selection before running and tells you how many records are missing required fields. If every record in the selection would be skipped, it blocks the export with None of these contacts will be created in your CRM.
These rules also apply to automatic campaign syncs, not just manual exports.