gtmaistandardperson
View siteSYSTEM READY [v2.4.0]
Person
SCHEMA_PERSONCorev1.0.0An individual associated with a Company or Account, potentially across multiple roles or companies over time.
Identity Key
verified primary_email > linkedin_profile_url > full_name + company + titleHow instances of this object are resolved and deduplicated when the same entity is seen across multiple vendors.
Schema Fields
| Property | Type | Constraint |
|---|---|---|
| person_id | String | Required |
| primary_email | Best identity key when available | |
| email_status | Enum | Verified, likely, unknown, invalid |
| full_name | String | Required |
| linkedin_profile_url | URL | Optional |
| current_company_id | String | Link to Company |
| current_account_id | String | Link to Account |
| title | String | Raw title |
| seniority | Enum | C-level, VP, director, manager, IC, founder |
| department | Enum | Sales, marketing, engineering, etc. |
| buying_role | Enum | Decision maker, influencer, evaluator, practitioner, blocker |
| source_systems | Array | Required |
| confidence_score | Number | 0–1 normalized |
Merge Rules
- 01Resolve in priority order: verified primary_email, then normalized linkedin_profile_url, then full_name + current_company_id + title at lower confidence.
- 02Never hard-merge on name alone.
Vendor Mappings
| Provider | Field ID |
|---|---|
| Apollo.io | person.id |
| HubSpot | contact.email |
| Salesforce | Contact.Id |
| member.urn | |
| Clay | person.email |