> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/analytics/getting-started-with-analytics.md).

# Getting Started with Analytics

Learn what is in Analytics: Dashboards, Pivot Tables, and Reports.

### Overview

Analytics turns Project data into reporting signals for governance and execution.

Use it for weekly status, risk tracking, and outcome reporting.

### Key Concepts

* **Dashboard**: quick monitoring view for recurring reviews
* **Pivot table**: analysis tool for grouping and summarizing data by field
* **Report**: packaged output for sharing outcomes with stakeholders

### How It’s Used

Use dashboards for recurring governance meetings.

Use pivot tables for deeper analysis, such as status distribution by Segment.

Use reports to standardize stakeholder updates.

### Benefits

* Faster status reviews
* Consistent reporting across Projects
* Earlier visibility into risk and slippage

### Setup Steps

Select the analytics tool based on the immediate goal.

#### Dashboards

Dashboards are for quick monitoring. They work well for weekly status checks.

* [Dashboards](/analytics/dashboards.md)

{% hint style="info" %}
Screenshot placeholder: dashboard with 3+ widgets and visible filters.
{% endhint %}

#### Pivot Tables

Pivot Tables are for deeper breakdowns. Use them to slice data by field.

* [Pivot Tables](broken://spaces/bO5MkvlsUXaVsGsjqKWy/pages/0hOj4KMod4iGVkX792sc)

{% hint style="info" %}
Screenshot placeholder: pivot table with rows, columns, and a measure.
{% endhint %}

#### Reports

Reports are for sharing outcomes. Use them to standardize what gets reviewed.

* [Reports](/analytics/reports.md)

{% hint style="info" %}
Screenshot placeholder: reports list showing existing reports.
{% endhint %}

### Best Practices

* Keep shared dashboards stable to protect trend comparability.
* Keep Segment Types stable to protect reporting continuity.
* Pair dashboards with Save Views to create follow-up work lists.

### Summary

Start with dashboards for monitoring, then use pivot tables for analysis depth, and reports for stakeholder packaging.


---

# 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://help.transform.ai/analytics/getting-started-with-analytics.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.