Cognism Chrome Extension in LinkedIn and Sales Navigator

A rep runs a Sales Navigator search, gets 300 results, and starts opening profiles. Somewhere around profile forty the job stops being research and becomes data entry: copy the name, check the title, guess the email pattern, paste it into the CRM, repeat. A browser extension exists to collapse those four steps into one click without leaving the tab. Cognism's Chrome extension does that on LinkedIn, Sales Navigator and LinkedIn Recruiter, and on company websites once one setting is switched on.

Cognism's help centre names the current build "Cognism - Sales Intelligence Extension" on the Chrome Web Store, and treats the older "Cognism - Premium Sales Intelligence" listing as legacy. This piece covers what the extension puts on the page, how a reveal draws down your allowance, how records reach the CRM, and the places where a rep's experience of it stops matching the sales pitch.

People looking for the Cognism app find two things that answer to the name, the web platform you log into and this extension, and only the second one installs anywhere.

Does the Cognism Chrome Extension Work on Company Websites?

Yes, once a setting called Enable Everywhere is switched on. Cognism's help article on company websites says that without it "the extension only appears on LinkedIn and Sales Navigator". With it on, opening a company's site shows firmographic data for that domain, lists the contacts Cognism links to it, and lets you export either to your CRM without leaving the page.

The article is specific about what appears. The company view is based on the domain and can include the company name and industry, company size, headquarters location, revenue range and the technologies the company uses. If Cognism has contacts linked to that domain, the panel lists names and job titles, departments and seniority levels, and whatever email addresses or phone numbers are available. Export works the same way as on LinkedIn: select the company or contact, click Export, choose the CRM fields if prompted, and the record syncs through Cognism.

The setup article adds two controls worth deciding centrally. Auto-open extension opens the panel automatically on supported pages, which some reps will want off, and the panel can sit on the left or right of the screen so it does not cover other tools. Enable Everywhere can also be turned off by anyone who only wants the extension on LinkedIn pages.

Which listing to install

Cognism has two extensions on the Chrome Web Store, and its own help centre says which one to use. Its install guide tells you to search for the Sales Intelligence Extension. Its troubleshooting article covers the error "Your account doesn't have access to the Cognism Chrome Extension. Please sign in with a seat-based user account to continue": the fix is to check the installed extension's name, remove "Cognism Premium Sales Intelligence" as the legacy build, and install the Sales Intelligence Extension instead.

Reading both store listings is worth two minutes, because they are the one Cognism surface where an independent party enforces disclosure.

The two read very differently. The legacy "Cognism - Premium Sales Intelligence" listing, read for this update, shows 40,000 users, a 4.8 rating from 195 ratings and version 4.0.34. The current "Cognism - Sales Intelligence Extension" listing shows 4,000 users, a 4.3 rating from 11 ratings, version 2.0.234 and 1.74MiB, with English as the only language. Both are published by COGNISM Limited under Workflow and Planning.

So the rating most people quote belongs to the build Cognism now tells customers to remove, and the current build has too few ratings to say much about the median experience. Read recent reviews individually rather than either average, because with a browser extension the failures cluster in time: a LinkedIn markup change breaks the overlay for everyone at once, and the ratings from that fortnight are the only public record of it. A recent version number is the property that actually matters here.

Cognism - Sales Intelligence Extension

The build the help centre says to install

• 4,000 users
• 4.3 from 11 ratings
• Version 2.0.234

Cognism - Premium Sales Intelligence

The legacy build it says to remove

• 40,000 users
• 4.8 from 195 ratings
• Version 4.0.34

What It Shows on LinkedIn, Sales Navigator and Recruiter

Cognism's help centre has one article per surface, and they describe the same pattern: open a page, the panel reads it, and the extension shows what Cognism holds for that person or company. On a LinkedIn contact profile the panel can show email addresses, mobile phone numbers, job title and company information and location details; on a LinkedIn company page, headcount and industry, headquarters, revenue range and technologies used. On a Sales Navigator lead profile it shows emails, mobiles, job title and seniority, and on an account page company size, industry, headquarters, revenue range and technologies. On both, if some data is unavailable, the extension shows which fields are missing.

LinkedIn Recruiter gets its own article. There the panel sits beside candidate profiles and can show email addresses, phone numbers, current job title and company and location, plus company size, industry, growth indicators and technology stack for the candidate's current employer. Cognism frames that as moving from sourcing to off-platform engagement faster.

Surface	Person view	Company view
LinkedIn	Emails, mobiles, job title and company, location	Headcount, industry, headquarters, revenue range, technologies
Sales Navigator	Emails, mobiles, job title and seniority	Size, industry, headquarters, revenue range, technologies
LinkedIn Recruiter	Emails, phone numbers, current job title and company	Size, industry, growth indicators, technology stack
Company website	Contacts linked to the domain, with titles and seniority	Name, industry, size, headquarters, revenue range, technologies

The legacy listing, whose own text says "The Chrome Extension works with LinkedIn and Sales Navigator", describes the prioritisation logic explicitly. It offers to help you identify multiple entries into a target account and rank a prospect list on a combination of company fit, the prospect's position and seniority, and whether a mobile number exists for them.

That last input is the one that changes rep behaviour most. Sorting a list by whether a mobile exists is a different activity from sorting by fit, and it quietly reshapes who gets worked first. If your team is email led rather than phone led, that ranking signal is close to noise for you, and it is worth saying so out loud during rollout so reps do not inherit a prioritisation model built for dialling.

On data, the legacy listing claims business emails and DNC-cleaned mobile numbers described as 87% accurate, and scopes that claim to EMEA and the US. The current listing makes a different claim: phone-verified mobile numbers that help you connect with decision-makers ~3x more than standard data. Note the scoping. It is a claim about two regions, so it says nothing about APAC or LATAM coverage, and a team prospecting outside those regions should test rather than assume.

How a reveal spends your allowance

The extension is a window onto the same account and the same wallet as the web app, and Cognism's pricing page sets out the rule in one line: one credit equals one revealed contact. It also states that there is no charge for viewing previously revealed contacts, and that the same credits work across the prospecting platform, Enrich and the API without extra cost.

Three practical consequences follow for a team working LinkedIn.

Reveals are per contact, not per profile view, so browsing is free and clicking is not. A rep who reveals everyone in a search result to see who has a mobile has spent the credits regardless of whether any of those people were ever contacted.

Duplicate work is genuinely free. Two reps landing on the same profile do not pay twice, and neither does the same rep six weeks later, which removes the usual awkward conversation about territory overlap burning budget.

Re-charging is tied to job moves. Cognism's pricing FAQ states that once a contact has been redeemed the record stays usable through the contract, and a credit is only used again if that contact changes jobs. That is a defensible way to charge, since a job move is exactly when the old record stopped being worth anything.

Getting records out and into the CRM

Cognism's integrations page states that you can access prospect details directly within your CRM using the Chrome extension, and lists Salesforce, HubSpot, Pipedrive, Bullhorn and Microsoft Dynamics on the CRM side, Salesloft and Outreach on the sales engagement side, and Zapier for everything else.

Teams weighing a CRM alongside this workflow can see how the two categories differ in Cognism compared to Freshsales, which lays out sourcing versus pipeline management.

The thing to settle before rollout is not whether the push works, it is what it writes. A one-click push from a browser extension is the fastest known way to fill a CRM with duplicates, because the extension is keying off a LinkedIn profile while your CRM is keyed off an email address or an account ID. Decide the matching rule, the ownership rule, and the overwrite rule before a rep sends the first record, or you will be reconciling the result for months. Anyone who has cleaned up after an uncontrolled enrichment push will recognise the pattern, and it is the reason the field-level detail in best data enrichment tools for SDR teams is worth reading before you turn a sync on rather than after.

Where the experience stops matching the pitch

Five things reliably produce the complaint that the extension "is not working", and only one of them is a bug.

The wrong listing is installed. A rep who installed the legacy Premium build sees the seat-based access error quoted above, and the fix is to swap listings rather than to file a bug. The same troubleshooting article lists the other quiet cause: Enable Everywhere is off, so the panel never opens on company websites.

Your package decides what appears. Cognism's pricing page comparison table gives Standard a cross and Pro a tick on exactly three rows: premium mobile filter, mobile verification on demand, and intent data. A rep on Standard looking at a colleague's screen and seeing intent signals they do not have is looking at a Pro account, not a broken install. This is the single most common source of "it shows me less than it shows him", and it is a purchasing fact rather than a technical one.

Coverage is regional, and the vendor says so. The 87% mobile accuracy claim on the legacy store listing is scoped to EMEA and the US. A rep working outside those regions is testing an unclaimed case, and their hit rate is not evidence of a fault.

The extension can only work with what the page renders. The store listing declares that the extension handles authentication information, user activity and website content, which tells you the mechanism: it reads the page. It follows that a surface showing less about a person offers the extension less to match on, and that a rendering change on LinkedIn's side can break the overlay without anything changing on Cognism's. That is a property of every LinkedIn extension rather than a fault in this one, and it is why the update cadence on the listing is a better health signal than the star rating.

Permissions are a real conversation with IT. An extension that reads page content and holds authentication information is a legitimate thing for a security team to ask about. The listing carries a set of declarations to bring to that conversation: the developer declares that data is not sold to third parties outside approved use cases, is not used or transferred for purposes unrelated to the item's core functionality, and is not used to determine creditworthiness or for lending. The developer has also identified itself as a trader under EU rules. Send those declarations and the privacy policy to your security reviewer at the start rather than after the install request gets blocked.

1Install the Sales Intelligence Extension, not the legacy Premium build

2Decide whether reps need Enable Everywhere for company websites

3Confirm which package each seat is on, since three table rows are Pro only

4Agree the CRM matching, ownership and overwrite rules before any export

5Tell reps that browsing is free and revealing is not

6Test the hit rate in your own territory before trusting a regional claim

The compliance point reps get wrong

A DNC-screened mobile number and a compliant call are not the same thing, and neither are a lawfully sourced email address and a lawful send.

Cognism's compliance page states that it collects, processes and shares data under the lawful basis of legitimate interest, as allowed under Section 6.1(f) GDPR, that it notifies business contacts of their inclusion in its database within GDPR timeframes, and that it regularly scrubs its data against 15 major Do Not Call and TPS lists. That is Cognism's compliance with Cognism's processing, and it is real work. It does not transfer to you when you click reveal. Your outreach still needs its own lawful basis, its own country-by-country electronic-marketing check, and its own transparency in the first message. Buying a lawfully assembled record and running a lawful campaign are two separate obligations, and the second one is yours. The detail is in our GDPR compliance guide.

The reason this matters more for an extension than for a bulk export is speed. A rep can go from a LinkedIn profile to a sent message in under a minute, with no list review, no suppression check, and nobody else in the loop. Whatever your compliance process is, it has to survive being that fast, which usually means the controls sit in the sending system rather than in the sourcing step.

Deciding whether it earns its seat

The extension is worth having if your reps genuinely work inside LinkedIn and Sales Navigator all day and your motion values mobile numbers. It is worth much less if your team builds lists in bulk and sends by email, because then the web app and a CSV do the same job with better auditing and none of the browser permissions conversation.

If you are comparing at the extension level rather than the platform level, the lighter tools compete hardest here: Cognism vs Lusha is the closest match on the in-browser workflow, Cognism vs LeadIQ covers the capture-to-sequence angle, and best Cognism alternatives covers the wider field. If email addresses rather than mobiles are what you are actually buying, best email finder tools is the more relevant comparison.

Whatever you install, the extension only ever improves the inputs. Records that arrive faster still need a message worth answering and sending infrastructure that reaches the inbox. If that is the half that is missing, see how a campaign gets built end to end.

Pricing and features are taken from the vendors' own pages. Verify current terms with the vendor before relying on them.