> 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/getting-started/features/mobile-engagement-platform/analytics/reach.md).

# Reach

The *Reach* tab shows how the reach of your push campaigns evolves over time. At a glance, you can see the total number of installs opt-in to push notifications and the number of new opt-in/opt-out installs every day.

## Global analytics

<figure><img src="https://1464139620-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUIK868wiiK9XOVyETGZS%2Fuploads%2FLpYbvx1Bz0k06q8kFWNo%2Fimage.png?alt=media&amp;token=45bdf28f-60de-4299-a8f1-ed986c9b11fc" alt="reach global"><figcaption></figcaption></figure>

Gives you valuable information on the volume of new installs opt-in to push notifications everyday. You can choose a custom date range in the top right corner if you want to analyse a specific period of time.

* **Total tokens**: Total number of installs with a token.
* **Total opt-ins**: Number of installs with a token opt-in to push notifications.
* **New opt-ins**: Number of new opt-in installs.
* **Opt-outs**: Number of new opt-out installs.

## Detailed stats

<figure><img src="https://1464139620-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUIK868wiiK9XOVyETGZS%2Fuploads%2FZHjCQ6of4KbzYpMIq3Qx%2Fimage.png?alt=media&amp;token=1c068689-b9fe-4a62-b134-2645acd73a89" alt="detailed reach"><figcaption></figcaption></figure>

The second part of the Reach analytics shows the same stats in a table. You can sort columns in ascending or descending order by clicking on the column header. This is helpful to find your best performing days.

You can export all your stats by clicking **Download CSV**.


---

# 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/getting-started/features/mobile-engagement-platform/analytics/reach.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.