> For the complete documentation index, see [llms.txt](https://docs.messageflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.messageflow.com/mobile-push/push-api/dashboard.md).

# Dashboard

The **Mobile Push API Dashboard** is displayed as shown below and provides a summary of recent sends within the selected time range.

<figure><img src="/files/OzImfvW44msypIn0pb0b" alt=""><figcaption></figcaption></figure>

* **Select range** – the date range that allows you to analyze mobile push campaigns during the chosen period.
* **Select applications** – choose the applications to analyze. When you click **Select applications**, a pop-up window appears where you can use checkboxes to select the apps linked to your account that you want to include in the summary. You can also type their names to search for them.
* **Message statuses** – in the dashboard view, you have access to a summary of campaign statuses:
  * **Injected** – messages accepted by the MessageFlow panel.
  * **OK** – messages successfully delivered to the recipient.
  * **Open** – messages opened by recipients.
  * **Track** – messages tracked (e.g., due to link clicks).<br>

    <figure><img src="/files/6XLOgcXnpW8rTNd49hNx" alt=""><figcaption></figcaption></figure>
* **Chart** – shows a timeline distribution of messages. Using checkboxes, you can select the statuses: *Injected*, *OK*, *Open*, and *Track* to see when the campaigns were run, how many messages were accepted in the panel, and how many were successfully delivered to recipients.<br>

  <figure><img src="/files/rzyOB3AJIuXDYBIq3REk" alt=""><figcaption></figcaption></figure>
* **Applications** – this section displays connected apps and the list of devices.<br>

  <figure><img src="/files/Ea02o9AO4MB4uXW0wLzC" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.messageflow.com/mobile-push/push-api/dashboard.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.