> 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/primers-database.md). # Primer's database The identity graph Primer builds audiences from — B2B and B2C people and companies, with coverage that varies by region. When you draft an audience with filters, you're querying Primer's **identity graph** — a large, continuously updated store of people and companies. It's what lets you target by firmographics, role, technographics and more without uploading a list first. ## What's in it * **People and companies**, spanning both **B2B** and **B2C** contexts. * Attributes you filter on: company firmographics (industry, headcount, revenue, location), person attributes (job title, department, seniority), technographics, keywords, and more. See [Your ICP definition](/primer/settings/icp-definition.md) and [Audience filters](/primer/audiences/audience-filters.md) for what you can target. ## Coverage varies by region Coverage isn't uniform — it's densest where the underlying data is richest and thinner in some regions and segments. That's why the same set of filters can estimate a larger audience in one geography than another. Primer's size estimate reflects the coverage it actually has for your filters, and [estimates match rates](/primer/audiences/match-rates.md) then reflect how much of that a given ad platform can identify. > Exact record counts are marketing figures, not a value in the product, so they aren't quoted here. For current database size and coverage claims, see [sayprimer.com](https://www.sayprimer.com). --- # 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/primers-database.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.