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

# Users

> Browse identified and anonymous users, see lifecycle stages and first-touch or last-touch attribution, and open full user profiles.

The **Users** page lists the people who were active in the selected date range.

## Users and Anonymous tabs

| Tab | Shows |
| - | - |
| **Users** | Identified users: people with a `user_id` from [`identify()`](https://docs.manalens.dev/guides/identify-users) |
| **Anonymous** | Visitors who have not been identified |

Each tab shows its count. Search by anonymous ID, user ID or the `email` trait. Each row shows the ID, lifecycle stage, country, device, OS, browser, first seen, last seen, last event, revenue, and the acquisition fields.

Click **First seen**, **Last seen** or **Revenue** to sort the table. The first click sorts from high to low, the second from low to high, and the third goes back to the default order (last seen, newest first). The sort applies to every page, and the link keeps it.

**Revenue** is the same value as on the user profile, for the selected date range. For an identified user with billing records in the selected currency (USD by default), it is the net billing revenue (invoices less refunds). Otherwise it is the sum of the `revenue` property on the user's custom events. For an identified user, this includes every anonymous ID that links to that user only (for example the website and the game). An anonymous ID that links to two or more users counts for none of them.

## Attribution filter

Acquisition filters on this page can match a user's first touch, last touch or either:

| Mode | Matches |
| - | - |
| **Any** (default) | Either the first or the last touch matches. The table shows the first touch, else the last. |
| **First-touch** | Only the first touch |
| **Last-touch** | Only the last touch |

First-touch and last-touch values are the earliest and latest non-empty value of each field over the user's whole history. The date range selects which people appear; it does not change these values. They are useful facts, but they are not conversion credit. For credit, see [attribution models](https://docs.manalens.dev/attribution/models.md).

## Audience insights

Two cards show above the table:

* **User Lifecycle:** how many people are in each stage.
* **Sessions per User:** how often people come back.

| Stage | Definition |
| - | - |
| **New** | First active in the last 30 days |
| **Returning** | Active in the last 30 days, not new and not fading |
| **At Risk** | No activity for 14 or more days after earlier activity |
| **Churned** | No activity for more than 30 days |
| **Resurrected** | Active again after a gap of 30 or more days |

## User profiles

Click a row to open the profile. An identified user has one profile for all anonymous IDs that link to that user only. Every link (Users, Activity, Live, a report) opens the same facts, attribution and revenue. An anonymous player whose game opened your website with a [handoff link](https://docs.manalens.dev/guides/identify-users.md#one-player-on-the-website-and-in-the-game) also has one profile for the browser and the game install. **Linked IDs** lists the other anonymous IDs. A profile shows:

* **Facts:** first seen, last seen, page views, events, revenue, country, device, OS, browser, locale, anonymous ID and user ID.
* **Attribution:** first and last channel, referrer, referral, ad, source, medium, campaign, content, term and click ID.
* **Activity:** a paged history of page views and custom events. For identified users, it also shows a calendar of active days over the last year. Activity from before `identify()` is included when the browser links to only this user.
* **Revenue over time:** revenue linked to this user, including invoices from [connected billing providers](https://docs.manalens.dev/features/revenue.md). With payment records, a legend under the chart and the tooltip of each bar show the amount of each provider (Stripe, Paddle, itch.io).
* **Activity:** the events of the user, with the payments and refunds from connected providers as rows.
* **Properties tab:** next to **Activity**. It lists the profile's properties: [known properties](https://docs.manalens.dev/api/profiles/known-properties.md) (Discord ID, Steam ID, email, socials) first with a label and an icon, then custom properties by name. Properties come from `identify()` traits and from the [profile properties API](https://docs.manalens.dev/api/profiles/update-properties.md).

## Properties tab

Open a profile and click **Properties**. Owners, admins and editors can:

* **Edit** a value. A number or a boolean keeps its type when the new text is still a number or `true`/`false`.
* **Delete** a property. It is removed from the profile.
* **Add property:** pick a known name from the list or type a custom name, then enter a value. Known names get a format check, for example a Discord ID is 17 to 20 digits.

Viewers see the properties but cannot change them. An anonymous visitor has no properties: properties belong to a `user_id`, so call `identify()` first. A change is saved as an `identify` event that adds no visit or activity. It shows in reports after a few seconds. A backend or a Discord bot can set the same properties with an [API key](https://docs.manalens.dev/api/authentication.md#api-keys) that has the `profiles:write` scope; see [Update Properties](https://docs.manalens.dev/api/profiles/update-properties.md).

> [!NOTE]
>
> A user is the explicit `user_id`, else the one user that the `anonymous_id` links to, else the `anonymous_id`. See [core concepts](https://docs.manalens.dev/data/concepts.md#people-and-identity-links).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.