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

# User Profile

## Viewing a User Profile

You can view an individual user's profile by searching directly with a User Identifier.

{% hint style="info" %}
**Searchable Identifiers**

Hackle ID, User ID, Device ID, Phone Number
{% endhint %}

![](https://143363954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyAVlNQhS253reum0Ce94%2Fuploads%2Fgit-blob-140ab02660fd71d50d7225d17ef6e0b90fbef28f%2F72a0e64486835cb59158ff0571e173a51a9e66ce_70339f95de04cb2b.png?alt=media)

### Profile Details

On the user profile screen, you can view information about the user's identifiers, as well as `Hackle Auto-collected Properties`, `User Properties`, `Push Messages`, and other information that Hackle automatically collects.

![](https://143363954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyAVlNQhS253reum0Ce94%2Fuploads%2Fgit-blob-a3eb45b446f483421c8d77997c9bf662fbfb3cda%2F02abae2b4987daed2fcf472e3211021f6608ba1c_3afb2f020cf74396.png?alt=media)

### Activity Timeline

You can view the user's recent activity timeline. You can see at a glance not only the user's activity events but also experiment and Feature Flag distribution history.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hackle.io/en/user-view/user-profile.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
