> 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-legacy/use-cases/6sense-ad-expansion.md). # 6Sense Ad Expansion 6sense helps identify in-market accounts, but its targeting typically operates at the account level. This can lead to ads being shown to individuals who are not key decision-makers, such as junior employees, which may reduce campaign efficiency. By integrating with Primer, teams can build persona-specific audiences based on their Ideal Customer Profile (ICP), improving precision and match rates across platforms like Google, Meta, and LinkedIn. For implementation steps and best practices, refer to Primer’s [6sense Ad Expansion Guide.](https://www.sayprimer.com/use-cases/primer-6sense-buyer-intent) {% embed url="" %} ### How It Works: * **Collect intent signals in 6sense**\ Enable predictive modeling in 6sense to identify in-market accounts based on website and CRM activity. * **Sync accounts into your CRM**\ Automatically push those accounts and their intent signals into Salesforce or HubSpot. * **Build persona-based audiences in Primer**\ Pull in those synced accounts, then add filters for titles, departments, company size, and more to refine targeting. * **Activate across channels**\ Sync your audience to Google, Meta, and LinkedIn for retargeting or new acquisition campaigns. ### Key Benefits: * Target real decision-makers inside in-market accounts * Improve match rates and control over who sees your ads * Reach buyers before they hit competitor funnels --- # 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-legacy/use-cases/6sense-ad-expansion.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.