talkvalue path person merge consolidates two duplicate person records into one. The source person’s emails, phones, channels, events, and activity history move into the target, and TalkValue retires the source ID. Prefer this over delete whenever you spot a duplicate. Attribution and event history from both records remain attached to the target.
Synopsis
Arguments
| Argument | Type | Description |
|---|---|---|
<sourceId> | integer | Person ID to merge from. After the call this ID stops resolving via person get. |
<targetId> | integer | Person ID to merge into. This record survives and absorbs the source. |
Options
| Flag | Type | Description |
|---|---|---|
--confirm | flag | Required. The CLI exits with a usage error if you omit this flag. |
Examples
1. Merge two duplicates
199 into person 142. The output is the target’s updated record, same shape as person get, so you can verify the merged email, phone, and channel set.
2. Inspect both before merging
3. Roll back a mistake
To reverse a merge, useperson merge-undo within the retention window:
mergeOperations[0].id on the target’s detail record) or in the dashboard’s activity log.
Response
person get 199 after the merge return 404.
See also
person get. Verify source and target before merging.person merge-undo. Reverse a merge within the retention window.person activity.MERGEDentries record the source → target link.person delete. Prefer merge over delete for duplicates.- People. The dashboard surface for the same operation.
