Field Mappings
How Attio attributes map to Quotient fields and how to customize them
Field mappings control how data moves between Attio and Quotient. When Attio sends a person record, Quotient needs to know which attribute becomes firstName, which becomes jobTitle, and where custom properties should land. Mappings make that explicit.
Quotient uses a two-phase approach: built-in logic handles critical fields (email addresses, record IDs, company associations, parsed address and revenue data), then configurable mappings, including defaults plus anything you add, fill in the rest.
Custom fields are commonly used in the CRM for business-specific attributes, for example which product SKUs a company uses, or what pricing plan a business is on. These fields are also highly relevant to marketing, and the Attio integration allows you to sync them bidirectionally to Quotient.
Default Mappings
When you connect Attio, Quotient creates default mappings automatically. These defaults are inbound (Attio → Quotient). You can change direction or add mappings on the Attio integration settings page under the Person, Company, and Deal tabs.
People (Attio → Quotient)
| Attio Attribute | Quotient Field | Notes |
|---|---|---|
| email_addresses | emailAddress | Built-in; primary email used for matching |
| name | firstName, lastName | Default mapping; parsed from Attio name components |
| job_title | jobTitle | Default mapping |
| avatar_url | avatarUrl | Default mapping |
| phone_numbers | mainPhoneNumber | Default mapping; primary number |
| linkedin, twitter, instagram | linkedinUrl, twitterUrl, instagramUrl | Default mappings |
| company | companyId (association) | Built-in; links person to synced company |
Quotient also sets source to ATTIO and initializes email subscription status for new imports. Secondary email addresses and phone numbers from Attio are stored automatically without a separate mapping.
Companies (Attio → Quotient)
| Attio Attribute | Quotient Field | Notes |
|---|---|---|
| name | name | Default mapping |
| description | description | Default mapping |
| domains | domain | Default mapping |
| logo_url | logoUrl | Default mapping |
| facebook, instagram, twitter, linkedin, angellist | socialLink* | Default mappings |
| primary_location | address1, city, regionCode, zip, country | Built-in; parsed into address fields |
| categories, employee_range, estimated_arr_usd | industries, totalEmployees, revenue | Built-in; parsed from Attio structured values |
Deals (Attio → Quotient)
| Attio Attribute | Quotient Field | Notes |
|---|---|---|
| name | name | Default mapping |
| stage | status | Default mapping; uses stage title |
| value | amount, currency | Built-in |
| associated_company, associated_people | companyId, person associations | Built-in |
Sync Direction
Each mapping has a direction that controls when it applies:
- Inbound: Attio updates Quotient (the default for pre-configured mappings).
- Outbound: Quotient updates Attio when person, company, or deal data changes in Quotient.
- Bi-directional: Changes in either system can update the other, subject to the sync engine and webhook processing.
Outbound and bi-directional mappings are useful when Quotient is the system of record for a field, such as a lead score or marketing qualification flag you want reflected on the Attio person record. Flows that include a Send to CRM step can also push person updates to Attio using your outbound person mappings.
Adding Custom Mappings
To map an Attio custom attribute:
- Open Attio integration settings.
- Select the Person, Company, or Deal tab.
- Add a mapping between the Attio attribute and the Quotient field (standard or custom property).
- Choose the sync direction that matches how you want data to flow.
Quotient loads available Attio attributes from your workspace when you edit mappings, so custom attributes you add in Attio appear in the picker after sync.
Tips
- Start with defaults, then add mappings only for attributes you actually segment or personalize on. Unmapped Attio fields are ignored, which keeps Quotient uncluttered.
- Sync companies before relying on person-company links; the initial import already follows this order, but manual people-only syncs may temporarily show missing company associations until companies are present.
- If an Attio attribute type does not map cleanly to a Quotient field type, create a custom person or company property in Quotient first, then map the Attio attribute to it.
Next Steps
- Setup guide: Connect Attio and run your first sync.
- Audience segments: Build segments from synced CRM fields.
- Flows: Automate marketing and push updates back to Attio with Send to CRM.