> 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/hubspot-buyer-intent.md). # HubSpot Buyer Intent ### **Expand Retargeting Audiences Beyond Pixel Limitations** Pixel-based retargeting is becoming less effective due to increasing browser restrictions on cookies, which can reduce your ability to reach previous site visitors. Primer offers an alternative by using HubSpot Buyer Intent data to create custom audiences for platforms like YouTube, LinkedIn, and Meta. This enables more reliable retargeting of high-fit buyers, even when pixel tracking isn't available. For step-by-step guidance, refer to Primer’s [HubSpot Buyer Intent guide.](https://www.sayprimer.com/use-cases/primer-hubspot-buyer-intent) {% embed url="" %} ### How to Convert HubSpot Buyer Intent into Ad Audiences: * **Enable Buyer Intent in HubSpot:**\ Make sure your HubSpot account has Buyer Intent data active (formerly Clearbit, now Breeze). * **Build your audience in Primer:**\ Filter HubSpot records where “record source” contains ‘buyer intent’ and add department and job title criteria to hone in on your ICP. * **Sync to your ad platforms:**\ Push your refined HubSpot intent audience to Meta, LinkedIn, and Google campaigns. Layer with pixel retargeting for maximum coverage. ### Why It Works: * Works even when visitors block cookies or pixels * Expands retargeting audiences beyond traditional pixel limits * Higher match rates and better precision than HubSpot Ads alone --- # 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/hubspot-buyer-intent.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.