> For the complete documentation index, see [llms.txt](https://documentation.freshpaint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.freshpaint.io/audiences/identity/user-profiles.md).

# User Profiles

## User Profiles

User Profiles surface a comprehensive, person-centric view of patients built on top of Freshpaint's Identity Graph. This is the central hub for searching, viewing, and understanding individual user identities in Freshpaint.

This page helps you:

* Search across multiple identifiers (email, phone, userId, anonymousId, device ID, traits)
* Visualize the Identity Graph — all identifiers ever associated with a patient
* Filter the event timeline to debug specific data flows

### User Profile Directory

The main User Profiles landing page displays a searchable list of all visitors. The directory includes:

* **Search bar** — Find patients by email, phone, userId, anonymousId, device ID, or custom traits
* **Filter controls** — Filter by last seen date, identifier types, event sources, and properties
* **Columns** — User, Freshpaint ID, Email, Last seen, Identifiers count
* **Column customization (⊞)** — Show or hide columns and adjust the display

<figure><img src="/files/HDwYcSZEhVdbkHPkKuw8" alt="Freshpaint User Profiles Directory View" height="376.5159821226287" width="586.580226904376"><figcaption></figcaption></figure>

### User Profile Details

Click any row in the directory to open the detailed profile view. The profile page displays:

* **User header** — Avatar, primary name or ID, email and phone identifiers (if available), and the Last Seen timestamp
* **Identifiers sidebar** — All known identifiers grouped by type
* **Event timeline** — Chronological list of all visitor activity

<figure><img src="/files/IYpBV1YstRVyiO0o52xN" alt="User Profile Example" height="463" width="373"><figcaption></figcaption></figure>

### Identifier Types

| Type                 | Example                 | What It Represents                                   |
| -------------------- | ----------------------- | ---------------------------------------------------- |
| Email                | <support@freshpaint.io> | User's email address (masked)                        |
| Phone                | 15555555                | User's phone number (masked)                         |
| External ID          | —                       | Externally defined unique identifier                 |
| Device ID            | 19e18cb2a8d21f9…        | Freshpaint-assigned unique identifier                |
| Impression Cookie ID | 19e18cb2ba0-04f84…      | Browser cookie tracking ad impressions               |
| IP Address           | 192.168.1.1             | User's public IP address collected from session data |

### What's Next?

* [**Identity Resolution**](/audiences/identity/identity-resolution.md) — Learn how Freshpaint links identifiers across sessions and devices
* [**Cross-Device Attribution**](/audiences/identity/cross-device-attribution.md) — Understand how resolved identities power cross-device attribution


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.freshpaint.io/audiences/identity/user-profiles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
