> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/guides-and-best-practices/profiles/how-to-see-the-data-attached-to-your-install-or-custom-id.md).

# How to see the data attached to your Install or Custom ID?

The debug tool allows you to see all the native and custom data Batch has on your most recent installs.

## What is the debug tool? <a href="#what-is-the-debug-tool" id="what-is-the-debug-tool"></a>

The [debug tool](https://doc.batch.com/getting-started/features/customer-engagement-platform/settings/debug) can display in near real-time all the data received from the SDK for your installation or your custom user ID.

{% hint style="info" %}
This is handy to:

* Make sure a Custom ID is correctly attached to your installation.
* Test your integration each time you track a new attribute or event with the SDK.
  {% endhint %}

## Using the debug tool <a href="#using-the-debug-tool" id="using-the-debug-tool"></a>

First, go to **Settings > Debug**.

You can use the debug tool to find your most recent install, based on:

* An **Installation ID,** which is an anonymous ID generated by Batch.
* A **Custom ID**, should be the unique user ID you are sending to Batch from the SDK (more information here: ([iOS](https://doc.batch.com/developer/sdk/ios/profile-data/custom-user-id) / [Android](https://doc.batch.com/developer/sdk/android/profile-data/custom-user-id) / [web](https://doc.batch.com/developer/sdk/web/profile-data/custom-user-id))

<figure><img src="https://509463063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiAYaWDWqtFZeXxyg67F%2Fuploads%2FQgLo9GDLy9Z4JU6dXfLv%2FCleanShot%202026-10-19%20at%2016.16.39%402x.png?alt=media&amp;token=3d6f904e-aeb3-40a8-96fb-15358e997c1c" alt=""><figcaption></figcaption></figure>

The debug tool shows all the native and custom data we have on your most recent installs:

* **Custom ID**: This field shouldn't be empty if you are sending it to Batch and are logged into the app. Make sure that ID disappears after your log out.
* **Attributes/events**: Your attributes and events will appear in the right panel of the debug tool. Make sure important attributes are sent to Batch in the right format (e.g. date, string, boolean, etc) and at the right moment (e.g. on the first start of the app and/or when a value changes etc). Events will appear as soon as you perform the tracked action in the app.
* **Last location**: In case you share with Batch the most recent location of your user, you should see a latitude/longitude in the right panel of the debug tool.

{% hint style="info" %}
Data sent server-side through the [Profile API](https://doc.batch.com/developer/api/cep/profiles) (attributes and events) won’t appear in the debug tool, which only shows data received by the installation. To see all the data attached to a user, use the Profile view: [How to find a user’s profile on the dashboard](https://doc.batch.com/guides-and-best-practices/profiles/how-to-find-a-users-profile-on-the-dashboard).
{% endhint %}


---

# 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://doc.batch.com/guides-and-best-practices/profiles/how-to-see-the-data-attached-to-your-install-or-custom-id.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.