> ## Documentation Index
> Fetch the complete documentation index at: https://help.usetapp.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Use advanced Analytics

> Open domain analytics, choose a time frame and move between revenue, menu and operational insights.

Use advanced Analytics when the Overview cards are not enough. The hub separates reporting into domain pages for revenue, menu, guests, bookings, demand and activity.

## Who can do this?

The analytics API enforces **Owner or Manager** access. Staff is not authorized even if a route or Overview link is visible in the interface.

## Where to do it

From **Overview**, follow the Analytics entry point. The Analytics hub lists the available domains for the selected shop.

## Explore Analytics

1. Confirm the active shop before opening a domain.
2. Choose a domain such as Revenue, Menu, Guests, Bookings, Demand or Activity.
3. Use the segmented time-frame control where the page provides it.
4. Read the page's KPI cards, charts and breakdown sections together.
5. Use information tooltips and metric-quality notes when shown; these explain a metric's scope or data limitations.
6. Return to the hub to switch domains rather than treating one page as the complete business view.

Different analytics pages deliberately expose different controls. A category selector on a menu report, for example, does not filter an unrelated revenue report.

The hub routes separately to Revenue, Menu, Guests, Bookings, Demand and Activity. Shared shop and period context does not make their definitions interchangeable. Use the domain's tooltips and quality notes before comparing a specialized metric with a headline Overview card.

## Data and access notes

An empty state can mean the selected shop and period have no qualifying records. An access error for Staff is not an empty period; it is an authorization boundary. The API, not the sidebar, is the source of truth.

## Platform notes

Analytics is currently described from management web. Orders can originate in management POS, management mobile or guest ordering, but reporting is read here. Values use the active shop's locale and currency.

## Market notes

The same analytics domains exist for GB and Germany, while displayed currency, dates and shop operating context are localized. Compare shops only with matching periods and metric definitions; switching language does not merge market data.

## Troubleshooting

If a report is empty, confirm the active shop, reporting period and domain-specific filters. If Staff receives an access error, ask an Owner or Manager to open the report; reloading cannot bypass the API permission boundary.

## Related guides

* [Understand the Overview dashboard](/en/overview/understand-overview-dashboard)
* [Analytics access for Staff](/en/overview/analytics-access-for-staff)