> For the complete documentation index, see [llms.txt](https://docs.churned.io/churned-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.churned.io/churned-docs/dashboard-and-features/churned-per-page/segments-page/users-page.md).

# Users Page

## Overview

<figure><img src="/files/UIBv60TGo679AvNZ46CT" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The **user page** displays your customers with their segment symbol also showing when they used your product last and which company the customer is part of.&#x20;
{% endhint %}

***

## User ID

<figure><img src="/files/K4TfeFJahfJNpjT3ySfC" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The **User ID** stands for the name, email, customer id, etc of the customer used your product.
{% endhint %}

***

## Segment

<figure><img src="/files/5t70HmAJ69tDqcxOAyLC" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The **name** of the segments are based on the RFM-Model:

* Champion ♥︎
* Loyalist ☻
* Potential Loyalist \[☺︎]
* New ⊕
* Need Attention ‼
* At Risk ☹︎
* Hibernating ☾
* Lost ⊖

You can filter this information to find out which customers are, for example, champions or hibernating.&#x20;
{% endhint %}

***

## Last Product Usage

<figure><img src="/files/7E8Td9N0TKE1IHe4Rr3f" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Last Product Usage** refers to the last time the customer has used your product, most of the time this will mean when they have last logged in to your service platform.
{% endhint %}

***

## Customer

<figure><img src="/files/rvULNzGWSDgwfykEEYvn" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The **customer** column will show you the company that the customer works at.&#x20;

You can use the search button to find the company you want to look at so you can get the information you are looking for even quicker.
{% endhint %}

***

## Filters&#x20;

<div align="left"><figure><img src="/files/zhSv45HT1FAuW2oiyJzA" alt="" width="263"><figcaption></figcaption></figure></div>

{% hint style="info" %}
There are a lot of possibilities with the **filter** button. We have divided it into:

* **Custom filters** → Filters that are made for the company&#x20;
  * The custom filters are made to filter "internally", meaning that they don't have their own column but the information will be filtered in the system.
* **Default filters** → Standard filters that are standard in the user page
  * The default filters aren't "made" specifically for your company. These filters are more general then the custom ones.

{% endhint %}

***


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.churned.io/churned-docs/dashboard-and-features/churned-per-page/segments-page/users-page.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.