> 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/profiling.md).

# Profiling

Explore how the Profiles section helps track visitor sessions, manage profiles, and differentiate between identified and unidentified visitors.

The **Profiles** section offers an overview of all the visitors that visited your website. To access the profiles section, navigate to **Engage** > **Profiles**.

![Profiles section](https://2164986937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fds5IoWmsX6a6ooVdYthx%2Fuploads%2Fgit-blob-fed79729859c975caae97368a06e9a3e4359e1c1%2FProfiles-v16.png?alt=media)

This section provides an overview of all visitors:

![Profiles Overview](https://2164986937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fds5IoWmsX6a6ooVdYthx%2Fuploads%2Fgit-blob-41127e0f8c8bc85dcea1a3f5b00446d5ab90e408%2Fprofiles-overview-v16.png?alt=media)

At the top, the total number of visitors that visited your website is displayed. You can also see how many visitors are identified versus unidentified.

The **New profiles (last 30 days)** chart shows how many profiles were added in the last 30 days. The **Profile growth (last 365 days)** graph shows how the number of profiles has grown over the past year.

The table lists the individual profiles.

## Identified versus Unidentified Profiles

As long as there is no data of a visitor, this profile is called "Unidentified". If a visitor [does not give consent](/umbraco-engage/developers/introduction/the-umbraco-engage-cookie/module-permissions.md) to be identified, they remain "Unidentified".

However, once a visitor logs in (via Umbraco's Members section) or submits an Umbraco Form (requires the [Forms](/umbraco-engage/add-ons/forms.md) add-on), they become an "Identified Profile." For example: If you see a visitor name in the Profiles table it is because the visitor has logged in as a member.

## Profiles Overview

![Table view of Profiles Overview](https://2164986937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fds5IoWmsX6a6ooVdYthx%2Fuploads%2Fgit-blob-5ef74d556a1ab98e984343ed87030645f368f5b1%2Fprofiles-overview-table-view-v16.png?alt=media)

The Profiles table displays all visitors to the website, showing:

* Whether the visitor was identified or unidentified
* The number of sessions of the visitor
* The number of pageviews within those sessions
* The first session that the visitor had on the website
* The last session of the visitor
* The number of goals triggered by the visitor
* The total value of the goals

Finally, you can see a blue or a grey icon at the beginning of the row. A grey icon indicates that Umbraco Engage did not enrich the visitor's experience. A blue icon indicates that Umbraco Engage enriched the visitor's experience by showing an A/B test variant or a personalized version.

### Filtering the Results

It is possible to filter the profiles table by clicking the **Filter** button.

![Filtering the profiles overview using the filter button](https://2164986937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fds5IoWmsX6a6ooVdYthx%2Fuploads%2Fgit-blob-4f6cef62731032f708160c798184e115e47bc592%2Ffiltering-results-v16.png?alt=media)

You can filter by:

* Excluding unidentified or identified profiles
* Excluding high-potential profiles
* A minimum number of completed goals
* A minimum goal value
* The period the profiles were active
* Segment
* Member name

For more details, click **Show profile** in a specific profile's row. For more information, see the [Profile Detail](/umbraco-engage/marketers-and-editors/profiling/profile-detail.md) article.

![Filtering Options](https://2164986937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fds5IoWmsX6a6ooVdYthx%2Fuploads%2Fgit-blob-e6940333aeff8db80b7c67ccec3ab8afc4a0b723%2Ffiltering-results-options-v16.png?alt=media)


---

# 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/profiling.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.