> 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/estimates.md).

# Audience estimates

What the size, match size, summary and preview estimates show as you build an audience.

As you add [filters](https://support.sayprimer.com/primer/audiences/audience-filters.md) and destinations, Primer shows estimates so you can see the shape of the audience before you run it: [size](#size), [match size](#match-size), the [summary](#summary) and the [preview](#preview). [Changes since your last run](#changes-since-your-last-run) — the **Δ** indicator — overlays the size and summary once the audience has run.

## Size

How many people match your filters, and how many companies they work at. This is not the final matched count: matching against a destination drops records the platform can't identify, so the audience that delivers is smaller. See [Audience size limits](https://support.sayprimer.com/primer/audiences/audience-size-limits.md) for the minimums and maximum that apply.

## Match size

For **Google Ads, Meta Ads and LinkedIn Ads**, a range of how many people in the audience that destination is likely to match. The Google range breaks down into Google Search, YouTube and Google Display. Other destinations show only their icon here. The range shows **—** while the audience is below a destination's minimum or above the maximum size.

Once the audience has synced, click a destination's icon to open the audience in that ad platform. See [Match rates](https://support.sayprimer.com/primer/audiences/match-rates.md) for what to expect after matching.

### Reddit and international match sizes

With the newer match estimate, Reddit Ads shows a range too, and LinkedIn notes when an audience is mostly outside the US and Canada, where its match rates vary widely.

## Summary

The **Summary** tab breaks the audience down by category — each row shows what share of the audience falls into that value. Some categories describe the **people** in the audience, others the **companies** they work at.

| Attribute        | Describes | What it shows                                           | Example                 |
| ---------------- | --------- | ------------------------------------------------------- | ----------------------- |
| Job title        | People    | Share of people by job title                            | Chief Marketing Officer |
| Seniority        | People    | Share of people by seniority level                      | C-Suite                 |
| Department       | People    | Share of people by department (and sub-department)      | Marketing               |
| Company domain   | People    | Share of people grouped by the company they work at     | acme.com                |
| Annual revenue   | Company   | Share of companies by revenue range                     | $1M–$5M                 |
| Headcount        | Company   | Share of companies by employee-count range              | 50–100                  |
| Industry         | Company   | Share of companies by industry                          | Marketing & Advertising |
| Company location | Company   | Share of companies by location (country, state or city) | United States           |

### Historical win rates

If you've [connected a CRM](https://support.sayprimer.com/primer/connections/integrations/connecting-a-crm.md), the summary adds a **Win Rate** column: for each value in the breakdown, how often opportunities with that attribute have been won, drawn from your CRM's historical deal data. It's shown for company **annual revenue, headcount, industry and location**, and people **seniority, job title and department**, with a marker for how statistically significant the rate is. Hovering a value also shows its expected **deal size** and its **difference in deal value versus your average**.

Win rates come from **Salesforce or HubSpot**. Without a CRM connected, the column prompts you to connect one; with a CRM connected but too few deals to measure, it reads **Insufficient Data**. A HubSpot connection made in companies-only mode has company win rates but no people ones.

## Preview

The **Preview** tab shows a sample of who matches your current filters: up to the **first 250 records**, **25 at a time** across pages. Search it by job title, company, industry or keywords. It's for sanity-checking your filters, not the full audience, and has no export.

### People and Companies preview

The newer preview switches between **People** and **Companies**, searches by name or company, and opens a person's or company's card when you click a row. **Download as CSV** exports up to 1,000 rows of the current view with extra columns, including ICP fit and website activity. Beside Chat, the download appears only for audiences with [Events filters](https://support.sayprimer.com/primer/audiences/audience-filters.md#events).

## Changes since your last run

Once an audience has been run at least once, a change indicator — labelled **Δ** — shows how the current estimate has moved against earlier runs of the same audience, so you can see the effect of a filter edit. It appears in two places:

* On the [**Size**](#size) totals — the company and person counts.
* As a **Δ** column in each [**Summary**](#summary) category.

Each Δ shows a **relative percent change by default and the exact record difference on hover**. It shows a **dash (—)** when the change is within estimate noise or can't be computed with confidence. A brand-new draft has nothing to compare against, so no Δ shows until the audience has run once.


---

# 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/estimates.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.
