> 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/crm-retargeting.md).

# CRM Retargeting

CRM retargeting gives your sales team additional air cover by syncing MQLs and SQLs from HubSpot or Salesforce into paid media channels. This keeps your brand in front of prospects across LinkedIn, Meta, Google, and YouTube—improving demo show rates and supporting sales motion beyond email.

Explore Primer’s [CRM Retargeting](https://www.sayprimer.com/use-cases/crm-retargeting) guide to learn how to re‑engage and convert more leads.

{% embed url="<https://youtu.be/DvUNJSWymS8>" %}

### How It Works:

* **Import leads from your CRM into Primer**\
  Select leads at key stages (e.g., MQLs, SQLs) and import them from HubSpot or Salesforce. You can segment by stage, industry, or engagement level to refine your audience.
* **Sync to ad platforms**\
  Send your audience from Primer into LinkedIn, Meta, Google, and YouTube as custom audiences. If your list is small, consider combining similar stages to meet minimum audience size for delivery.
* **Launch supporting ad campaigns**\
  Run ads aligned with sales and marketing goals:
  * Demo reminder campaigns
  * Case study promotion
  * Warm-up ads between meetings
* **Measure impact**\
  Use CRM tracking to monitor conversion lift at different stages:
  * Discovery call attendance
  * Demo progression
  * Closed-won rates
  * Primer’s built-in holdout testing helps isolate ad-driven impact.

### Key Benefits:

* Extend touchpoints beyond email to keep prospects engaged
* Support sales outreach with aligned messaging
* Improve lead progression with minimal manual effort
* Achieve higher match rates with synced audiences


---

# 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/crm-retargeting.md?ask=<question>&goal=<user_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.