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

# Filters and segments

> Narrow any report by page, location, technology, event property or acquisition, and save a set of conditions as a reusable segment.

## Date range and comparison

Every report page has a date range in the toolbar. Choose a preset or a custom range. Ranges use UTC days. On Overview and custom dashboards, you can also compare with the previous period.

## Filters

Open the filter menu in the toolbar to add a condition. Filters apply to every card on the page.

| Group | Fields |
| - | - |
| **Data** | Date from, Date to, Page path |
| **Location** | Country, Locale |
| **Technology** | Device (`desktop`, `mobile`, `tablet`, `bot`), Operating system, Browser |
| **Event** | Event property: any key in your event `properties` |
| **Acquisition** | Channel, UTM source, UTM medium, UTM campaign, UTM content, UTM term, Campaign ID, Paid source, Ad click ID, Referral, Referrer origin |

Each condition uses one operator:

| Operator | Meaning |
| - | - |
| is, is not | Exact match |
| is any of, is none of | Match a comma-separated list |
| contains, starts with, ends with | Text match |
| greater than, less than | Number comparison |
| is set, is not set | The field has a value, or not |

Conditions combine with AND. A report can have up to 20 conditions.

> [!TIP]
>
> Events from a game or app build have an **App** group: platform, storefront, app version, build and engine. See [App and game events](https://docs.manalens.dev/sdks/app-events.md#reports).
>
> Use an **Event property** filter to compare plans, experiments or features. For example, `plan is pro` on a funnel shows the conversion rate for Pro users only.

When you type a value, the filter menu suggests the values that occur in the selected date range, most frequent first: countries, builds, versions, event names, event property values and the other fields. You can still type any value. For **is any of** and **is none of**, each suggestion adds one value to the list.

## People filters

On the [Users](https://docs.manalens.dev/features/users.md) page, the filter menu also has a **People** group. These conditions select people, not events. They apply to the Users and Anonymous tabs, their counts and CSV export, and the Audience insights cards.

| Filter | What it matches |
| - | - |
| **Lifecycle** | The user's lifecycle stage at the end of the date range: New, Returning, At Risk, Churned or Resurrected. Choose one or more stages. |
| **Behavior** | People who did an event a number of times (at least, more than, exactly, at most, fewer than) in the last 7, 30 or 90 days, or within a number of hours or days after they were first seen. You can add one event property condition. |
| **Revenue** | The Revenue column of the Users table, in the date range. |
| **Data source** | People with (or without) events from the web SDK, an app SDK or the server API in the date range. |

A user is the identified user ID. Anonymous IDs that link to one user ID count as that user. People conditions combine with AND, and with the other filters. Other reports do not apply people conditions; they show a notice instead.

In the API, people conditions are the `user_filters` and `behavior_filters` query parameters (JSON arrays). For example, `user_filters=[{"field":"lifecycle","op":"in","value":["New","Returning"]}]` or `behavior_filters=[{"event":"purchase","event_type":"track","op":"gte","times":2,"relative_to":"first_seen","window":{"value":7,"unit":"day"}}]`. `lifecycle` takes `eq` and `in`; `revenue` takes `eq`, `neq`, `gt`, `gte`, `lt` and `lte`; `source` takes `eq`, `neq`, `in` and `nin`. Any other field or operator returns HTTP 400.

## Segments

A **segment** is a named set of filter conditions that you can use again.

1. Add one or more filters.
2. Open the filter menu. Under **Segments**, enter a name and click **Save as segment**.
3. To apply a segment, open the filter menu and click its name. Click it again to remove it.

A segment saves the people conditions too. A behavior window such as "last 30 days" stays a rolling window. When a segment is active, its conditions are added to any other filters on the page. Segments belong to the project, so your teammates can use them too. You can also apply a segment to a [funnel](https://docs.manalens.dev/features/funnels.md) chart.

## Bots

Reports exclude bot traffic unless you set **Device** to `bot`.


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