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

# Analytics

Analytics gives you an aggregate view of verification activity — volumes, completion rates, and match rates — without having to page through individual checks in the Verification logs. It's scoped **per project**, using the same project selector as the rest of the Portal.

{% hint style="info" %}
Analytics is currently available for **Secure SNA (Silent Network Authentication)**. Analytics for SIM Swap and Discovery is on the roadmap.
{% endhint %}

### Getting there

1. From the left-hand navigation, click **Analytics**.
2. Use the project selector in the top-right corner to choose which project's data you're viewing.
3. The **Overview** tab loads by default.

### Filtering results

The filter bar at the top of the Overview tab controls every chart on the page:

* **Date range** — restrict the data to a specific window. The active range is shown as a chip (e.g. `01 Jul 2026 – 10 Aug 2026`); click the **×** on the chip to clear it.
* **Status** — filter to checks in a specific completion status (`Completed`, `Error`, `Expired`), the same statuses used in Verification logs.
* **Network** — filter to checks routed over a specific mobile network operator, drawn from the project's allowed networks.
* **Clear all** — reset every filter back to its default.

### Overview tab

The Overview tab shows three charts, all scoped to the current project, date range, and filters.

<figure><img src="/files/W1LWi92X1VWTxK3U9lc9" alt=""><figcaption></figcaption></figure>

#### Overview of SNA completion statuses

A donut chart showing how SNA checks in the selected range resolved, broken down by:

* **Completed** — the check ran to completion.
* **Error** — the check failed before it could complete.
* **Expired** — the check timed out without a result.

The centre of the donut shows the total number of checks in the range; the legend shows the count and percentage for each status.

#### Distribution of matches in completed SNA

A donut chart scoped to **completed** checks only, showing the split between:

* **Matched** — the network confirmed the claimed MSISDN.
* **No matched** — the network did not confirm the claimed MSISDN.

The centre shows the total number of completed checks; the legend shows the count and percentage for each outcome.

#### Total number of SNA requests

A line chart plotting SNA request volume across the selected date range, with the running total shown in the chart title. Use this to spot trends — spikes tied to a release, a drop-off after an integration change, or steady growth as an integration ramps up.

### What's next

* [**Verification logs**](https://docs.idlayr.com/enterprise-portal/verification-logs) — inspect activity once your integration is making calls.
* [**Projects**](https://docs.idlayr.com/enterprise-portal/projects) — once signed in, create your first project.
* [**Allowed networks**](https://docs.idlayr.com/enterprise-portal/allowed-networks) — review which MNOs your project is approved to route to.


---

# 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.idlayr.com/enterprise-portal/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.
