> 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/ai-workbench-qore/console/app-builder/analytics.md).

# Analytics

Track published app visitors, traffic trends, and audience characteristics.

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](/ai-workbench-qore/start-here/control-center.md).

<figure><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-3e578a7e841b7732e8ce6fa39ba08575c5689a75%2Fqore_app-builder_studio-import-an-existing-app-more-analytics_rounded_shadow.png?alt=media" 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 Observe](/ai-workbench-qore/control-center/observe.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="/pages/807cab861e090edd0ce825909db3db1b28f73799" %}
[Control Center](/ai-workbench-qore/start-here/control-center.md)
{% endcontent-ref %}

{% content-ref url="/pages/4023fee41d519b1fbe13cbf03c9027c75b45de1a" %}
[Observe](/ai-workbench-qore/control-center/observe.md)
{% endcontent-ref %}

***

{% columns %}
{% column width="83.33333333333334%" %}

<p align="right"><em>Maintained by</em> <mark style="color:green;">Abhishek Paul</mark><br><code>AI-assisted, human-approved</code></p>
{% endcolumn %}

{% column width="16.666666666666664%" %}

<div align="left"><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-d034645b4f8f8ee661985f5306b60ded3289653c%2Fmaintainer-abhishek-paul.png?alt=media" alt="" width="60"></div>
{% endcolumn %}
{% endcolumns %}


---

# 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://docs.uptiq.ai/ai-workbench-qore/console/app-builder/analytics.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.