App Logo
linkedin.com

Get LinkedIn post analytics

Read a LinkedIn post's own analytics from the post-summary page: impressions, members reached, profile viewers, followers gained, the engagement breakdown (reactions, comments, reposts, saves, sends, and link visits), and the default top-demographics bucket per category. Analytics exist only for posts the signed-in member authored, so the post must be your own — it throws otherwise. Pairs with get_profile_posts: pass the urn it returns. Older or low-reach posts legitimately lack some metrics (membersReached null) and demographics (topDemographics []). Use get_post for public counts on any post.

Input

postUrl required

The post identity: a urn (urn:li:activity:<id>, e.g. from get_profile_posts), a /feed/update/urn:li:activity:<id>/ URL, a /posts/<slug>-<id>-<code>/ permalink, a lnkd.in shortened share link, or a bare numeric activity id. Must be a post authored by the logged-in account.

Output

urn required

The activity/ugcPost urn the analytics were read for (join key with get_profile_posts).

analyticsUrl required
topDemographics required

Default 'All' view: the top bucket per available category (Location, Seniority, Company size, Industry, Job title, Company). [] when demographics are unavailable for the post.

saves optional
sends optional

Sends on LinkedIn (DM shares).

reposts optional
comments optional
reactions optional
linkVisits optional

Visits to links from this post.

impressions optional
membersReached optional

Unique members reached; read deterministically off the page's own membersReachedFeature container, not the LLM. null on older posts that predate this metric.

profileViewers optional

Profile viewers attributed to this post.

followersGained optional
linkEngagements optional

Total link engagements; null when the post has no link.

socialEngagements optional

Total social engagements = reactions + comments + reposts + saves + sends.

FAQ

Read a LinkedIn post's own analytics from the post-summary page: impressions, members reached, profile viewers, followers gained, the engagement breakdown (reactions, comments, reposts, saves, sends, and link visits), and the default top-demographics bucket per category. Analytics exist only for posts the signed-in member authored, so the post must be your own — it throws otherwise. Pairs with get_profile_posts: pass the urn it returns. Older or low-reach posts legitimately lack some metrics (membersReached null) and demographics (topDemographics []). Use get_post for public counts on any post.
Required: postUrl.
It returns urn, saves, sends, reposts, comments, reactions, linkVisits, impressions, analyticsUrl, membersReached, profileViewers, followersGained, linkEngagements, topDemographics, socialEngagements.
Yes. It acts as you on linkedin.com: on your own Chrome it reuses your session, and on a Reduck-hosted browser it loads the linkedin.com cookies saved by the Reduck extension.
It only reads. It looks things up on linkedin.com and changes nothing there.
Ask an AI agent connected to Reduck to run reduck/linkedin.com/get_post_analytics, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/linkedin.com/get_post_analytics
It is part of Reduck's official curated catalogue.

Start building not clicking