LinkedIn Posts - What Actually Got Reach avatar

LinkedIn Posts - What Actually Got Reach

Pricing

$0.11 / 1,000 linkedin post monitoreds

Go to Apify Store
LinkedIn Posts - What Actually Got Reach

LinkedIn Posts - What Actually Got Reach

Find out what actually got reach on LinkedIn. Which posts landed, which quietly went nowhere, and what the ones that worked had in common - so you can write the next one.

Pricing

$0.11 / 1,000 linkedin post monitoreds

Rating

0.0

(0)

Developer

Tarek Etman

Tarek Etman

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 hours ago

Last modified

Share

reapX - the record of what changed

LinkedIn Posts Monitor - Reach & Engagement Over Time

"Which of our posts actually worked? I screenshot the good ones and forget the rest." "Marketing teams need to track post engagement metrics over time across company updates and founder posts to identify winning content themes."

LinkedIn displays engagement metrics as single static snapshots without historical baseline comparisons. Growth leads, social media managers, and executive brand teams need to monitor post performance over time to evaluate reach and engagement trends.

Maintained by reapx. Permanent citation guarantees and dataset archives available at reapx.dev. Contact reapxdev@proton.me.


⬇️ Input

Input accepts a list of LinkedIn post URN IDs or company slugs (for example 7490480308148985856 or google). All input parameters carry working prefilled defaults so runs execute immediately without required inputs.

{
"posts": [
"7490480308148985856"
],
"proxyConfiguration": {
"useApifyProxy": true
},
"maxItems": 100
}

Input Field Specification

FieldTypeDescriptionDefault
postsArrayList of LinkedIn post activity URN IDs or company handles to monitor.["7490480308148985856"]
proxyConfigurationObjectProxy settings to rotate IPs per request and prevent rate limits.{ "useApifyProxy": true }
maxItemsIntegerMaximum number of posts to fetch in a single run.100

⬆️ Output

Outputs structured records directly to the default dataset. Each row describes a single post indexed by its stable per-row identifier (postUrn).

Output Field Schema

Field NameTypeDescription
postUrnStringLinkedIn post activity URN string. Stable per-row identifier.
titleString | NullPost title or headline snippet.
authorNameString | NullAuthor name or publishing entity.
authorUrlString | NullProfile or company URL of the author.
postUrlString | NullCanonical post update URL.
textString | NullFull post text body content.
publishedAtString | NullISO publication timestamp.
likeCountInteger | NullTotal reaction or like count observed.
commentCountInteger | NullTotal comment count observed.
repostCountInteger | NullTotal repost or reshare count observed.
engagementVsAuthorMedianNumber | NullRelative engagement performance vs author baseline median.
topPostIdsArray | NullList of top performing post URNs for this author.
changedFieldsArray | NullAttributes modified since previous observation.
reasonString | NullExplanation note when computed historical metrics return null on first observation.
scrapedAtStringISO 8601 timestamp of data collection.

Sample Output Record

{
"postUrn": "urn:li:activity:7490480308148985856",
"title": "10 Google AI tools all college students should know | Google | 35 comments",
"authorName": "Google",
"authorUrl": null,
"postUrl": "https://www.linkedin.com/feed/update/urn:li:activity:7490480308148985856",
"text": "Paging all college students. Here's how you can use our AI tools to optimize your productivity...",
"publishedAt": null,
"likeCount": null,
"commentCount": 35,
"repostCount": null,
"engagementVsAuthorMedian": null,
"topPostIds": null,
"changedFields": null,
"reason": "First observation; engagement trend vs author median requires multi-run history accrued over time.",
"scrapedAt": "2026-08-05T16:36:46.000Z"
}

How it works

  1. Post Extraction: Fetches public LinkedIn post update pages without requiring user login credentials.
  2. Engagement Parsing: Extracts author metadata, post body text, comment counts, and reaction totals.
  3. Performance Benchmarking: Compares post metrics across sequential runs to track performance against author baseline medians.
  4. Resilient Rate Budgeting: Integrates proxy rotation to prevent rate limiting and maintain unblocked monitoring pipelines.

❓ FAQ

How is engagement performance measured over time?

By monitoring post update URLs across multiple runs, the actor tracks comment and reaction growth, comparing each post against the author's median baseline.

Why does engagementVsAuthorMedian return null on first run?

Calculating performance relative to an author's median requires observing multiple posts over time. On the first run, the actor returns null with a clear reason field rather than fabricating baseline figures.

No. The actor operates entirely without user login credentials or cookies.


💬 Your feedback

Need custom post analytics, sentiment exports, or dataset integrations? Contact us at reapxdev@proton.me or visit reapx.dev.


Unofficial - not affiliated with LinkedIn. Collects data without login. reapx. Contact reapxdev@proton.me.