> For the complete documentation index, see [llms.txt](https://tembi.gitbook.io/tembi-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tembi.gitbook.io/tembi-knowledge-base/product-how-to/filters.md).

# Filters

Filters are how you turn a large market dataset into a specific, usable scope - whether you are building prospect lists, monitoring accounts, or analysing competitors.

In Tembi, filters are organised by data type (webshop, company, delivery, etc.), and you can also pin your most-used filters for faster day-to-day work.

### Where to find filters

Go to **Webshops** and click **Filters**.

Inside the filter panel you can:

* Search for a filter using the search field
* Browse filters by category
* Add filters to your active scope
* Pin filters as favourites for quick access

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

### Filter categories

Tembi groups filters into a few clear buckets. These mirror the main data layers in the platform.

#### Sales and ownership

Used for commercial workflow and pipeline management:

* Lead owner
* Lead status
* Tags
* Webshop address
* Saved list

#### Webshop

Used to segment by how the webshop operates and behaves:

* Webshop platform
* Size indication
* Growth prediction
* Traffic and traffic growth
* Technology signals (for example technological investments)
* Domain details (TLD, registration date)
* Systems (checkout system, payment system, return system, etc.)
* Checkout score
* Sitemap search
* Custom scraping flag

#### Company

Used when you want to filter by the company behind the webshop:

* Company name and free search
* Organisation number
* Address and location fields (municipality, zip code, postal town)
* Industry fields
* Employees
* Company foundation date

#### Delivery

Used when your question is about delivery setup and configuration:

* Delivery provider
* Delivery provider position in checkout
* Delivery method
* Delivery provider + shipping method
* Export markets
* Lost first position
* Fastest shipping time range
* Free delivery threshold
* Checkout text search
* Delivery price position
* Parcel return address

#### Product insights

Used to qualify and segment by what webshops sell:

* Ecommerce category and category type
* Brand within a category
* Number of categories
* Number of products and growth in products
* Median product price
* Median product weight
* Mapped products and categories counts
* Portfolio mix views (price vs product count, weight vs product count)

#### Financial

Used for company-level financial segmentation where available:

* Company revenue
* Revenue growth
* Gross profit
* Financial result

### Smart filters

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

Smart filters are pre-configured filters built for common last-mile delivery workflows.

They are designed to help you get to the key views fast without building the logic manually.

Typical smart filters include:

* **New webshop clients**
* **Lost webshop clients**
* **First positions**
* **New first positions**
* **Lost first positions**

Use smart filters as a starting point, then add additional filters (for example size indication, category, platform, geography) to refine the scope.

### Practical tips

* Use the search bar in the filter panel when you know what you want (for example type “delivery”).
* Keep favourite filters for the handful of filters you change frequently.
* Save full filter setups when you want consistency across time or across the team.
* If your setup needs AND/OR logic with multiple groups, use advanced filtering and save the result as a saved filter.

If you want, paste one or two ICP definitions in plain language (for Sales or KAM) and I’ll translate them into the cleanest filter setup using these categories.


---

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

```
GET https://tembi.gitbook.io/tembi-knowledge-base/product-how-to/filters.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.