Linkedin Posts Engagers (Likers and Commenters) ✅ No cookies ✅ avatar

Linkedin Posts Engagers (Likers and Commenters) ✅ No cookies ✅

Pricing

from $1.10 / 1,000 results

Go to Apify Store
Linkedin Posts Engagers (Likers and Commenters) ✅ No cookies ✅

Linkedin Posts Engagers (Likers and Commenters) ✅ No cookies ✅

Extract Likers and Commenters from LinkedIn Posts – 100% Public Data, No Login or Cookies! Boost your LinkedIn engagement analysis with this powerful tool that scrapes likers and commenters from public LinkedIn posts without using cookies. Perfect for marketers, recruiters, analysts.

Pricing

from $1.10 / 1,000 results

Rating

5.0

(2)

Developer

Scraping Solutions

Scraping Solutions

Maintained by Community

Actor stats

39

Bookmarked

1K

Total users

129

Monthly active users

18 hours

Issues response

4 days ago

Last modified

Share

LinkedIn Post Engagers Scraper: Likers, Commenters & Reshares

Extract the public professionals who engage with LinkedIn posts. Collect likers, commenters, or people who reshared one or multiple posts and export structured profiles for lead generation, audience research, recruiting, campaign analysis, and CRM workflows.

No LinkedIn login or cookies required.

Turn visible LinkedIn engagement into a prospecting dataset. Paste public post URLs, choose likers, commenters, or reshares, and receive export-ready public profiles connected to the exact post where each person engaged.

Why choose this Actor?

CapabilityWhat you get
No login or cookiesRun without sharing a LinkedIn account, password, or session cookie.
Three engagement audiencesCollect likers, commenters, or resharers according to your campaign goal.
Multiple posts per runAnalyze several public LinkedIn posts from one input.
Source attributionEvery profile remains connected to the post where the engagement occurred.
Professional contextReceive the public name, profile URL, and professional headline when available.
Automation-readyExport to Excel, CSV, or JSON, or connect the dataset to an API workflow.
Pay per delivered resultPublic pricing starts from $1.10 per 1,000 results, with applicable Store discounts.

Start in less than a minute

  1. Copy one or more public LinkedIn post URLs.
  2. Paste them into LinkedIn post URLs.
  3. Choose commenters, likers, or reshares.
  4. Set the maximum number of profiles.
  5. Click Start and export the resulting dataset.

What this Actor does

Provide one or more public LinkedIn post URLs and choose the engagement audience you want to collect:

  • Likers: people who reacted to the post.
  • Commenters: people who participated in the discussion.
  • Reshares: people who amplified the post by sharing it.

Each result can include the source post, engagement type, person's name, professional headline, and public LinkedIn profile URL.

Why use LinkedIn engagement data?

A directory tells you who exists. Engagement data helps show who is paying attention right now.

Use this Actor to:

  • discover prospects interested in a competitor, event, product, or industry topic;
  • identify decision-makers engaging with relevant thought leadership;
  • build audiences for account-based marketing and personalized outreach;
  • analyze who responds to company and executive posts;
  • compare the audiences of several LinkedIn posts;
  • find candidates participating in professional conversations;
  • send structured engagement data to a CRM, spreadsheet, database, or AI workflow.

Quick start

Extract up to 500 commenters from selected LinkedIn posts:

{
"urls": [
"https://www.linkedin.com/posts/nvidia_our-ceo-jensen-huang-on-the-opportunity-ahead-activity-7470878303642607616-N8fO",
"https://www.linkedin.com/posts/microsoft_march-2026-activity-7444745624991944704-b2uN"
],
"resultsLimit": 500,
"type": "commenters"
}

To collect reactions instead, change type to likers:

{
"urls": [
"https://www.linkedin.com/posts/nvidia_ai-activity-7352008871848128512-TAoD"
],
"resultsLimit": 1000,
"type": "likers"
}

Input

FieldTypeRequiredDescription
urlsarrayYesPublic LinkedIn post URLs to analyze. Add one URL per line in the input form.
resultsLimitintegerYesMaximum number of results requested. Accepted range: 1–3,000.
typestringYesEngagement audience: likers, commenters, or reshares.

Supported LinkedIn post URLs

Use a public LinkedIn post URL, for example:

https://www.linkedin.com/posts/company_topic-activity-1234567890123456789-abcd

The post must be publicly accessible. Private, deleted, restricted, or unavailable posts may return fewer results or no data.

Output

Results are stored in the default Apify dataset and can be exported as JSON, CSV, Excel, XML, or accessed through the Apify API.

Example result:

{
"post_Link": "https://www.linkedin.com/posts/nvidia_ai-activity-7352008871848128512-TAoD",
"type": "likers",
"url_profile": "https://www.linkedin.com/in/example-profile",
"name": "Alex Morgan",
"subtitle": "VP of Data & AI | Enterprise Technology"
}

Output fields

FieldDescription
post_LinkLinkedIn post where the engagement was found.
typeEngagement type requested for the run.
url_profilePublic LinkedIn profile URL of the engager.
namePublic name displayed by LinkedIn.
subtitleProfessional headline or subtitle displayed by LinkedIn.

Field availability depends on what LinkedIn publicly exposes for each person.

Practical workflows

Which engagement type should you choose?

GoalRecommended typeWhy
Find people actively discussing a problemcommentersComments usually represent the strongest visible engagement signal.
Build a broader topic-aware audiencelikersReactions normally provide greater audience coverage.
Identify advocates and content amplifiersresharesResharers took an additional action to distribute the post.
Compare audiences across campaignsRun each type separatelySeparate datasets make each signal easier to segment and score.

Build an intent-based prospect list

  1. Select posts discussing a problem your product solves.
  2. Extract commenters for higher-intent conversations or likers for broader reach.
  3. Export names, headlines, profile URLs, and source posts.
  4. Segment the results by role, company, seniority, or topic in your preferred tool.
  5. Research each prospect before conducting responsible, personalized outreach.

Analyze competitor audiences

Add posts from competing companies and preserve post_Link in your export. This lets you compare which professionals engage with each brand or topic.

Monitor campaigns

Save the input as an Apify Task and schedule recurring runs. Send the dataset to Google Sheets, Make, Zapier, a webhook, or a database for reporting.

Pricing

This Actor uses pay-per-result pricing. Public pricing starts from $1.10 per 1,000 delivered results, depending on the customer's Apify plan and applicable Store discounts.

You pay for results written to the dataset. The requested limit is a maximum, not a guaranteed number: a post may expose fewer public engagers than requested.

Use through the Apify API

Python

from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor(
"scraping_solutions/linkedin-posts-engagers-likers-and-commenters-no-cookies"
).call(run_input={
"urls": [
"https://www.linkedin.com/posts/nvidia_ai-activity-7352008871848128512-TAoD"
],
"resultsLimit": 500,
"type": "commenters",
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item)

JavaScript

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_APIFY_TOKEN' });
const run = await client
.actor('scraping_solutions/linkedin-posts-engagers-likers-and-commenters-no-cookies')
.call({
urls: [
'https://www.linkedin.com/posts/nvidia_ai-activity-7352008871848128512-TAoD',
],
resultsLimit: 500,
type: 'commenters',
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

HTTP

curl -X POST \
"https://api.apify.com/v2/acts/scraping_solutions~linkedin-posts-engagers-likers-and-commenters-no-cookies/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"urls": [
"https://www.linkedin.com/posts/nvidia_ai-activity-7352008871848128512-TAoD"
],
"resultsLimit": 500,
"type": "commenters"
}'

Tips for better results

  • Use the full public LinkedIn post URL.
  • Start with one post to validate availability before processing a larger list.
  • Use commenters when you want stronger visible intent.
  • Use likers when you want broader audience coverage.
  • Use reshares to identify people who actively amplified the content.
  • Keep post_Link in your export so every profile remains connected to its engagement source.

Limitations

  • Only publicly available LinkedIn data can be returned.
  • LinkedIn may limit, reorder, or temporarily omit engagement records.
  • Counts visible on a post can differ from the number of profiles LinkedIn makes publicly accessible.
  • Deleted, private, restricted, or malformed URLs may return no results.
  • Names and professional headlines reflect the values available at extraction time.
  • The Actor does not provide private contact details or access private LinkedIn accounts.

FAQ

Does this Actor require LinkedIn cookies?

No. It does not require your LinkedIn session cookies or account credentials.

Can I process multiple LinkedIn posts?

Yes. Add multiple public post URLs to urls.

Can I extract likers and commenters in the same run?

Each run uses one type. Run or schedule separate tasks when you need multiple engagement audiences.

Why did I receive fewer results than requested?

resultsLimit is a maximum. LinkedIn may expose fewer public profiles, and some engagement records may be unavailable, restricted, or duplicated.

Can I export the data to Excel?

Yes. Open the run dataset and choose Excel, CSV, JSON, XML, or another supported format.

Can I automate it?

Yes. Use Apify Tasks, schedules, API calls, webhooks, Make, Zapier, or another Apify integration.

Responsible use

Use public data responsibly and comply with applicable laws, privacy requirements, LinkedIn's terms, and your outreach platform's policies. Do not use the output for spam, harassment, unlawful profiling, or discriminatory decisions.

Support

If a public post returns unexpected results, open an issue and include:

  • the post URL;
  • selected type;
  • requested resultsLimit;
  • run ID;
  • expected and actual behavior.

This information helps us reproduce and resolve the issue quickly.