> 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/analytics/how-to-track-app-uninstalls-on-ios-and-android-outside-of-batch.md).
# How to track app uninstalls on iOS and Android? (outside of Batch)
You don’t know where to track the uninstall stat of your application? I’ll tell you where you can find this indicator.
At Batch, we do recommend using tools such as Google play developer for Android or iTunes Connect for iOS that can give you relevant information about uninstalls.
## Google Play Console
If Batch does not know the information on the uninstallation of your application, Google knows it.
All you have to do is connect to your Google Play Console and find on the statistics tab the number of uninstalls. You can also check on the dashboard the number of installs and uninstalls for the last week, month, or year.
## iTunes Connect
iTunes Connect does not give you the exact number of uninstallation. But it can give you another information, which is "retention". Retention measures the usage of your app over time.
---
# 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/analytics/how-to-track-app-uninstalls-on-ios-and-android-outside-of-batch.md?ask=&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.
