POST /api/v1/merge_customers
Merge two customer profiles together. The payload contains primary and secondary profile objects. The primary profile remains after the merge and the secondary is deleted. This operation is not reversible.
The following information is merged into the primary profile from the secondary profile:
- Attributes that are not set, or are empty, on the primary.
- The most recent 30-days of event history. Events merged from the secondary person cannot trigger campaigns.
- Manual segments that the primary person did not already belong to.
- Message delivery history.
- Campaign journeys that the primary person has not entered. If the secondary person has started a journey that the primary person has not, the primary person continues on that campaign journey after the merge. If the secondary person has completed journeys that the primary person has not, the primary person gains these historical journeys after the merge. This may be important for determining entry (or re-entry) criteria for subsequent campaigns, segments, etc.
Servers
- https://track.customer.io
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
primary |
Yes |
The person that you want to remain after the merge, identified by one of If email is disabled as an identifier in your workspace settings, then you must reference people by |
|
secondary |
Yes |
The person that you want to delete after the merge, identified by one of If email is disabled as an identifier in your workspace settings, then you must reference people by |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.