> 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/linkedin-audience-efficiency.md). # LinkedIn Audience Efficiency ### **Drive Higher-Quality B2B Leads by Syncing Your ICP to LinkedIn** LinkedIn Ads offer strong targeting capabilities, but native filters can sometimes include roles or titles that don’t closely align with your ideal buyers—especially in B2B campaigns. Primer enables you to define your Ideal Customer Profile (ICP) more precisely outside of LinkedIn and then sync that refined audience directly into your ad campaigns. This approach helps improve targeting accuracy and lead quality. For more details and performance benchmarks, refer to [Primer’s LinkedIn Efficiency guide.](https://www.sayprimer.com/use-cases/primer-linkedin) {% embed url="" %} ### How to Build and Sync ICP Audiences for LinkedIn: * **Create your ICP audience in Primer:**\ Define your ideal companies, departments, seniorities, and titles. Preview your audience to ensure quality before syncing. * **Sync the audience to LinkedIn:**\ Push your custom audience into LinkedIn as a matched list. Note: full population can take up to 72 hours. * **Run a test campaign:**\ Compare LinkedIn’s native targeting vs. your synced ICP audience by running A/B tests. * **Track performance:**\ Measure form completions, qualified leads, CPL, CPM, and CPA over 1-2 weeks to evaluate impact. ### Why It Works: * LinkedIn’s native filters are good—but can be too broad * Primer’s synced audiences offer tighter control and precision * Avoid “close but wrong” titles for better lead quality and ROI --- # 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/linkedin-audience-efficiency.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.