> 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/getting-started/what-primer-does.md).

# What Primer does

Primer builds targetable ad audiences from your first-party data and ICP and syncs them to your ad platforms.

Primer takes the people and companies you care about — your CRM, a CSV, your ICP, your website visitors — and turns them into audiences you can analyze, track, and/or target in your GTM motions (Ads, Email Campaigns, etc)

## The core flow

1. **Bring in data.** Connect a CRM, import a CSV, push records via S3 or the API, or install the website pixel.
2. **Draft an audience.** Define who you want to reach with filters, then Primer estimates its size, reach and firmographics.
3. **Sync.** Primer syncs your audience to the specified destinations and matches the records to ad platforms if applicable.
4. **Target.** Use the synced audience in your GTM motion (ad campaigns, outbound outreach, etc).

Each step has its own page. Start with [building an audience](/primer/audiences/building-an-audience.md).


---

# 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/getting-started/what-primer-does.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.