Clay and LinkedIn Sales Navigator

An enriched audience pushed into Campaign Manager, people or whole accounts.

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.

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 actually syncs

Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.

WhatDirectionWhat 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.

Nothing in that table moves in both directions. Whichever system you treat as the source of record, the other one is downstream of it, and a correction made in the wrong place does not travel.

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 ClayIn LinkedInWhat 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

A few things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.

  • 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.

Every row above travels as a file: five field mappings and four documented exclusions, each one's note, and the three vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.

Field map

The useful reading of this table is that identifiers decide everything here. The difference between a 60% and a 95% match is one more identifier per person, and for accounts it is the page URL and the domain rather than the name, so the enrichment that happens before the sync is the part that determines what the ads reach.

What each Clay plan lets you build and push

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. Pick one on each side and the grid marks the answer.

Pick one on each side.

Clay planBuild an audiencePush it to LinkedIn AdsBuild 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.

How to connect Clay to LinkedIn

Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.

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 it takes
Twenty minutes to set up, then about 48 hours of LinkedIn processing before you can target anything.
Setup checklist 0 of 6 done

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.

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.

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.

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.

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.

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.

Hand it to an agent instead

The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at this pair as a skill and it has the whole pair without reading two sets of vendor docs first.

curl -o .claude/skills/clay-linkedin/SKILL.md https://www.reversecontact.com/integrations-hub/skills/clay-linkedin.md

What breaks, and what nobody tells you

Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.

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.

Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.

The 6 failures people actually hit

Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.

01

The sync stops and says the audience is too small

WhyFewer 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.

02

The audience never leaves Building

WhyLinkedIn 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.

03

The match rate is far lower than expected

WhyWork 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.

04

LinkedIn shows a smaller audience than Clay sent

WhyNothing 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.

05

A list larger than 300,000 arrived incomplete

WhyThe 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.

06

Title-based targeting is matching the wrong people

WhyLong 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.

If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The same symptom on another pair is often the same cause, so the directory indexes all of them by the message rather than by the integration.

When this is the right integration

Set it up when

  • An enriched segment should become an ad audience without a CSV in between
  • You want to advertise to whole accounts rather than to named individuals
  • Existing customers should stop seeing acquisition ads

Do not bother when

  • The segment is smaller than 300 matchable records
  • Your CRM already syncs ad audiences natively and the enrichment can happen there
  • You need ad engagement back in Clay, which this integration does not send

The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.

What practitioners say about it

Searched for this pair by name, in the words a person would use. 14 threads from March 2026 to August 2026 were read in full on 28 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.

The CRM may already do this, which is the real alternative

Yeah but I think 90% of the customers have Salesforce and HubSpot and they both natively sync ad audiences. You could essentially enrich the data and clay push it to your CRM and from your CRM you can push it to your ad platforms and then track the downstream impact with clay audiences. You can't even actually track the downstream impact of any of those things

r/SaaSMarketing·March 2026·1 points

The most useful thing said about this integration anywhere, and it is the argument against building it. If you run Salesforce or HubSpot, enriching in Clay and letting the CRM talk to LinkedIn is one connection fewer to own. The case for doing it from Clay is the account audience, which the CRM route does not offer, and the closing complaint about downstream impact is accurate: nothing comes back from this sync.

Two destinations, and people keep asking for a third

No just LinkedIn meta.

r/gtmengineering·March 2026·1 points

Answering somebody asking about Reddit ads. Clay's pricing page describes the feature as sending ad audiences to LinkedIn and Meta, which matches, and LinkedIn is the only one of the two that accepts account audiences. Worth knowing before you design a cross-platform audience strategy around it.

Match rate is the currency, not the connection

There are a couple of options for Reddit currently but the match rates are super low even with solid identity graphs

r/gtmengineering·March 2026·1 points

Said about another platform and true of this one. The published figures here are 60 to 70% on work emails and 90 to 95% with a hashed personal email, which is the difference between clearing the 300 record floor and not. An audience sync is only as good as the identifiers behind it, whoever is receiving them.

Somebody is already sceptical of the headline number

Curious to hear that too! Clay claims to have improved their CPL by a 10X ratio, that seems a bit too good to be true

r/PaidSocialAdvertising·August 2026·1 points

Quoted because the scepticism is the right instinct and because this directory applies it too. A tenfold cost-per-lead improvement is a vendor marketing figure, not a documented limit, and it is not repeated anywhere on this page. The numbers here are the ones Clay publishes in its documentation: the match rates, the 300 floor, the 300,000 ceiling and the 48 hours.

The recurring objection to Clay, applied to ads

Everything in Clay seems to be "something you can do yourself", but they charge for the convenience and integration.

r/gtmengineering·March 2026·1 points

True here in a specific way: you could export a CSV and upload it to Campaign Manager by hand, which is what this replaces. What you are buying is that the audience stays current as the data changes, and that you are not maintaining the same segment definition in two systems. Whether that is worth the Growth plan is the question this page cannot answer for you.

What the threads add up to

Finding these took a fix to the research tooling rather than a wider search. Queries are built from the tool record's display name, which is LinkedIn Sales Navigator, so every harvest of this pair searched prospecting and returned threads about Sales Navigator with not one mention of a matched audience. Searching it as Clay plus LinkedIn Ads found the right threads immediately, and they are small: this is a feature people are still deciding about rather than one they have war stories from.

None of these five is a number this page relies on, which is the right relationship: the floor, the ceiling, the match rates and the processing window all come from Clay's own documentation. What the threads add is the alternative route through the CRM and a healthy suspicion of the marketing figure, neither of which a vendor page would tell you.

The longer answer

Read the direction before anything else, because this pair points the opposite way from what its name suggests. Nothing comes back. There is no ad engagement, no click and no lead returning into Clay from LinkedIn, so this is a publishing step rather than a sync, and any closed loop you want has to be assembled from the CRM and the site rather than from here. The practitioners in the threads below describe exactly that gap.

The reason to choose LinkedIn over Clay's other ad destinations is the account audience, and the reason to be careful is the size band. Three numbers decide whether this is worth building:

  • 300 matchable records, below which LinkedIn will not build the audience and Clay stops before uploading.
  • 300,000 records, above which the list is trimmed, and which is the tightest of any Clay ads destination.
  • 60 to 70% match on work emails alone, against 90 to 95% with Enhanced matching adding a hashed personal email.

Those combine into a practical floor that is higher than it looks. A segment of 400 rows matching at 60% produces 240 matchable records and no audience at all, so the enrichment is not a refinement here, it is what gets you over the line.

The honest alternative is worth stating, because a practitioner states it better than we would: Salesforce and HubSpot both sync ad audiences natively, so a team already running one of those can enrich in Clay, push to the CRM, and let the CRM talk to LinkedIn. That is one fewer connection to own and it reuses a sync somebody has already tested. The case for doing it from Clay is the account audience, which the CRM route does not give you, and not having to keep a segment definition in two places.

Checked by

Reverse Contact

We sell B2B people and company data, and we publish this directory. Every tier requirement, sync direction and limit on this page was read from a vendor's own knowledge base, developer documentation or pricing page on the date below. Nothing on it is restated from a press release or a third-party listing.

Where a vendor publishes no public figure, this page says so rather than estimating, which is why no page here prints a cost per enriched record. Reverse Contact appears in this directory as a data provider and publishes it. No other vendor pays for placement, and every link out of a listing or a citation carries nofollow, including the ones that point at Reverse Contact. The only followed links on this page are the two calls to action and the reviewer.

Tier requirements, sync behaviour and documented limits change without notice. Confirm against your own contract before you budget. What has changed since · How we checked, and what we will not claim

Researched and written by

Eugene Suslov

Researched and wrote every page in this directory, and checked every tier requirement, sync direction and documented limit against the vendor's own knowledge base, developer documentation or pricing page.

Verified
2026-10-28
Sources
3 vendor documents
Paid placement
None

The integration moves the record. Something has to fill it.

Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under Clay, LinkedIn and everything else in this directory, and it returns null with a confidence score rather than a guess.

Free trial, no card required, and 500 credits to start.

Clay and LinkedIn, asked and answered

Is there a Clay LinkedIn integration?

There is, and it is probably not the one you are looking for. The Clay LinkedIn integration pushes audiences out to LinkedIn Campaign Manager for ad targeting. It does not import a Sales Navigator search: Clay's documented table sources are CRM systems, webhooks, CSV files and Clay's own Find People, and there is no LinkedIn or Sales Navigator source among them. If you came here to get Sales Navigator data into a table, the honest answer is that this integration does not do it and the LinkedIn hub explains why almost nothing does.

What can it actually send?

Two kinds of audience. A people audience carries email, first and last name, company, title and country. A company audience carries company name, domain, website, page URL, stock symbol, city, state, country, zip code and up to three industries. LinkedIn is the only Clay Ads destination that accepts account audiences at all, which is the reason to pick Companies here rather than anywhere else.

What match rate should I expect?

Clay publishes two figures. Work emails alone typically match 60 to 70%. Running Enhanced matching, which adds a hashed personal email, typically takes it to 90 to 95%. Those are Clay's numbers for LinkedIn rather than a promise about your list, and the gap between them is the whole argument for enriching before you sync rather than after.

Why is my LinkedIn audience smaller than the number Clay sent?

Because LinkedIn reports a deduped member count. It resolves the records you sent to member profiles, counts each person once, and does not count records that resolve to no profile at all. Clay documents that this usually sits below the Matched count it reports for the same run, so the two numbers disagreeing is the expected state rather than a fault.

Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.

Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.

Ask an assistant