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

# Statistics

The Statistics section provides a detailed view of how age verification is performing across your sites.

It helps you analyze traffic, monitor verification activity, and identify trends or potential issues.

The page is divided into two main areas:

* **Graph Data panel (top)**\
  Visual charts showing key metrics such as Sessions, Checks, Accesses, and Cost.
* **Table Data panel (bottom)**\
  A detailed breakdown of the same data by selected dimensions.

By default, statistics are shown for the last 7 days, but this can be adjusted using the date selector.

## <mark style="color:$primary;">Dimensions Available</mark>

Statistics can be analyzed across multiple dimensions, including:

* **Dates:** Year, Month, Week, Day, Hour
* **Sites:** Individual websites configured in your account
* **Countries:** Based on user IP address
* **Regions:** Based on user IP address
* **Operating Systems:** OS used by the end user
* **Browsers:** End-user browsers
* **Device Types:** Desktop, Mobile, etc.

## <mark style="color:$primary;">Filtering and Analysis</mark>

You can refine your data by applying multiple filters at the same time.

To apply filters:

1. Click + **ADD FILTER** at the top of the Statistics page.
2. Select a dimension (e.g. Site, Country, Browser).
3. Choose one or more values.
4. Click **APPLY**.

![Statistics Filters](https://content.gitbook.com/content/1v2DbmntPqhCff92tEVb/blobs/3uBacRTbpWlCQjGTUIXu/image)

Filter logic:

* Multiple values within the same dimension use **OR** logic.
* Filters across different dimensions use **AND** logic.

This allows you to:

* Compare performance across sites or countries.
* Analyze pass rates by device type.
* Review cost trends over time.

Filters can be reset at any time using **RESET FILTERS**.

## <mark style="color:$primary;">Metrics Available</mark>

The Statistics section supports the following metrics:

* **Sessions:** Number of visits to the verification page
* **Checks:** A Check is counted each time a verification method is started, including failed or abandoned attempts.

  A Check is also counted when:

  * a returning user logs in with AgeGO Log In (email, Google or passkey);
  * a user is recognised through Cross-Site Verification.

  Returning users recognised automatically through an active session or the Remember me option (including `ag_remember_me` in S2S) do not generate a Check.
* **Check Rate:** Checks / Clicks (percentage)
* **Accesses:** Total successful accesses after verification
* **Access Rate (Sessions):** Accesses / Sessions (percentage)
* **Cost:** AgeGO usage cost, in EUR.

## <mark style="color:$primary;">Exporting Data</mark>

You can download your statistics in CSV format:

* **Download Visible Data:** Exports only the columns currently shown
* **Download All Data:** Exports the full dataset

This allows you to perform deeper analysis externally if needed.


---

# 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.agego.com/admin-panel/statistics.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.
