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

# Analytics

> Track review cycle time, activity, repository trends, and team velocity in the Autter platform.

Autter analytics helps you understand how pull requests move through review. Use trends to find bottlenecks and evaluate process changes.

<Frame caption="Placeholder: replace with an approved analytics dashboard screenshot.">
  <img src="https://mintcdn.com/autter/ZqVSJE8MeDV-Tn7Q/images/placeholders/analytics-dashboard.svg?fit=max&auto=format&n=ZqVSJE8MeDV-Tn7Q&q=85&s=c2207c61fb5277b8c84862eb6ee3dec6" alt="Placeholder showing Autter analytics for merged pull requests, review time, changed lines, and active reviewers" width="1200" height="620" data-path="images/placeholders/analytics-dashboard.svg" />
</Frame>

## Metrics highlighted by Autter

The public analytics product includes metrics such as:

* pull requests merged per engineer
* median review time
* lines modified per pull request
* active reviewers
* cycle time from first commit to merge
* review workload and response time
* team and repository trends over time

Available views and exports can vary by plan. See [current pricing](https://www.autter.dev/pricing).

## Questions analytics can answer

* Is median review time improving?
* Where does cycle time accumulate?
* Are pull requests growing larger?
* Is review work distributed unevenly?
* Did a new review rule reduce recurring issues?
* Which repositories need a different rollout or rule set?

## Use metrics responsibly

Review metrics describe a system, not a person's value. Interpret them with repository complexity, incident work, mentoring, and team responsibilities.

Good uses include:

* finding long waits between review stages
* comparing a repository before and after a workflow change
* spotting an overloaded reviewer group
* tracking whether smaller pull requests merge faster
* identifying recurring issue categories that need a rule or engineering investment

Avoid ranking engineers from one metric. A low pull request count can reflect complex work, review load, or responsibilities outside code delivery.

## Add AI authorship analytics

The Autter CLI can contribute explicit AI authorship and coding agent context in connected mode. This lets teams evaluate AI usage without inferring authorship from code style.

See [Connect to the Autter platform](/cli/connect-platform) and [Data and privacy](/cli/data-and-privacy).