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

{% hint style="info" %}
This guide is specific to Batch's Mobile Engagement Platform (More on the [difference between Batch's CEP and MEP](/getting-started/other/faq/what-are-the-differences-between-batch-customer-engagement-platform-and-mobile-engagement-platform.md)).
{% endhint %}

## 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/dashboard/settings/app-settings#integration-debug-tool) can display in near real-time all the data received from the SDK or the [Custom Data API](https://batch.com/doc/api/custom-data-api/set-update.html) for your installation or your custom user ID.

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

* Make sure a Custom User ID is correctly attached to your installation.
* Test your integration each time you track a new attribute or event with the SDK.
* See if the data you sent using the Custom Data API is attached to your installation.
  {% 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 User 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="/files/HhXC87QwWtQ876u27sxi" alt=""><figcaption></figcaption></figure>

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

* **Custom User 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.&#x20;
* **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" %}
Event sent by the [Trigger event API](https://doc.batch.com/developer/api/mep/trigger-events-api/track-events) won't appear on this page.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://doc.batch.com/guides-and-best-practices/profiles/how-to-see-the-data-attached-to-your-install-or-custom-user-id.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.