LinkedIn Salesforce Integration: Sales Navigator, Lead Gen Forms and Ads Conversions (2026 Guide)

Three LinkedIn Salesforce integrations, not one

Search for “LinkedIn Salesforce integration” and you get three different products mixed together:

• Sales Navigator for Salesforce, owned by sales ops: sellers see LinkedIn inside Salesforce and log outreach as activities.
• Lead Gen Forms to Salesforce, owned by marketing ops: ad form submissions become leads.
• The Conversions API: Salesforce tells LinkedIn Ads which leads qualified and which deals closed.

If you are planning several integrations at once, start with our Salesforce integration guide.

Which one do you need?

Pick the tab that sounds like your problem.

How the data flows

Keeping the three flows apart on paper is the easiest way to avoid loops and double counting.

1. LinkedIn Sales Navigator for Salesforce

This is what most people mean by “Salesforce LinkedIn integration”. It has three parts that are often confused:

• CRM sync. Sales Navigator imports Salesforce accounts, contacts, leads and opportunities, matches them to LinkedIn members and companies, and auto-saves them for the record owners. Sellers then get alerts on people and companies they already own.
• Activity writeback. Seller activity in Sales Navigator is written to the matching Salesforce record (see the table below).
• Embedded profiles and experiences. LinkedIn components on Lead, Contact, Account and Opportunity pages show LinkedIn member and company information without storing it in Salesforce fields.

On top of these, data validation flags contacts who have left their company (the Not at Company flag), and sellers can create Salesforce leads and contacts from Sales Navigator.

Requirements as of October 2026

• Sales Navigator plan: Advanced Plus. LinkedIn’s admin guide says it is required for CRM sync, embedded profiles and data validation.
• Salesforce edition: Enterprise, Performance, Unlimited or Developer. Professional works only with API access and Chatter turned on, which may cost extra from Salesforce.
• One org: LinkedIn’s documentation says you can sync one Salesforce instance per Sales Navigator contract.
• Integration user: LinkedIn recommends a dedicated integration user, not a personal admin login. CRM sync needs read access to the synced objects and fields; writeback needs API write access to Tasks, Notes and Calls.
• Salesforce setup: My Domain enabled before installing the Lightning components.
• Person accounts: supported with the native integration; you choose business or person accounts at setup, and they can’t be mixed in one Sales Navigator dashboard.

What Sales Navigator writes back to Salesforce

According to LinkedIn’s FAQ, writeback never overwrites or merges existing Salesforce data and doesn’t copy LinkedIn profile or company data into your fields. If you want firmographic fields filled in, that is an enrichment job; see our ZoomInfo Salesforce integration guide for that pattern.

How to set up Sales Navigator for Salesforce

Licenses and the integration user come before any install, because a sync tied to a personal login stops when that person leaves. The steps follow LinkedIn’s admin setup guide, which has the current screens.

1. Confirm licensesCheck that the sellers who need the integration hold Advanced Plus seats, and that you have a Sales Navigator admin who also has a user seat to test with.
2. Create the integration userA dedicated Salesforce user owned by the team, with read access to accounts, contacts, leads and opportunities and write access to Tasks, Notes and Calls. If someone leaves, the sync keeps running.
3. Start in a sandboxConnect a Salesforce sandbox first. LinkedIn suggests testing data validation with about 10 contacts, because sandbox timeouts can stop full runs.
4. Install the Sales Navigator packageInstall the LinkedIn Sales Navigator package from AppExchange (now AgentExchange). LinkedIn recommends it over the native option because it unlocks all features, including data validation.
5. Assign permission setsGive non-admin sellers the LinkedIn Sales Navigator Standard User permission set, and add the components to Lead, Contact, Account and Opportunity page layouts in Lightning App Builder.
6. Connect CRM syncIn Sales Navigator, open Admin Settings, then CRM, choose Production, select Salesforce and sign in as the integration user. Choose what to import (auto-save of leads, contacts and accounts) and what to export (lead and contact creation, data validation, activity logging).
7. Review validation rulesSalesforce validation rules on Contact can block the Not at Company flag or make bulk updates fail. Fix or exempt them before turning data validation on.
8. Pilot writebackHave one or two sellers authenticate, send an InMail and log a note, then check that both appear on the right record.
9. Roll outBrief sellers on matching and on the Salesforce sign-in prompt, which LinkedIn says comes back about every 90 days. Expect the first import to take a couple of days to a week; after that, check the CRM sync timestamp in Admin Settings weekly for the first month.

2. LinkedIn Lead Gen Forms to Salesforce

Lead Gen Forms are pre-filled forms inside LinkedIn ads. Submissions stay in Campaign Manager until something moves them, in one of four ways.

If marketing already runs Marketo or HubSpot, route LinkedIn leads through it, so scoring, consent and nurture stay in one place. Our Marketo Salesforce integration and HubSpot Salesforce integration guides cover that second hop.

HubSpot’s knowledge base says new LinkedIn leads can take up to two hours to appear and that the email field must be required on the form for HubSpot to create contacts.

Field mapping for Lead Gen Forms

Map the minimum first, and ask only what sales will use.

How to set up the native Salesforce route

1. Check LinkedIn rolesThe person connecting needs the right role on the ad account and on the LinkedIn Page the ads run from. Missing permissions are a common reason ad accounts don’t show up.
2. Check Salesforce permissionsSalesforce’s documentation says setup requires Modify All Data. Pick a default lead creator with Modify All Data, Send Email and Access Activities: this user receives overflow leads by email.
3. Connect ad accountsIn Lead Settings, turn on Use LinkedIn Lead Sync APIs with Lead Forms (required since December 2024). Then connect your LinkedIn account in Setup to link its ad accounts. If an account is missing or shows NOT_AUTHORIZED, use Refresh Ad Accounts.
4. Map fieldsOn the Lead Gen Fields page, set the default lead creator, record type and Lead Source, and map form fields and custom questions to lead fields. Leads submitted before you connected don’t sync; import them manually.
5. Route the leadsPoint lead assignment rules at the new leads (by country, segment or campaign) so they reach a person or queue, not the default creator.
6. Send a test leadCampaign Manager can send a test lead through a Lead Gen Form. Check the lead, its source, its owner and every mapped field.
7. Repeat after form changesWhen marketing adds a question, refresh the ad accounts and map the new field in Salesforce, then send another test lead.

3. LinkedIn Conversions API with Salesforce as the source

LinkedIn optimizes toward the conversions it sees: if all it sees is form fills, it buys more form fills, including the ones sales rejects. The Conversions API lets you send later outcomes from Salesforce, such as a lead marked qualified or an opportunity won, so reporting and bidding follow pipeline.

Ways to connect Salesforce

As of October 2026, LinkedIn’s help center lists these routes when you create a Conversions API data source in Campaign Manager:

• Salesforce Data 360 (formerly Data Cloud). Listed as a direct partner. Salesforce documents a LinkedIn Conversions API connector in Data 360 that activates conversion events to a conversion rule you create in Campaign Manager. Salesforce lists it as available with the Ad Audiences add-on license, so it fits teams already on Data 360.
• Zapier. LinkedIn lists Salesforce via Zapier: a Salesforce trigger, such as a lead status change, sends an event to a LinkedIn conversion rule. Quick to start, with limited error handling.
• Direct API. Your middleware reads Salesforce changes (Change Data Capture, Platform Events or a scheduled query) and calls LinkedIn’s conversion events endpoint. LinkedIn’s help center estimates two to four weeks on average for a direct integration, plus maintenance.

What a conversion event needs

• A conversion rule in Campaign Manager, associated with the campaigns you want credited. Its type can be Lead, Qualified Lead or Purchase, among others; Marketing Qualified Lead and Sales Qualified Lead are available from the API’s August 2026 version.
• At least one identifier. LinkedIn’s API documentation accepts a SHA-256 hashed email (lowercased and trimmed before hashing), the LinkedIn first-party click ID and the Lead Gen Form response ID. First and last name and a few others also count. Send several to raise the match rate; only matched events count.
• A timestamp within 90 days. The API rejects older events, so send them as they happen, not in quarterly batches.
• An event ID that is unique per conversion, which LinkedIn uses to deduplicate events.

Built by Gilzor

Results we’ve shipped

70+products launched

98%delivered on time

85%clients come back

Aviation33%faster baggage weigh-inWeb and Mobile application for Airlines→Healthcare+30%lab test ordersMedical Lab Web and Native Mobile Applications→Retail · Startup700+stores aggregatedMobile application for Grocery shops→

Talk to the people who build it. Tell us about your project and get a free estimate of scope, timeline and cost.

See how we’d approach yours →

Pitfalls and how to fix them

Data that should not sync

Don’t scrape or bulk-copy LinkedIn profile data into Salesforce fields. LinkedIn’s terms govern it, and embedded profiles show it without storing it.

Keep internal notes out of anything that leaves Salesforce, and send hashed identifiers to the Conversions API. Involve whoever owns privacy before CRM data goes to an ad platform, especially for EU or California contacts.

When a custom integration makes sense

Custom work starts to pay off when:

• LinkedIn leads must update existing contacts or attach to accounts and opportunities, not just create leads.
• You need routing rules the native setting can’t express: territories, round robin across regions, partner leads.
• You want Conversions API events from Salesforce without Data 360, with retries, batching and monitoring that Zapier doesn’t give you.
• You run several Salesforce orgs or business units with separate LinkedIn ad accounts.

A typical build is a small service. It reads form responses from LinkedIn’s Lead Sync API and outcomes from Salesforce Change Data Capture, and posts them to LinkedIn’s conversion events endpoint. A link table of IDs, idempotent writes and failure alerts keep it reliable. Run it as a dedicated integration user, which can sit on one of the limited Salesforce Integration user licenses that supported editions include. If web forms also feed Salesforce, plan them together; see the Salesforce website integration guide.

Only the custom flows above land in these ranges (source: our API integration cost guide). Sales Navigator and Lead Gen setup on their own are mostly configuration and rarely reach them.

Go-live checklist

Some items apply only to one of the three integrations; skip what you aren’t connecting and check off the rest.

FAQ

Where Gilzor fits

Sales ops, marketing ops and paid media each own a piece of LinkedIn, so the first job is deciding which of the three integrations you need and who owns it. We can help with that split. Gilzor builds and maintains Salesforce integrations; we are a software development company, and our people work from Poland and Cyprus.

We set up Sales Navigator sync and Lead Gen Forms routing, build Conversions API feeds from Salesforce, and support them after launch. The Salesforce integration services page describes how we scope such work.