> 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/primer-support-review/section-connections/datasets.md). # Datasets Connect your own people and company lists to Primer as a dataset — import a CSV, upload via S3, or push over the API. A dataset is your own static list of people and companies, connected to Primer to filter audiences against. Alongside a CRM connection, you can import your own lists directly. Every method loads the same canonical records — they differ only in how the file reaches Primer. * **Importing a CSV** — upload a file in the app. Start here: it defines the columns Primer recognizes, which the other methods reuse. * **Uploading via S3** — drop CSVs to a Primer S3 location for automated, scheduled loads from a warehouse or pipeline. * **Pushing via API** — send records over HTTP to push continuously from your own systems. Each upload is a **complete snapshot** of that dataset: records absent from a new file are dropped, not merged with the previous one. --- # 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/primer-support-review/section-connections/datasets.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.