> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/account-intelligence/workflows/workflow-template/linkedin-high-intent-audience-sync.md).

# LinkedIn High-Intent Audience Sync

### Business Question

**Which hot accounts should we retarget on LinkedIn ads (or any other ad platform), and how do I keep that audience list fresh without manual updates?**

Your Intent Score tells you who's buying. Your LinkedIn Campaign Manager audience determines who sees your ads. This workflow syncs them automatically — every day, your hottest prospects see your ads without you ever touching the list.

#### Use Case

LinkedIn ads work best when you're reaching accounts that are actually in-market. Manually updating your Campaign Manager audience is error-prone and takes time. This workflow automates it.

Every day at your chosen time, HockeyStack queries your hot/on-fire accounts view and syncs those account names to a LinkedIn Campaign Manager audience. Your marketing team runs ads against that audience. As accounts cool down and drop out of the view, they're removed from the audience. The audience is always fresh.

### How to Set Up

#### **Step 1: Create a High-Intent View**

Go to **Companies → Views** and create a new view. Name it something like `Hot Accounts` if you segment by region.

**Apply these filters:**

| Filter                       | Value                                              | Why                                                     |
| ---------------------------- | -------------------------------------------------- | ------------------------------------------------------- |
| **Intent Score**             | Hot, On Fire                                       | Strong buying signal                                    |
| **Is In Stage**              | No Current Stage (or specific stages to re-engage) | Don't alert on accounts already in deals                |
| **Company Type**             | Prospect, Lead                                     | Exclude customers                                       |
| **Optional: Exists in CRM**  | Not exist in CRM                                   | Surface accounts Sales don't have visibility to via CRM |
| **Optional: Geography**      | Your region/country                                | Segment alerts by team                                  |
| **Optional: Employee Count** | Your ICP range                                     | Further qualify                                         |

#### **Step 2:** Create a New Workflow

Go to **Workflows** and click **+ New Workflow**.

* **Name:** `LinkedIn Sync - High Intent Accounts`
* **Source:** Select the high-intent view you just created
* **Execution Mode:** **Scheduled**
* **Schedule:** Everyday

<figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2FK30iXph3bRZ6MImkoN53%2FScreenshot%202026-09-10%20at%2012.42.21%E2%80%AFPM.png?alt=media&amp;token=512a9b20-1103-4ae7-8ae8-220daf952252" alt=""><figcaption></figcaption></figure>

#### **Step 3: Connect LinkedIn and Create/Select an Audience**

Click **+ Add Node** and select **LinkedIn**.

**Configure the LinkedIn node:**

| Setting              | Value                                               |
| -------------------- | --------------------------------------------------- |
| **LinkedIn Account** | Select your Campaign Manager account                |
| **Sync Type**        | Account (company-level targeting)                   |
| **Audience Name**    | `[Company Name] - High Intent` or `HI_Companies_GH` |
| **Audience Action**  | Create new or sync to existing audience             |

**Important:**

* Use **Account sync** (not Contact sync) since you're building a company audience
* Name the audience something descriptive so your marketing team knows what it is

<figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2FO6VOUzgPfz60f8lyS6aF%2FScreenshot%202026-09-10%20at%2012.44.57%E2%80%AFPM.png?alt=media&amp;token=726f8f13-72e6-4a0f-8f79-017735b0d0b2" alt=""><figcaption></figcaption></figure>

#### **Step 4: Enable and Test**

* Click **Enable** to turn on the workflow
* Click **Run Now** to execute immediately and test
  * You can also do "Dry Run", "Run Once", or "Run Once For a Single Record" for testing
* Go to your LinkedIn Campaign Manager → Audiences, verify the audience was created/updated with the right account count
* Create a test ad campaign targeting that audience to confirm it works

###

### Common Variations

**Variation A: Exclusion Audience (Dual Setup)**\
Create a second workflow:

* **View:** Filter to those Is Not In Closed Won
* **LinkedIn node:** Sync to a separate exclusion audience (e.g., `HI_Exclusions_Customers`)
* Your marketing team then uses this as an exclusion list in their campaigns
* Result: Hot prospects see ads, existing customers don't

**Variation B: Intent Tiers (Hot + On Fire Separately)**

* Create two views: one for `On Fire` only, another for `Hot + On Fire`
* Create two workflows syncing to two LinkedIn audiences
* Marketing team can bid differently on each tier (higher spend on On Fire)

**Variation C: Contact-Level Audience (Buying Committee)**

* Switch sync type to **Contact** instead of Account in LinkedIn node
* Run Contact Discovery first to identify decision-makers per account
* Result: Ads reach CEO/CFO/VP Sales at hot companies, not just the company
* Requires Contact Enrichment node to populate email/LinkedIn fields first

**Variation D: Weekly or Monthly Sync**

* Change schedule to **Weekly** or **Monthly**
* Use if you want slower list churn or have lower volume
* Trade-off: less fresh, but cheaper on LinkedIn API calls


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hockeystack.com/account-intelligence/workflows/workflow-template/linkedin-high-intent-audience-sync.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
