> ## Documentation Index
> Fetch the complete documentation index at: https://www.text.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Customer identities

> Learn how Text connects customer records from different browsers, devices, and channels and how to retrieve their combined data.

Text can create separate identity records for one customer — this happens when someone contacts an organization from another browser, device, or channel. A `customer_id` identifies one customer record, not necessarily the complete customer.

## Customer clusters

The Customer Data Platform associates identities that belong to the same customer. Together, they form a *customer cluster*:

```text theme={null}
Customer cluster
├── Browser identity
├── Mobile identity
└── Messaging-channel identity
```

One record becomes the master record for the cluster and represents its combined customer data. The other records remain child identities and retain their own `customer_id` values and source data. Merging identities does not replace their customer IDs with the master record's ID.

| Field | Question it answers | How it behaves |
| - | - | - |
| `id` or `customer_id` | Which individual customer record is this? | It identifies one customer identity and does not change when the identity joins a cluster. |
| `cluster_id` | Which cluster does this customer record belong to? | It is present on every customer record. All records in a cluster have the same `cluster_id`. For an unmerged record, it has the same value as `customer_id`. |
| `monitoring.master_id` | Which master record does `monitoring` link to? | This field appears inside `monitoring`. It contains the master record's ID after a merge, is empty before a merge, and is unavailable when `monitoring` is `null`. |
| `is_master` | Is this the master record for the cluster? | It is `true` for the master record. |
| `child_sources` | Which sources contain activity for this customer identity? | It can contain `monitoring`, `helpdesk`, or `api`. An empty array means that the identity has no visits, chats, or tickets and was not created with `create_customers`. It is omitted for a master record. |

If customer record `B` is merged into master record `A`, its `customer_id` remains `B`, while `cluster_id` and `monitoring.master_id` contain `A`.

## Customer IDs in API responses

Different APIs can return different IDs from the same cluster. For example, a chat can contain the customer record associated with that conversation, while a customer list can return the cluster's master identity.

## Retrieve customer data

Choose the method based on the data you need:

* Use [`get_customer`](https://www.text.com/docs/api/customer-data-platform/customers/get-customer) for the data stored on one identity.
* Use [`get_merged_customer`](https://www.text.com/docs/api/customer-data-platform/customers/get-merged-customer) for data combined across a cluster. You can pass any customer ID from the cluster and receive the same merged view.
* Use [`get_merged_customer_chats`](https://www.text.com/docs/api/customer-data-platform/customers/get-merged-customer-chat-ids) or [`get_merged_customer_tickets`](https://www.text.com/docs/api/customer-data-platform/customers/get-merged-customer-ticket-ids) for activity associated with every identity in the cluster.

> [!TIP]
>
> If an email address, phone number, chat, or ticket appears to be missing from
> one customer record, pass its `customer_id` to
> [`get_merged_customer`](https://www.text.com/docs/api/customer-data-platform/customers/get-merged-customer)
> before concluding that the data is unavailable.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.