> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-engage/marketers-and-editors/reporting.md).

# Reporting

You should continuously monitor personalization on your website to make adjustments where needed.

On the **Reporting** dashboard in the **Engage** section, you can monitor the personalization set up on your website.

## Segments

You can get an overview of how the segments you have configured for your website are doing.

![Segment performance overview](https://2164986937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fds5IoWmsX6a6ooVdYthx%2Fuploads%2Fgit-blob-0d13531654bc363ec45ea10f14da07694b538b1d%2FSegment-performance-overview.png?alt=media)

When you select a segment, you will see an overview of the configuration. As you scroll down, you can monitor its performance.

Learn more about segments and how to set them up in the [Personalization section](/umbraco-engage/marketers-and-editors/personalization/creating-a-segment.md).

### Segment Potential

The segment potential depends on how many pageviews, sessions, and profiles are covered within the segment.

In the Reporting dashboard, you can see the coverage of these parameters. You can also see the number of sessions a new profile requires to activate the selected segment.

### Segment Personalization

In many cases, it can be interesting to monitor how many of your website's sessions, page views, and profiles have been personalized.

In the Segment Personalization section, you can see how much of the incoming traffic on your website is personalized.

### Goal Performance

You can also get an overview of how the goals you have configured are performing. The table in the **All goals** section compares the goal performance between the control group and the personalized group.


---

# 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://docs.umbraco.com/umbraco-engage/marketers-and-editors/reporting.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.