LiHelper Connector: the LinkedIn analytics Chrome extension

Syncs your LinkedIn analytics to LiHelper from your own browser session. No password or cookie ever leaves your browser.

LiHelper Connector is a free Chrome extension that reads the analytics LinkedIn shows you — impressions, engagements, followers, profile views and per-post stats — inside your own logged-in tab and sends only those numbers to your LiHelper dashboard. It exists because LinkedIn's official API does not expose personal-profile analytics to third parties, so the safest way to get real numbers is to read them where you already see them: in your browser, as you, on your IP. It never runs in the background, never touches your password or cookie, and needs only the storage permission plus access to linkedin.com. Install it from the Chrome Web Store.

Add LiHelper Connector to ChromeFree · works on every plan, including Free

What it does: personal-profile LinkedIn analytics the official API does not expose

  • Syncs your analytics. On your LinkedIn analytics pages, click "Sync everything" and the extension reads your impressions, engagements, followers, profile views and per-post stats, then sends only those numbers to your LiHelper dashboard. That data feeds the Performance trends card and your personal best-time model.

  • Drafts comments you review. On a post in your feed, "Draft comment" sends the post text to LiHelper and returns an on-brand comment for you to read, edit and post yourself.

  • Runs actions you queued (Pro). Likes and comments you approved in LiHelper run in your own session when you click "Run pending actions". Only confirmed actions count, and the server caps them per day.

  • Easy Apply assist (Pro). On a job page, "Apply to this job" fills the Easy Apply form with your saved details and stops at the review step for you to submit. It never guesses a screening question.

The six "Sync everything" steps

One click runs six steps in order, each on a LinkedIn page you could open yourself. The extension opens the page, reads it, merges the result and pushes everything to your account once at the end. Two of the steps (your profile and your skills) open in a visible tab because LinkedIn only renders those cards as they scroll into view; your previous tab is restored afterwards. Later syncs finish in seconds because most of the history is already stored.

  1. Overview — linkedin.com/analytics/creator/

    Post impressions, total followers, profile views and search appearances — the headline numbers on your creator analytics page.

  2. Content analytics — linkedin.com/analytics/creator/content/

    Impressions and engagements across every time range (7, 14, 28, 90 and 365 days) plus the discovery figures LinkedIn shows: members reached, reactions and comments.

  3. Post stats — linkedin.com/analytics/creator/top-posts/

    The full per-post list for the past year — impressions, engagements and the date each post went out — so your best-time model has real history to learn from.

  4. Posts — linkedin.com/in/me/recent-activity/all/

    The text, posted date and, where shown, the reactions, comments and reposts of your own recent posts. Plain reposts are skipped. This is what the AI uses as examples of your voice.

  5. Your profile — linkedin.com/in/me/

    Your headline, current role and company, About text, connections count and the Pages you administer, so Autopilot topics come from your real job rather than a generic industry list.

  6. Your skills — linkedin.com/in/me/details/skills/

    Your full skills list. Combined with the profile step, this is what makes the drafts profile-driven instead of template-driven.

What it never does

  • Never reads or sends your LinkedIn password or session cookie — it has no code path that touches either.
  • Never runs in the background: no timer, no tabs permission, no activity after you close the popup.
  • Never loads remote code. Everything is bundled in the package you install; there is no eval and nothing fetched at runtime.
  • Never reads other websites. It has host access to linkedin.com and the LiHelper API only, not <all_urls>.
  • Never scrapes other people: it reads your own analytics, your own profile and the text of a post you personally chose to act on.
  • Never submits a guessed Easy Apply answer, and never clicks Post on a Page for you — you do.
  • Never exceeds the daily caps, because the server, not the extension, hands out every action.

The full picture of where each LiHelper feature runs, and the daily caps and circuit breaker behind the Pro actions, is on the security page.

Permissions, explained

These are the permissions the extension requests and the justification we gave Chrome Web Store review for each one, word for word. If a future version needs anything more, the store will ask you before it updates.

Chrome permissions requested by LiHelper Connector and why each is needed
PermissionWhy it is needed
storageStores the user's LiHelper account-link token, the time of their last sync and a cached copy of their own LiHelper profile card locally, so they don't re-enter the token each time. Nothing else is stored.
Host: https://www.linkedin.com/*Needed to read the user's own analytics numbers and post text on LinkedIn pages they have open, and to perform the like/comment/apply actions the user explicitly triggers, inside their own session.
Host: https://api.lihelper.com/*The LiHelper API. The extension sends the synced analytics numbers, post text for comment drafting, and action outcomes to the user's own LiHelper account, authenticated by their token.
Content scripts on linkedin.com/analytics, /dashboard, /in/Read the user's own analytics and profile numbers when they click Sync.
Content scripts on linkedin.com/feed, /in/, /posts/Show the "Draft comment" button and run the like/comment actions the user queued.
Content script on linkedin.com/jobsPre-fill the Easy Apply form when the user clicks "Apply to this job".
Content script on linkedin.com/company/*Pre-fills the Page admin composer with the post the user queued in LiHelper, ONLY after they click "Post as Page" in the popup; the user clicks LinkedIn's own Post. Inert on every other visit to a company page.
externally_connectable (lihelper.com, www.lihelper.com, lihelper.vercel.app)Lets the LiHelper web app ask the extension whether it is installed, to show a correct setup status. No data flows through it.

Remote code: none. All code is bundled in the package; there is no eval and no remotely loaded script. The data it collects is limited to your LinkedIn member ID and display name (to link the accounts), your LiHelper account token (your own app, not LinkedIn credentials), and the website content described above: your own analytics numbers, profile fields, the text of posts you choose to draft comments on, and Easy Apply form fields you choose to fill. It does not collect health, financial, location, web-history, keystroke or messaging data. Details are in the Privacy Policy.

Install and link it in two steps

Version 0.3.9 is current — see what changed in each release on the changelog.

  1. Step 1 — Install the extension

    Open LiHelper Connector on the Chrome Web Store and click Add to Chrome. The store keeps it up to date automatically. If you cannot use the Web Store, the app's Extension page offers a zip you can load unpacked from chrome://extensions with Developer mode on; manual loads do not auto-update, so the popup will tell you when a new version is out.

  2. Step 2 — Link it to your account

    In LiHelper go to Settings → Connect the browser extension, generate a token and copy it. Open the extension popup, paste the token and click Link account. The token is stored locally in the extension, is shown once, and can be revoked at any time from the same Settings page. Then open any LinkedIn page and click "Sync everything".

Once linked, the web app can detect that the store version is installed (through the externally_connectable permission above) and marks the setup step done. Sideloaded copies have a different ID and complete the step by syncing instead.

Which plans include it

All of them. Analytics sync through the extension is part of the Free plan, alongside scheduling, drafts and the calendar, so you can see real numbers without paying anything. Creator adds the AI post generation and designed images that turn those numbers into drafts in your voice; Pro adds the in-session actions the extension assists with — approved likes and comments within daily caps, and Easy Apply assist. Compare them on the pricing page, or read how LiHelper works to see where the synced data goes.

Extension FAQ

What does the LiHelper Connector read from LinkedIn?

Only your own pages. On "Sync everything" it reads impressions, engagements, followers, profile views and per-post stats from your analytics pages, your recent posts from your activity page, and your headline, current role, About text, skills and the Pages you administer from your profile. It sends those values to your LiHelper account and nothing else — never your password, cookie, messages or other people's profiles.

Is the extension free, and do I need a paid plan?

The LiHelper Connector is free on the Chrome Web Store and works on every plan, including Free ($0, no card). Analytics sync is available to everyone. The Pro-only features it assists with — running approved likes and comments, and Easy Apply assist — need a Pro plan, but the extension itself never charges anything and never changes what plan you are on.

Does the extension run in the background?

No. It has no timer, no tabs permission and no background job. It acts only when you click a button in its popup or on a LinkedIn page you already have open, and it stops when that action finishes. Auto-publishing on Pro does not use the extension at all; scheduled posts go out through LinkedIn's official API from the server.

Is a LinkedIn analytics Chrome extension safe for my account?

Reading your own analytics in your own logged-in tab is the lowest-risk way to get numbers LinkedIn's API does not expose: nothing acts as you from a server, and no cookie is copied anywhere. The in-session actions on Pro carry more risk and are capped per day by the server. The security page explains what runs where and what LiHelper refuses to do.

Does it work in browsers other than Chrome?

It is built and tested for Chrome and distributed through the Chrome Web Store. We have not verified it on other Chromium browsers, so we do not promise support for them. Everything else in LiHelper — writing, scheduling and publishing posts — works in any modern browser without the extension.

LiHelper is an independent product and is not affiliated with, endorsed by, or sponsored by LinkedIn. Something not syncing? Email support@lihelper.com with the version shown in the popup, or see the contact page for what to include. Ready to start? Add LiHelper Connector to Chrome, then create your free account.