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

# Overview

> See visitors, page views, sessions, bounce rate, session duration and revenue, with breakdowns by page, source, country, device and event.

The **Overview** page is the home of each project. It shows your key metrics for the selected date range and where your traffic comes from.

## Key metrics

| Metric | Definition |
| - | - |
| **Visitors** | Unique visitors (`anonymous_id`) in the period |
| **Page views** | Total page views |
| **Sessions** | Total sessions. A session ends after 30 minutes without events. |
| **Session duration** | Average active time per session |
| **Bounce rate** | Share of sessions with one page view. Lower is better. |
| **Revenue** | Sum of the numeric `revenue` property on custom events from the website, the game and your server, once per event, plus the payments of connected providers (Stripe, Paddle, itch.io) net of refunds. All amounts are converted to one currency (USD by default) with the ECB rate of the day. A sale is counted once: see [Revenue](https://docs.manalens.dev/features/revenue.md#one-sale-is-counted-once). With a filter, only your own events count |

Click a metric to show it on the trend chart. Each metric shows the change against the previous period of the same length. Turn on **Compare** to overlay the previous period on the chart.

For Visitors, Sessions and Revenue, you can break down the chart by an acquisition or demographic field, such as channel, referrer, UTM source, device or country.

> [!TIP]
>
> To report revenue on the Overview, send it on a custom event: `track('purchase', { revenue: 49 })`. Revenue by source uses the acquisition on the revenue event. A game, app or server event has no acquisition of its own, so it uses the first website visit of the same player at or before the purchase, at most 90 days earlier. A game purchase by a player who came from your newsletter shows under the newsletter, not **Direct**. A purchase with no website visit before it shows under **Direct**. The **Source** label is the same as on the Attribution report: the UTM source, else the ad network of an ad click, else `ref:<code>` for a referral code, else the referrer, else **Direct**. Revenue is converted to one currency, USD by default (see [revenue](https://docs.manalens.dev/features/revenue.md)).

## Breakdowns

| Card | Tabs |
| - | - |
| **Pages** | Pages, Entries, Exits, Origins |
| **Acquisition** | Channels, Referrers, UTM, Referrals, Ads |
| **Countries** | Visitors by country |
| **Technology** | Devices, OS, Browsers |
| **Events** | Custom events, All events |

Use the unit menu on a card to switch its values. Pages show Visitors or Views (Sessions for Entries and Exits). Acquisition, Countries and Technology show Visitors, Sessions or Revenue. Sessions are the sessions of the Sessions tile: a session has the source of its first page view (a game session: of its first event). A filter selects the visitors with a matching event, then all sessions of those visitors count, so a card can list a source that the filter does not name.

To download a card's list, open the card menu (⋮) and click **Export**. The CSV has the active tab and unit, in the selected date range and with your filters. The Countries card also has a country code column. The file name gives the project, list, unit and period.

To narrow the whole page, add a [filter or segment](https://docs.manalens.dev/features/filters-segments.md).

## Live visitors

When visitors are active, a live visitor count appears near the page title. Click it to open [Live view](https://docs.manalens.dev/features/live-view.md).

## Related

* [Activity](https://docs.manalens.dev/features/activity.md) for the event stream behind these numbers.
* [Attribution](https://docs.manalens.dev/attribution/overview.md) for how channels are classified.
* [Dashboards](https://docs.manalens.dev/features/dashboards.md) to save these metrics as charts.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.