> 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/connections/integrations.md). # Integrations Connect Primer to the tools you already use — your CRM and your ad destinations — to bring data in and push audiences out. Integrations are the live connections between Primer and your other tools. Connect a source to bring people and companies in, and connect a destination to push finished audiences out. * [**Connecting a CRM**](/primer/connections/integrations/connecting-a-crm.md) — read people and companies from HubSpot or Salesforce. * [**Connecting a destination**](/primer/connections/integrations/connecting-a-destination.md) — sync a ready audience to an ad platform like Google, Meta or LinkedIn. Don't see the tool you want to connect? For ad platforms, check [Platforms that aren't listed](/primer/connections/integrations/connecting-a-destination.md#platforms-that-arent-listed) — some are in beta or run through a connection you already have. For anything else, contact . To see who visits your site, set up [Website tracking](/primer/connections/website-tracking.md); for static lists you upload yourself, see [Datasets](/primer/connections/datasets.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/connections/integrations.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.