> For the complete documentation index, see [llms.txt](https://support.sayprimer.com/primer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.sayprimer.com/primer/audiences/audience-filters.md).

# Audience filters

The filter sources you build an audience from — Primer data, website events, your CRM and CSV files — and the limits on filter values.

Filters define who's in an audience. The filter picker groups them by **source** — where the data comes from — in the tabs **Primer**, **Events**, **HubSpot**, **Salesforce** and **CSV Files**. You can combine filters from any source. Text filters match with operators like **is** / **is not**, and numeric and date filters also take ranges.

## Primer data

Primer's own person and company data, available to everyone.

* **People** — Job Title, Seniority Level, Department, Person Location, Skills, Degrees, Majors.
* **Companies** — Industry, Headcount, Annual Revenue, Company Location, Domain, Keywords, Technology, NAICS Code, Founded Year.

Most of these are picked from Primer-defined lists so audiences stay comparable; the picker shows the available values as you type. **Job Title** and **Keywords** also accept your own values.

Keyword coverage is limited, so keep **Keywords** for narrowly focused campaigns. **Technology** works best for technology that shows on a company's website; back-end tools such as CRMs have limited coverage.

## How many values a filter takes

Most filters accept up to **50 values**. A few take more: Job Title, Department, Industry, NAICS Code and Domain.

## Events

The people your [website pixel](https://support.sayprimer.com/primer/connections/website-tracking/installing-the-pixel.md) has seen — for example everyone who visited a page or arrived from a campaign. These filters appear once the pixel is [Connected](https://support.sayprimer.com/primer/connections/website-tracking/pixel-connection-status.md).

* **Pages** — the page someone visited, matching the **first**, **last** or **any** page.
* **UTM parameters** — source, medium, campaign, term and content, matching the **first**, **last** or **any** touch.
* **Forms** — form name, number of form fills and last form submission date.
* **Engagement** — number of visits, session time, first and last touch dates, referrer domain, device type, browser and intent level.
* **Audience** — whether someone belongs to another of your audiences.

Some website filters can apply to a whole **Company** instead of one **Contact**: the audience then includes anyone at a company where any visitor matched.

With a CRM connected, the Events tab also lists **deal** filters — deal name, amount, stage, type, created and close dates, and whether a deal is closed or won.

## CRM

The **HubSpot** and **Salesforce** tabs list the standard and custom fields of the objects Primer reads from your CRM, so you can filter on your own data. They appear once the [CRM is connected](https://support.sayprimer.com/primer/connections/integrations/connecting-a-crm.md); see [HubSpot](https://support.sayprimer.com/primer/connections/integrations/connecting-a-crm/hubspot.md) and [Salesforce](https://support.sayprimer.com/primer/connections/integrations/connecting-a-crm/salesforce.md) for which objects Primer reads.

## CSV Files

Filter against lists you've [imported as a CSV](https://support.sayprimer.com/primer/connections/datasets/importing-a-csv.md).

## Filters for exclusion audiences

An [exclusion audience](https://support.sayprimer.com/primer/audiences/exclusion-audiences.md) uses Primer filters only; the other tabs are greyed out.

## Why some filters are slower to process

Most filters resolve against pre-indexed (normalized) values, so estimates update quickly. A **CRM filter** on a custom field that hasn't been normalized is the exception: Primer scans the raw values instead, so the [estimates](https://support.sayprimer.com/primer/audiences/estimates.md) take longer. When your audience uses one, the builder shows *"Unnormalized filters can cause slower estimates."*

This is only a speed note, not an error: the filter still matches correctly and the audience still builds and syncs. Remove the filter to speed estimates up again, or wait for them to finish.


---

# 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://support.sayprimer.com/primer/audiences/audience-filters.md?ask=<question>&goal=<user_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.
