> For the complete documentation index, see [llms.txt](https://docs.growthfactor.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.growthfactor.ai/data-and-visualization/filters.md).
# Filters
GrowthFactor uses filters in two different places, for two different jobs:
* **List & library filters** narrow what you *see* across your dashboard pages — deals, sites, files, maps, layers, and Market Planning studies — by workspace, type, and sort order.
* **Analog filters** control which of your existing stores are *used for analysis* in Site Analysis, so sales projections and analog comparisons reflect the most relevant subset of your portfolio.
Both are covered below.
***
## List & Library Filters
{% columns %}
{% column valign="middle" %}
Most dashboard pages share a single **Filter** menu for narrowing long lists. Look for the **Filter** button (funnel icon) at the top right of the page — it appears on **Deals, Sites, Files, Maps, Layers,** and **Market Planning studies**.
The button shows a badge with the number of filters currently applied, so you can tell at a glance when a list is narrowed.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
### What's in the menu
The menu combines every way to narrow a list in one place. Each page shows only the sections that apply to it:
* **Show** — limit the list by type or scope (for example, **My Layers**, **Territories**, or **Workspace Layers** on the Layers view)
* **Sort by** — order the list (for example, **Newest first**, **Oldest first**, or **Alphabetical**)
* **Workspaces** — scope the list to one or more workspaces. The workspace tree mirrors your hierarchy, so you can include a parent and its sub-workspaces together. A count next to each workspace shows how many matching items it holds
### Resetting
Click **Reset** at the top of the menu to clear every applied filter at once and return the list to its default view.
***
## Analog Filters in Site Analysis
Analog filters control which of your existing stores are used as comparisons when scoring and forecasting a candidate site. By filtering your portfolio by tags, you can ensure sales projections and analog comparisons are based on the most relevant subset of your locations.
### What Filters Do
When you apply filters:
* **Analog comparisons** use only stores matching your criteria
* **Sales projections** recalculate based on the filtered comparison set
* **Filtered Stores** appear as purple pins on the map
* **Unfiltered stores** remain visible (as red pins) but aren't used in calculations
This allows you to compare a potential site against stores that share meaningful characteristics—rather than your entire portfolio.
***
### Accessing Filters
Click **Filters** in the top bar of Site Analysis (next to the trade area selector). The filter panel displays your available tags and current selections.
***
### Tags
Tags are labels assigned to your stores in My Stores. Common tag categories include:
| Category | Example Tags |
| --------------- | --------------------------------- |
| **Geography** | TX, Southeast, Urban, Suburban |
| **Format** | Drive-through, Mall, Freestanding |
| **Performance** | Top Quartile, New Store |
| **Size** | Small Format, Large Format |
See My Stores for how to create and assign tags.
***
### Applying Filters
1. Click **Filters** to open the filter panel
2. Select tags to include in your comparison set
3. Click **Apply Filters** to update your analysis
The filter bar displays your active selections (e.g., "All of: Florida, Urban").
#### Include vs. Exclude
Click a selected tag to toggle between include and exclude:
* **Include (checkmark):** Only stores with this tag are used
* **Exclude (X):** Stores with this tag are removed from the comparison set
**Example:** To analyze against Florida stores that are *not* Urban:
1. Select "Florida" (include)
2. Select "Urban" and click to toggle to exclude
3. Apply filters
#### Match Mode
**All of:** Stores must have *all* selected include tags to match.
> "All of: Florida, Suburban" returns only stores tagged with both Florida AND Suburban.
**Any of:** Stores matching *any* selected include tag are included.
> "Any of: Florida, Texas" returns stores tagged with Florida OR Texas.
***
### Viewing Filtered Results
When filters are active:
* **Purple pins** on the map show stores matching your filter criteria
* **Red pins** show all other stores (visible but not used for analysis)
* The **filter bar** displays your current selections
* **Sales projections** update to reflect the filtered analog set
***
### Clearing Filters
Click **Reset** to remove all filter criteria and return to using your full store portfolio for analysis.
***
### Common Filter Scenarios
**Regional comparison:**
> Evaluating a Texas site? Filter to Texas stores only so projections reflect regional performance patterns.
**Format matching:**
> Evaluating an urban location? Filter to Urban-tagged stores to compare against similar site types.
**Excluding outliers:**
> Have stores affected by unusual circumstances (construction, temporary closure)? Tag and exclude them from analog sets.
>
> For stores you always want to exclude, email us at - we can update the underlying system to always exclude those stores.
**New vs. mature stores:**
> Filter to stores open 3+ years to base projections on stabilized performance, excluding ramp-up periods.
***
### Best Practices
**Be consistent.** Use standardized tag names across your portfolio. "TX" and "Texas" as separate tags fragment your data.
**Check filter impact.** After applying filters, note how many stores remain in the comparison set. Too few analogs can reduce projection reliability.
**Document your approach.** When presenting analysis, note which filters were applied so stakeholders understand the comparison basis.
---
# 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.growthfactor.ai/data-and-visualization/filters.md?ask=&goal=
```
`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.