gtmaistandardengagement
View siteSYSTEM READY [v2.4.0]
Engagement
SCHEMA_ENGAGEMENTCorev1.0.0A touchpoint between the GTM system/team and a Person, Account, or Company.
Identity Key
source_system + source_record_idHow instances of this object are resolved and deduplicated when the same entity is seen across multiple vendors.
Schema Fields
| Property | Type | Constraint |
|---|---|---|
| engagement_id | String | Required |
| engagement_type | Enum | Required |
| direction | Enum | inbound, outbound, internal, system |
| channel | Enum | email, phone, LinkedIn, web, paid_search, paid_social, event, partner |
| source_system | String | Required |
| source_record_id | String | Required |
| company_id | String | Link at the appropriate level |
| account_id | String | Link at the appropriate level |
| person_id | String | Link at the appropriate level |
| status | Enum | sent, delivered, opened, clicked, replied, bounced, completed, no_show |
| occurred_at | Timestamp | Required |
| sentiment | Enum | positive, neutral, negative, unknown |
Merge Rules
- 01Unique on (source_system, source_record_id).
- 02Preserve channel-specific events; aggregate into scores and journey summaries, but keep raw touchpoints traceable.
- 03Federated: resolved at query time from the vendor's MCP, never persisted in D1.
Vendor Mappings
| Provider | Field ID |
|---|---|
| Salesloft | activity.id |
| Outreach | mailing.id |
| HubSpot | engagement.id |
| Gong | call.id |
| Apollo.io | email.id |