How to push LinkedIn leads into Salesforce (2026 setup guide)

There are two answers, because "LinkedIn leads" means two things. Lead Gen Form submissions from LinkedIn Ads sync into Salesforce natively. You connect a LinkedIn member account in Salesforce Setup under LinkedIn Lead Gen, set lead defaults, and map fields. New submissions then arrive as Leads automatically. People your reps find in Sales Navigator are different. Sales Navigator has no CSV export, so you either use CRM Sync with Lead/Contact Creation on the Advanced Plus plan, pushing one record at a time, or you use a third-party tool.

Which kind of LinkedIn lead do you mean?

Get this straight first. The two kinds share a name and almost nothing else.

If you run ads, most of this page is about the first row. If you prospect, skip to the Sales Navigator section.

How do I sync LinkedIn Lead Gen Form leads into Salesforce?

The steps below follow Salesforce Help's "Generate Leads from LinkedIn Lead Gen Ads" page as of October 2026. Budget an afternoon if your permissions are already sorted. The field mapping takes longer than the connection itself.

Before you start

Check three things.

1. LinkedIn role. You need the Lead Gen Form Manager or Designated Admin role on the LinkedIn page. Without it you get a "Not Authorized" error.
2. Salesforce permissions. The user you set as Default Lead Creator needs Modify All Data, Send Email and Access Activities. Grant them through a permission set or through a user profile. Salesforce warns against combining the two.
3. Edition. One third-party guide says you need a Sales Cloud org. We could not confirm the full list of eligible editions, so check the Required Editions box on the Salesforce Help page before you start.

The setup, in order

1. In Salesforce Setup, type "LinkedIn Lead Gen" into Quick Find. In Lightning this sits under Platform Tools, Feature Settings, Marketing, LinkedIn Lead Gen.
2. Connect a LinkedIn member account. Salesforce connects every ad account tied to that member, and every form on those ad accounts starts generating Leads. Salesforce recommends a member account that is associated with all your ad accounts and company pages. Otherwise some forms will silently not sync.
3. Under Set Lead Defaults, fill in Default Lead Creator, Record Type and Lead Source. Set Lead Source to something like "LinkedIn Lead Gen" so you can report on it later.
4. Open Lead Gen Fields and map LinkedIn fields to Salesforce fields.
5. To use work email instead of personal email, un-map the default email field, choose "Work Email" and save.
6. Submit a test lead on a live form and confirm it lands with the right owner and source.

A note on menu paths. Some vendor blogs describe starting from Campaign Manager instead, under Admin Settings or a CRM setup menu. Both routes may exist. Those posts are one to two years old, so check LinkedIn's current CRM integration help page if the menus don't match.

The hidden field trap

This one is in Salesforce's own documentation and it catches people. Salesforce sorts LinkedIn hidden fields alphabetically by field name before it writes values to your mapped fields. The first hidden field alphabetically always goes to the first mapped field. Map them in a different order and your campaign ID ends up in your sales rep field.

The fix is boring. Name your hidden fields deliberately, list them A to Z, and map them in that order.

Custom questions and identifiers

LinkedIn sends its data fields over as text. Plan your Salesforce fields around that:

• Create text custom fields for the LinkedIn identifiers you care about: lead, creative, form, campaign and account IDs.
• Create two custom fields per custom question, one for the question and one for the answer. If you change the question wording later, you still know what the answer meant.

What are the limits on LinkedIn Lead Gen Forms?

These limits shape what you can send to Salesforce in the first place. The first two rows come from LinkedIn's help. The rest come from a 2026 vendor summary by LeadSync, not LinkedIn's own page.

LinkedIn itself recommends three to four fields. Fewer fields usually means more submissions, and Salesforce can enrich the rest later. If you are tempted to collect everything on the form, read our piece on lead enrichment waterfalls first.

Do UTM parameters come through to Salesforce?

Not on their own. A Lead Gen Form is not a landing page, so the UTMs on your ad URL do not ride along the way they would with a web form. Hidden fields solve this. LinkedIn says hidden fields can carry static or dynamic values like UTM source, ad set ID or the sales rep who owns the account, and those values sync to your CRM. Set them per form, then map them, alphabetically.

How long does LinkedIn keep the lead data?

Sources disagree and we could not confirm the current figure. An older LinkedIn marketing blog post said lead data stays available for 90 days and is then deleted. That post is several years old. Treat 90 days as the safe assumption and don't rely on LinkedIn as a backup.

This matters because of the backfill rule. Leads submitted before you connect Salesforce don't sync automatically. You have to download and import them by hand, ideally the same day you connect. Also note that Salesforce can register only one environment, sandbox or production, per LinkedIn ad account at a time. Test in sandbox, then reconnect to production, and expect a gap while you switch.

How do I get Sales Navigator leads into Salesforce?

This route is slower. Sales Navigator has no CSV export of leads or accounts. The sanctioned exit is CRM Sync. On the Advanced Plus plan, CRM Sync includes Lead/Contact Creation, which lets a rep create a Salesforce record from a Sales Navigator profile. It works one record at a time. We don't have a verified 2026 price for Advanced Plus, so ask LinkedIn for a quote.

The manual alternative is a rep copying name, title, company and LinkedIn URL into a new Salesforce Lead. Call it two to three minutes per record if they also look up an email, which adds up fast. Our post on manual prospecting time covers which parts are worth automating. Records entered by hand also go stale. People change jobs and the Lead never updates, which is the problem in outdated prospect data.

Third-party tools fill the gap between those two options. If you are weighing them, our Sales Navigator alternatives roundup is a starting point. Be careful with scraping extensions, since they put the rep's LinkedIn account at risk.

Where does the sync usually break?

Once leads are flowing, the next problem is speed. A form fill that sits unworked for two days goes cold. Our post on speed to lead covers response timing.

Where Saava fits

Saava doesn't replace the LinkedIn Lead Gen sync, and nothing on this page needs it. Saava works earlier in the process. It finds people showing buying signals on LinkedIn, scores them against your ICP and sends outreach from the LinkedIn account or email you connect yourself. If your real question is "which LinkedIn people are worth putting in Salesforce at all," that is the part we cover. See our LinkedIn intent data guide and lead scoring for LinkedIn engagement.

FAQ

Can I export leads from Sales Navigator as a CSV?

No. Sales Navigator has no CSV export of leads or accounts. The sanctioned route into Salesforce is CRM Sync, with record creation on the Advanced Plus plan.

Will leads from before I connected Salesforce sync over?

No. Leads submitted before the connection don't sync automatically. Download them from LinkedIn and import them manually, and do it soon, because LinkedIn may delete lead data after about 90 days.

Why are my hidden field values landing in the wrong Salesforce fields?

Salesforce writes hidden fields in alphabetical order by field name. Map them to your Salesforce fields in that same order.

Can I connect both a sandbox and production org to the same ad account?

Not at the same time. Salesforce registers only one environment per LinkedIn ad account, so test first and then switch.

Do I need middleware like Zapier for this?

Not for ad leads, since the native sync covers them. Middleware makes sense if you need logic the native mapping can't do, or a CRM setup the native route doesn't support.

If you want the people worth syncing found and contacted for you, start a trial