> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/marketing-intelligence/dashboard-builder/using-the-new-dashboard-filters.md). # Dashboard Filters HockeyStack's dashboard filters enable you to filter entire dashboards by fields of your choice. This is useful when you want to take a look at your marketing efforts from a particular angle, for example by filtering a set of reports by deal type (new vs. existing business) or company size (by number of employees or market segment). Additionally, you can filter different objects in a dashboard by different fields at the same time. A common scenario is one where you want to filter a table that presents Leads, MQLs, and Closed Won deals by Region, but there are separate fields that define Region on lead and deal objects. The region on the lead object may be Lead\_Region\_\_c, while the region on the opportunity object may be Opp\_Region\_\_c. You can now create a Defined Property that combines these two fields into a single filter. ## How It Works First, you need to build Properties, which you will later use for filtering. Go to Definitions → Properties, and create mappings, using the fields of your choice (you'll find them in **Action Properties** section of a dropdown), and mapping them either to specific values of your choice or simply back to the Property value.

In the Advanced Options of your Property, toggle Include in Filters. If you don’t manually turn this on, it won’t be displayed in the filter options. If it's a touchpoint breakdown, toggle the touchpoint breakdown.

### Keep in mind * Properties are executed from top to bottom. So place your detailed definitions on top, and the general ones on the bottom. --- # 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.hockeystack.com/marketing-intelligence/dashboard-builder/using-the-new-dashboard-filters.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.