> For the complete documentation index, see [llms.txt](https://docs.antsomi.com/cdp-365-user-guide-en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.antsomi.com/cdp-365-user-guide-en/insights/reports/filter-your-data/configure-filter-conditions.md).
# Configure filter conditions
Filters conditions tell Insights which records to include in or exclude from your report.
## Configure filter conditions
Filters conditions tell Insights which records to include in or exclude from your report.
### Include vs Exclude filters
*Include* filters retrieve only the records that match the conditions, while *exclude* filters retrieve only the records that DON'T match the conditions.
### Filter clauses
Conditions consist of one or more clauses.
A simple filter has just one clause. For example, `Country` **Equals** "France".
Multiple clauses can be joined with "OR" logic (true if any conditions are met), "AND" logic (true if all conditions are met), or both. For example:`Country` **Equals** "France" OR`Country` **Equals** "Germany"AND`User Type` **Equals** "New user"AND`Sessions` **Greater Than** 100
An OR clause can contain dimensions or metrics, but not both.
### Operators
Operators compare the fields in the filter against values you provide. The operators available depend on whether you are filtering a text, number, date, or logical field.
### Text operators
| Operator | Description |
| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Is | The comparison value exactly matches the dimension value.
Example
The comparison value "chrome" exactly matches "chrome" but not "Chrome" or "chromebook"
|
| Contains | The comparison value is contained within the dimension value.
Example
The comparison value "chrome" is contained within "chrome" and "chromebook" but not "Chrome"
|
| Starts with | The dimension value starts with the comparison value.
Example
The comparison value "Chrome" starts "Chrome" and "Chromebook" but not "Google Chrome"
|
| Matches any | One or more of the comparison values exactly matches the dimension value. Works just like Equals but for a comma-separated list of values.
Example
IN "Chrome,Windows,MacOS" matches if any of those are in the dimension.
If your values contain commas or backslashes as part of the data to match, use a backslash to escape them.
Example
If you want to match "ab,cd" and "50\50" precede the comma and backslash with :
In "ab,cd, 50\50"
|
| Is Null | Matches if the dimension value is null. |
### Numeric operators
| Operator | Description |
| ------------------------------- | ------------------------------------------------------------------------------ |
| Equals ("=") | The dimension or metric value is equal to the comparison value |
| Less than ("<") | The dimension or metric value is less than the comparison value |
| Greater than (">") | The dimension or metric value is greater than the comparison value |
| Greater than or equal to (">=") | The dimension or metric value is greater than or equal to the comparison value |
| Less than or equal to ("<=") | The dimension or metric value is less than or equal to the comparison value |
| Is Null | The dimension or metric value is null |
### Date operators
| Operator | Description |
| -------- | ---------------------------------------------------------- |
| After | The dimension value is greater than the comparison value |
| Between | Dimension values are within the range of comparison values |
| Before | The dimension value is less than the comparison value |
| Is Null | The dimension value is null |
---
# 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.antsomi.com/cdp-365-user-guide-en/insights/reports/filter-your-data/configure-filter-conditions.md?ask=&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.