---
name: clay-linkedin-integration
description: Connect Clay and LinkedIn Sales Navigator: what syncs, which editions carry it, the setup order, and the failures to expect. Covers contacts, companies. Use when the user wants to set up, audit or troubleshoot Clay and LinkedIn together, or asks why data is not moving between them.
---

# Clay and LinkedIn Sales Navigator

> Generated from https://www.reversecontact.com/integrations-hub/clay-integrations/clay-linkedin-integration
> Every tier requirement, sync direction and limit below was read from the vendors' own documentation on 2026-10-28.
> Vendors change these without notice. Re-check anything load-bearing before you rely on it.

**What you have to buy first:** Clay Growth or above, a LinkedIn Ads account with billing set up, and a role on that ad account above viewer

**What moves:** contacts, companies, one way, out of Clay.
**How it is built:** native. **Effort:** minutes.

## The short version

Not the integration most people searching for it expect. Clay does not import a Sales Navigator search, and no documented Clay source does: this pair is Clay pushing an enriched audience into LinkedIn Campaign Manager, for targeting or for exclusion. Taken on those terms it is the strongest ads destination Clay has, because LinkedIn is the only one that accepts account audiences as well as people. The constraints are a 300 record floor, a 300,000 ceiling that is the tightest of any destination, a 48 hour wait before the audience is usable, and a Growth plan.

## What each Clay plan lets you build and push

Rows: Clay plan. Columns: What you are trying to do. This is the one grid on the Clay hub that is a staircase rather than a wall, because the three things this pair needs are gated at three different points. Building an audience starts one plan earlier than pushing it anywhere, and building it out of CRM data is capped rather than absent. LinkedIn gates none of it: its side is a permission and a billing account.

| Clay plan | Build an audience | Push it to LinkedIn Ads | Build it from CRM data |
|---|---|---|---|
| Free | Not included | Not included | Not included |
| Launch | Included | Not included | Not included |
| Growth | Included | Included | Capped |
| Enterprise | Included | Included | Included |

- **Included.** Clay's plan comparison gives Launch unlimited Search and CSV upload audiences, and marks Push audiences to ad platforms as unlimited ad audiences on Growth and Enterprise.
- **Capped.** Growth builds audiences from a CRM or a data warehouse up to 250,000 imports. Only Enterprise is unlimited.
- **Not included.** Not available on that plan at any volume.

Counted off that grid, of twelve pairings: six give you included, one gives you capped, five give you not included.

Launch is the interesting row and the trap: you can build the audience and you cannot send it anywhere, so the capability that looks present is the half that does not matter. Growth is the first plan where this pair exists at all, and the only thing Enterprise adds is the ceiling on CRM imports.

## What actually syncs

Direction is written from Clay's point of view: out means out of Clay, in means into it.

| What | Direction | What that means in practice |
|---|---|---|
| A people audience | One way, out | Email, first and last name, company, title and country. Clay hashes the email before upload, so Campaign Manager never receives the address itself. |
| An account audience | One way, out | Company name, domain, website, page URL, stock symbol, city, state, country, zip and up to three industries. LinkedIn is the only Clay Ads destination that takes these. |
| An exclusion list | One way, out | The same audience, used the other way round in Campaign Manager, so you stop paying to advertise to existing customers. Same mechanism, different setting at the LinkedIn end. |
| Refreshed membership | One way, out | Clay keeps audiences current as the underlying data changes, so a row that stops qualifying leaves the audience without anybody rebuilding it. |
| Nothing at all | One way, in | There is no inbound half. No ad engagement, no impressions, no clicks and no leads come back into Clay from this integration, which is why attribution has to be assembled somewhere else. |

## Which field lands where

Two field sets, chosen when the sync is created rather than per run, and one of them exists nowhere else in Clay's ads integrations. The email is hashed before it leaves Clay, so what Campaign Manager receives is a scrambled code rather than the address.

| In Clay | In LinkedIn | What to know about the match |
|---|---|---|
| People audience | LinkedIn matched audience, member | Email, first name, last name, company, title and country. Match rate 60 to 70% on work emails alone. |
| Enhanced matching | Hashed email 1 | Returns up to three ranked candidate personal emails. Only the top-ranked one is sent to LinkedIn, because an upload is one row per email and three would triple the person. |
| Company audience | LinkedIn matched audience, account | Company name, domain, website, page URL, stock symbol, city, state, country, zip and up to three industries. The only Clay ads destination that takes this. |
| Company page URL and domain | The account match | Clay states these match far more reliably than company name alone, so map them when you have them rather than relying on the name. |
| Job title | The title field, possibly truncated | Some fields have character limits. Clay's own advice is a formula column to shorten long titles before mapping. |

**What does not cross:**

- Any ad engagement. Impressions, clicks, form fills and leads do not come back into Clay from this integration, so attribution lives elsewhere.
- Hashed email 2 and 3. They appear as locked chips and are shared with other destinations in the sync, but LinkedIn receives only the first.
- The raw email address. Clay hashes before upload, which is the point: the addresses themselves are not part of what Campaign Manager receives.
- A fourth industry. Company audiences take up to three.

## Connect it, in this order

**Who has to do it:** Somebody with a role above viewer on the LinkedIn ad account, which means admin or campaign manager, plus a Clay builder. The account you authenticate with has to have access to that specific ad account.
**How long:** Twenty minutes to set up, then about 48 hours of LinkedIn processing before you can target anything.

### 1. Check the Clay plan and the LinkedIn billing

*Where:* Clay: pricing

Push audiences to ad platforms reads not included on Free and not included on Launch, and unlimited ad audiences on Growth and Enterprise. On the LinkedIn side you need an active Ads account with billing set up. Both are prerequisites rather than things you can work around, and the LinkedIn one catches teams who have an ad account but have never run a campaign.

### 2. Decide people or accounts, because the sync is built around it

*Where:* Clay: Ads

Go to Ads, click Create ad sync and pick People or Companies. This is where the record type is set for the whole sync. Companies is only worth choosing for LinkedIn, because no other Clay ads destination accepts account audiences, so if this audience is going anywhere else as well you are building two syncs.

### 3. Choose the segment

*Where:* Clay: Select an audience

Pick from the People list or the Company list tab. Check the size here against the 300 minimum and the 300,000 maximum before going further, because those are the two numbers that decide whether the rest of this works.

### 4. Add LinkedIn Ads and authenticate

*Where:* Clay: Sync destinations

Add LinkedIn Ads under Sync destinations and authenticate when prompted, granting Clay permission to create and manage matched audiences. Then pick the destination under Select account. If the connection lapses later, the platform card shows Connection issue or Reconnection required and you reconnect from there.

### 5. Turn on Enhanced matching, and shorten the titles

*Where:* Clay: the field mapping

Enhanced matching adds a hashed personal email and takes the typical match rate from 60 to 70% up to 90 to 95%. While you are in the mapping, add a formula column to shorten long job titles, because some fields have character limits and a truncated title matches nothing useful.

### 6. Wait, and then check the right number

*Where:* LinkedIn: Campaign Manager

The audience appears under matched audiences and takes about 48 hours to process. When it lands, expect LinkedIn's count to be lower than Clay's Matched count: LinkedIn dedupes to member profiles and does not count records that resolve to nobody. That difference is normal and is not a failed sync.

There is nothing installed on the LinkedIn side beyond the authorisation, so disconnecting is a Clay action. The audiences already in Campaign Manager stay there and keep being usable, which is worth knowing before you remove the connection and expect the targeting to stop.

## How to check it worked

- Confirm the segment clears 300 matchable records, not 300 rows. A list of 400 rows matching at 60% does not clear it, and Clay tells you the produced count when it stops.
- Check the audience reached matched audiences in Campaign Manager rather than assuming the sync status is the whole story. The 48 hour processing window sits between the two.
- Compare LinkedIn's member count with Clay's Matched count once, so the permanent gap between them stops being alarming.
- Run one audience as an exclusion before trusting it for targeting. An exclusion list that is wrong costs you nothing, and a targeting list that is wrong spends money.

## When it goes wrong

Each row is a symptom somebody reports, the documented reason, and the fix. Work down it before escalating to either vendor, because most of these are configuration.

| Symptom | Why it happens | What to do |
|---|---|---|
| The sync stops and says the audience is too small | Fewer than 300 matchable records. LinkedIn will not build an audience below that, and Clay checks before uploading rather than after. | Widen the segment or map more identifier fields, which is what the message tells you. Enhanced matching is usually the faster of the two, because it raises the match rate on the rows you already have rather than needing more rows. |
| The audience never leaves Building | LinkedIn processing, which takes about 48 hours. Clay notes specifically that it will not be the 300 record minimum, because that fails before upload. | Wait out the full window before investigating. If it is still building after that, reconnect from the platform card, which shows Connection issue or Reconnection required when the authorisation has lapsed. |
| The match rate is far lower than expected | Work emails with no enrichment. Clay publishes 60 to 70% for work emails alone against 90 to 95% with a hashed personal email added. | Turn on Enhanced matching. For company audiences, map company page URL and domain rather than relying on company name, which Clay states matches far less reliably. |
| LinkedIn shows a smaller audience than Clay sent | Nothing is wrong. LinkedIn reports a deduped member count and does not count records that resolve to no member profile. | Compare against Clay's Matched count once to learn the size of the gap, then stop using audience size as the health check. It will always read lower. |
| A list larger than 300,000 arrived incomplete | The cap trims rather than rejects, so the sync looks successful and the audience is short. | Split the segment across separate syncs. This is the tightest cap of any Clay ads destination, so a list that fits Meta or Google will not necessarily fit here. |
| Title-based targeting is matching the wrong people | Long job titles were truncated by a field character limit, silently, so the value LinkedIn received is a cut-off string. | Add a formula column to shorten titles before mapping them, which is Clay's own documented advice. Check a long title end to end rather than trusting the preview. |

## What breaks, from the vendors' own docs

- **300 matchable records minimum.** LinkedIn will not build an audience below 300 matchable records, and Clay checks it before uploading rather than after. A sync that comes in short stops with a message telling you how many records it produced and to widen the segment or map more identifier fields. That is the better failure, but it does mean a narrow ABM list of fifty accounts is not a LinkedIn audience.
- **300,000 records maximum, and it is the tightest cap Clay has.** Anything above the cap is trimmed rather than rejected, so a larger list has to be split across separate syncs. Clay states this is the tightest limit of any of its ad destinations, with the others taking up to 1,000,000, which makes LinkedIn the one to plan the segmentation around.
- **48 hours before the audience is usable.** LinkedIn takes about two days to finish processing a matched audience. Clay documents this as the answer to an audience that never leaves Building, and specifically notes it will not be the 300 record minimum, because that is checked before upload. Budget it into any campaign date you have promised somebody.
- **Only one hashed email is sent.** Enhanced matching returns up to three candidate personal emails, ranked by how many providers agree. Hashed email 1, 2 and 3 all appear as locked chips and the mapping is shared across every destination in the sync, but LinkedIn receives only the top-ranked one. Clay's reason is sound: an upload carries one row per email, so sending all three would enter the same person in the audience three times.
- **Long job titles truncate silently.** Some fields have character limits, and Clay's advice is to add a formula column to shorten long job titles before you map them. Nothing reports the truncation, so a title-based segment can quietly match on a cut-off string.
- **The count LinkedIn shows is not the count you sent.** LinkedIn reports a deduped member count, below Clay's Matched figure, excluding records that resolve to no profile. Two systems reporting different sizes for the same audience is correct behaviour here, which makes it a poor place to look for evidence that a sync worked.

## The APIs, if you are building around it instead

### Clay

- **Base:** `Configured in the table, not through an API`
- **Auth:** Per-integration, set in the workbook.

| Call | Request | What it does |
|---|---|---|
| `ACTION HubSpot / Salesforce Lookup` | - | Read-only. Pulls records into the table and changes nothing in the CRM. |
| `COLUMN HTTP API` | `POST https://api.reversecontact.com/v2/enrich/persons\nHeaders: { "Authorization": "Bearer rc_...", "Content-Type": "application/json" }\nBody: { "email": "/Work Email" }` | `/Work Email` is a column reference, so each row posts its own value. This is how a provider with no native listing becomes a column. |
| `ACTION HubSpot / Salesforce Update` | - | Writes back. Immediately live to every CRM user. Turn on "ignore blank values" and exclude rep-owned properties. |

**Rules that will cost you time if you skip them:**

- **Clay bills per action on the attempt, not the result.** Effective cost per filled field is the action rate divided by your match rate. Order a waterfall cheapest-first and use conditional runs so the expensive source only sees the residue.
- Import a filtered slice, never the whole portal. Filter on the gap you are filling.
- Run read-only until the columns look right, write to ten rows, open them in the CRM, and only then schedule.

Docs: https://university.clay.com/docs/hubspot-integration-overview

### LinkedIn Sales Navigator

- **Base:** `No public API for this workflow`
- **Auth:** CRM Sync is installed as an app, not called as an API.

**Rules that will cost you time if you skip them:**

- **CRM Sync requires Sales Navigator Advanced Plus**, not Advanced. The embedded profile card runs on Advanced and syncs nothing.
- **It does not backfill.** Only new and updated data syncs after switch-on; history needs an uninstall and reinstall.
- **Field mappings cannot be customised.** Every supported field syncs or none do.
- **Read your contract before extracting anything from search results.** The constraint is contractual rather than technical, so it does not announce itself when you cross it. An agent must not automate scraping here.

Docs: https://knowledge.hubspot.com/integrations/connect-hubspot-and-linkedin-crm-sync

## Filling the record this integration moves

The integration above moves a record between two systems. Neither of them creates what is in it, so a sync that works perfectly still carries whatever gaps the record arrived with. Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record through one API, and returns null with a confidence score rather than a guess.

### Reverse Contact

- **Base:** `https://api.reversecontact.com/v2`
- **Auth:** `Authorization: Bearer rc_your_api_key`. Keys are created in Workspace > API Keys.

| Call | Request | What it does |
|---|---|---|
| `POST /v2/enrich/persons` | `{ "email": "j.okafor@northwind.io" }` | Resolve a person from an email, a name plus company, or a profile URL. Cached resolution, returns in the response. |
| `POST /v2/enrich/companies` | `{ "domain": "northwind.io" }` | Resolve a company from a domain or a name. |
| `POST /v2/fetch/persons` | `{ "linkedInUrl": "..." }` | Standard profile lookup from the database. |
| `POST /v2/fetch/persons/live` | `{ "linkedInUrl": "..." }` | Live on-demand resolution. ASYNCHRONOUS: returns a webhookId to poll, not a record. |
| `POST /v2/search/people` | `{ "filters": { "currentCompanyDomain": "northwind.io" } }` | Filtered people search. 1 credit a profile delivered, and /v2/search/people/count is free. It replaced /v2/search/persons, which returns 410 Gone since 13 October 2026. |
| `POST /v2/search/organizations` | `{ "filters": { "companyDomain": "northwind.io" } }` | Filtered company search. A domain can also go straight to a company through POST /v2/enrich/companies, or through the enrich_company MCP tool since November 2026. |
| `POST /v2/contact/email` | `{ "linkedInUrl": "..." }` | Find an email. ASYNCHRONOUS: returns a taskId to poll. 3 credits for a professional address, 5 for a personal one, 8 for both, refunded when neither is found. |
| `GET /v2/webhooks/:webhookId` | - | Poll an async job until status is "succeeded". Polling is free and does not count against the rate limit. |

Response shape:

```json
{
  "success": true,
  "data": {
    "person": {
      "fullName": "Jane Okafor",
      "headline": "VP Sales at Northwind",
      "location": "London, United Kingdom",
      "linkedInUrl": "https://linkedin.com/in/...",
      "currentPosition": { "title": "VP Sales", "companyName": "Northwind", "startDate": "2023-04" },
      "emails": [], "experience": [], "education": [], "skills": []
    },
    "company": { "name": "Northwind", "domain": "northwind.io",
                 "industry": "Software Development", "employeeCount": 220 }
  },
  "error": null,
  "metadata": { "requestId": "req_...", "executionTimeMs": 480, "updatedAt": "2026-09-01T..." },
  "quotas": { "creditsConsumed": 1, "workspace": { "credits": { "total": 10000, "used": 4521, "left": 5479 } } }
}
```

**Rules that will cost you time if you skip them:**

- A miss returns **null**, not a best guess. Every response carries a confidence score, and you can raise the precision threshold on the request. Branch on it: do not treat a low-confidence answer as a match.
- Use the cached endpoints anywhere that must answer inside one HTTP request. The `/live` endpoints return a task and need polling.
- `quotas.workspace.credits.left` is on every response. Log it, or you will find out about the balance from a 402.
- Credit costs per call are published and a dollar rate per lookup is not: 2 credits for a reverse lookup from an email, 1 for a cached profile lookup, 2 for a live refresh, 3 for a business email and 20 for a direct phone number, with the last two charged only when one is found. Checks and the search count endpoint are free. Credit packs expire after 3 months. Do not hard-code a dollar cost assumption.

**MCP server:** `https://api.reversecontact.com/mcp`

- Auth: OAuth 2.1 where the client supports it, otherwise `Authorization: Bearer rc_your_api_key`.
- Tools: `enrich_person`, `enrich_person_live`, `enrich_company`, `enrich_company_live`, `search_persons`, `search_companies`, `check_usage`, `check_task`
- Streamable HTTP, JSON-RPC 2.0. The `_live` tools return a task id that `check_task` polls.

Docs: https://docs.reversecontact.com/getting-started

## Sources

- Clay: LinkedIn Ads in Clay: https://university.clay.com/docs/linkedin-ads-in-clay
- Clay: sources: https://university.clay.com/docs/sources
- Clay pricing: https://www.clay.com/pricing
- 14 practitioner threads read on 2026-10-28, summarised on the page: https://www.reversecontact.com/integrations-hub/clay-integrations/clay-linkedin-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/clay-integrations/clay-linkedin-integration

---

*Published by Reverse Contact, which appears in this directory as a data provider.
No other vendor pays for placement. Where a vendor publishes no public figure, this file says so
rather than estimating. Reverse Contact costs are stated in credits, which it publishes; no dollar
rate per lookup appears here, because none is published and dividing a pack price is not their number.*
