> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/app-builder/analytics.md).

# Analytics

Analytics shows you who is using a published app and where they come from. Open it from the app workspace's **More** menu → **Analytics**.

**In-app and unified app analytics:** In-app analytics is available alongside a unified view in the [Control Center](/start-here/control-center.md).

<figure><img src="/files/uuAHLAx5zvExHGL0L6BV" alt="The Analytics screen, showing unique visitors trend, top browsers, devices, countries, and pages"><figcaption><p>Analytics for a published app.</p></figcaption></figure>

## What it shows

Analytics reports **Unique Visitors** as a trend over a period you choose — for example the last 30 days — so you can see how traffic moves day to day. Alongside the trend, it breaks visitors down by:

* **Top browsers** — which browsers your visitors used.
* **Top devices** — desktop, mobile, and so on.
* **Top countries** — where visitors came from.
* **Top pages** — which pages drew the most visits.

{% hint style="info" %}
Analytics covers the app's **published** URLs, so a version you haven't published yet won't appear here. The account-wide view across all apps lives in [Control Center's Observability](/governance/observability.md).
{% endhint %}

## Why this matters

* Analytics tells you whether a published app is actually being used, and by whom.
* It's scoped to one app; publish a version to start collecting data for it.

## Related

{% content-ref url="/spaces/0qmgQjJ5aArDTj2ACFHG/pages/807cab861e090edd0ce825909db3db1b28f73799" %}
[Control Center](/start-here/control-center.md)
{% endcontent-ref %}

{% content-ref url="/spaces/0qmgQjJ5aArDTj2ACFHG/pages/4023fee41d519b1fbe13cbf03c9027c75b45de1a" %}
[Observability](/governance/observability.md)
{% endcontent-ref %}


---

# 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.uptiq.ai/app-builder/analytics.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.