ContactMerge
The answer of a merge (1.61.0): contact is the target after the merge, without its profile; the target keeps its id; identities and external ids are unioned (two ids of one system are 409 contact_merge_conflict); attributes keep the target value and take the source value where the target has none; a declared language or zone beats a derived one; memory consent takes the more restrictive state. Consent records do not move, because they belong to addresses.
An object with 4 fields.
Fields
| Field | Type | Required | Description |
|---|---|---|---|
contact | Contact | yes | |
merged_at | Timestamp | yes | |
object | "contact_merge" | yes | |
source_contact_id | ContactId | yes | Now a merged tombstone. |
Used by
The operations whose parameters, request body or responses name this shape directly.