# Analytics Feature

## Overview

Our **Analytics Feature** provides real-time and historical insights into your streaming sessions, enabling you to optimize performance and enhance viewer experiences. This page explains what data is captured, how to access the analytics dashboard, and how to interpret the metrics.

You can visit the analytics page by visiting to your project details page and navigating to the analytics tab.

***

## What it does?

Our analytics module tracks key data points for each streaming session, such as start time, viewer location, browser, operating system, screen size, latency, and more.

***

## **Why It Matters**

* Quickly diagnose performance issues (e.g., high latency or loading times).
* Understand where viewers are located and what devices they use.
* Make informed decisions about stream quality settings and user experience.

***

## **Key Metrics**

| **Metric**                 | **Description**                                                                                         |
| -------------------------- | ------------------------------------------------------------------------------------------------------- |
| **Session Start**          | A simple timestamp indicating when the session began.                                                   |
| **Streaming ID**           | A unique identifier for each streaming session.                                                         |
| **OS / Browser**           | The operating system and browser used by the viewer.                                                    |
| **Region / Country**       | Geographical location of the viewer.                                                                    |
| **Screen Resolution**      | The viewer’s screen width and height.                                                                   |
| **WebRTC FPS**             | Frames per second as measured by WebRTC (network-based metric). Note: the app may render at higher FPS. |
| **Latency (ms)**           | Round-trip time between the server and the viewer’s device.                                             |
| **Loading Time (s)**       | Time taken to start playback after the session is initiated.                                            |
| **Session Duration (min)** | Total time the viewer spent in the session.                                                             |

{% hint style="danger" %}
**Warning:** Do not assume latency is based solely on proximity; network quality plays a crucial role.
{% endhint %}

{% hint style="warning" %}
**Latency (ms)**\
High latency is typically due to one of two main factors:

* **Distance to Server:** Being far away from the server naturally increases the travel time for data.
* **Poor Network Conditions:** Issues such as network congestion, interference, or weak signal strength can also result in elevated latency.
  {% endhint %}

{% hint style="info" %}
**Note: WebRTC FPS**\
This metric reflects the effective frame rate over the network as measured by WebRTC. It may be lower than the app's rendering FPS because it accounts for real-world network issues like bandwidth limitations and packet loss. It won't effect your performance.
{% endhint %}

{% hint style="warning" %}
**Hint: Network Speed Caveat**\
In corporate environments or households with multiple connected devices, speed tests might show a high connection speed at the router level. However, the actual speed available to each device can be significantly lower when bandwidth is shared.
{% endhint %}