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

# Analytics

> Track translation progress and coverage with built-in analytics.

Entri's analytics give project managers a clear picture of where localization work stands. Rather than manually counting untranslated strings, the analytics dashboard surfaces coverage and progress data automatically, so you can see what's done, what's in progress, and where work is stalled.

## Translation Coverage

Coverage reports show what percentage of keys have been translated and approved for each target language. Coverage is calculated separately for each status in the workflow:

| Status           | Meaning                                   |
| ---------------- | ----------------------------------------- |
| **Untranslated** | No translation value exists yet           |
| **Translated**   | A value has been entered but not reviewed |
| **Reviewed**     | Checked by a reviewer                     |
| **Approved**     | Final — ready for production              |

A language is only fully ready for release when all keys are in **Approved** status. The analytics dashboard makes this visible at a glance for every language in your project.

## Project Health Overview

The project overview gives you a single-screen summary of where every language stands:

* Total key count
* Per-language progress bar showing the breakdown of Untranslated / Translated / Reviewed / Approved
* Languages closest to completion and languages furthest behind
* Recent activity indicating whether work is actively progressing

Use this view during sprint planning or before a release to quickly identify which languages are ready and which still need attention.

## Identifying Bottlenecks

When a language has many keys in **Translated** status but few in **Approved**, it signals a review backlog. When a language has keys stuck in **Untranslated**, translation work hasn't started or is blocked.

The analytics view helps you answer:

* Which language is furthest behind schedule?
* Is translation work keeping pace with new key additions?
* Are reviews creating a bottleneck before approval?
* Which languages are ready to ship?

<Tip>
  Filter the translation editor by status (for example, show only **Untranslated** keys) to jump directly from the analytics view into the specific work that needs to be done. This is faster than paging through the full key list manually.
</Tip>

## Use Cases by Role

**Project managers** — use the coverage report before each release to confirm all target languages meet the required approval threshold.

**Translation leads** — use per-language progress to assign work to translators and track output over time.

**Developers** — use the overview to see the impact of recently pushed keys on overall coverage, and to confirm that translations are ready before a deployment.

<Info>
  Analytics reflect the live state of the project. There is no delay between making a change in the editor and seeing it reflected in the coverage numbers.
</Info>