Sign in
Track Customers

Merge duplicate people

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 primary profile must already exist in Customer.io for the merge operation to work. If the primary profile doesn't exist, your request won't do anything.

If you perform requests concurrently or in rapid succession, you could create a race condition where the primary profile doesn't exist yet. For example, if you identify a person and send a request to this endpoint immediately, the primary profile might not exist when we process your merge request.

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 automations.
  • Manual segments that the primary person did not already belong to.
  • Message delivery history.
  • Automation 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 automation 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 automations, segments, etc.
post/api/v1/merge_customers

Request body

Example request

{
  "primary": {
    "id": "42"
  },
  "secondary": {
    "id": "42"
  }
}

Response

A successful request returns an empty object response.

Changes

No recorded changes to this endpoint across all 1 revision of this API.