> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/android/set-up-luciq-for-android/identify-users.md).

# Identify users

Bind every Android bug and crash report to the user who sent it. Covers user identification and the extra data you can attach for debugging.

With each crash or bug report sent from your application, we send all needed information to your dashboard to help you debug the problem easily and communicate with the user reporting the problem.

1. [**User Identification**](/android/set-up-luciq-for-android/identify-users/user-identification.md)\
   This section discusses how to bind each report to the identity of the user reporting the problem. You also have the flexibility to add some extra data about the device as well as the user.
2. [**Setting Custom Data**](https://docs.luciq.ai/android/set-up-luciq-for-android/identify-users/setting-custom-data)\
   Set custom attributes, log specific user events, and tag your reports. All of these are explained in this section.


---

# 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.luciq.ai/android/set-up-luciq-for-android/identify-users.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.