Summary
The current linkedin (personal profile) integration in Postiz has no analytics support. LinkedIn launched the Member Post Analytics API (memberCreatorPostAnalytics) in July 2025 that gives per-post engagement data for personal profiles via approved third-party tools. Postiz should implement this to give users analytics parity between linkedin (personal) and linkedin-page (company) integration types.
Current Behaviour
linkedin-page (company/organization) integrations return post analytics via organization statistics endpoints
linkedin (personal profile) integrations return no analytics — the provider has no analytics code path at all
- This creates a broken experience for users who manage personal profiles through Postiz
Requested Change
Implement a dedicated analytics code path for the linkedin personal integration type using the memberCreatorPostAnalytics API.
API Details
Endpoint: GET https://api.linkedin.com/rest/memberCreatorPostAnalytics
Required scope: r_member_postAnalytics (new scope — requires addition to the OAuth flow for personal provider)
Query modes:
q=entity — single post statistics (by post URN)
q=me — aggregated statistics across all member posts
Available metrics (current API version li-lms-2026-06):
| Metric |
Description |
IMPRESSION |
Number of impressions |
MEMBERS_REACHED |
Unique viewers |
REACTION |
Total reactions |
COMMENT |
Total comments |
RESHARE |
Total reshares/reposts |
POST_SAVE |
Times post was saved |
POST_SEND |
Times post was sent via messaging |
LINK_CLICKS |
Link clicks |
FOLLOWER_GAINED_FROM_CONTENT |
Followers gained from this post |
PROFILE_VIEW_FROM_CONTENT |
Profile views driven by this post |
Sample request:
GET https://api.linkedin.com/rest/memberCreatorPostAnalytics?q=entity&entity=(share:urn%3Ali%3Ashare%3A{POST_URN})&queryType=IMPRESSION&aggregation=TOTAL
Authorization: Bearer {token}
X-Restli-Protocol-Version: 2.0.0
Linkedin-Version: 202606
Official docs: https://learn.microsoft.com/en-us/linkedin/marketing/community-management/members/post-statistics
Proposed Implementation
- Add
r_member_postAnalytics to the LinkedIn personal provider OAuth scopes — currently linkedin.provider.ts only requests openid, profile, w_member_social
- Implement
getPostsData() method in linkedin.provider.ts that calls memberCreatorPostAnalytics?q=entity for each post URN and returns impression/reaction/comment counts
- Keep separate code paths — personal profile uses
memberCreatorPostAnalytics, company page uses organization statistics endpoints
Access Requirements
LinkedIn's Member Post Analytics API is part of the Community Management API product. Per LinkedIn's announcement, third-party vendors can apply for access at no cost via a form at developer.linkedin.com. Postiz would need to apply for the r_member_postAnalytics permission to surface this in the managed cloud product; self-hosted users could apply independently.
Impact
- Unblocks analytics for all users with
linkedin (personal profile) integrations
- Provides impression, reaction, comment, reshare, link-click, and follower-gained metrics per post
- Enables A/B test reporting and weekly performance automation for personal LinkedIn accounts
References
Summary
The current
linkedin(personal profile) integration in Postiz has no analytics support. LinkedIn launched the Member Post Analytics API (memberCreatorPostAnalytics) in July 2025 that gives per-post engagement data for personal profiles via approved third-party tools. Postiz should implement this to give users analytics parity betweenlinkedin(personal) andlinkedin-page(company) integration types.Current Behaviour
linkedin-page(company/organization) integrations return post analytics via organization statistics endpointslinkedin(personal profile) integrations return no analytics — the provider has no analytics code path at allRequested Change
Implement a dedicated analytics code path for the
linkedinpersonal integration type using thememberCreatorPostAnalyticsAPI.API Details
Endpoint:
GET https://api.linkedin.com/rest/memberCreatorPostAnalyticsRequired scope:
r_member_postAnalytics(new scope — requires addition to the OAuth flow for personal provider)Query modes:
q=entity— single post statistics (by post URN)q=me— aggregated statistics across all member postsAvailable metrics (current API version li-lms-2026-06):
IMPRESSIONMEMBERS_REACHEDREACTIONCOMMENTRESHAREPOST_SAVEPOST_SENDLINK_CLICKSFOLLOWER_GAINED_FROM_CONTENTPROFILE_VIEW_FROM_CONTENTSample request:
Official docs: https://learn.microsoft.com/en-us/linkedin/marketing/community-management/members/post-statistics
Proposed Implementation
r_member_postAnalyticsto the LinkedIn personal provider OAuth scopes — currentlylinkedin.provider.tsonly requestsopenid,profile,w_member_socialgetPostsData()method inlinkedin.provider.tsthat callsmemberCreatorPostAnalytics?q=entityfor each post URN and returns impression/reaction/comment countsmemberCreatorPostAnalytics, company page uses organization statistics endpointsAccess Requirements
LinkedIn's Member Post Analytics API is part of the Community Management API product. Per LinkedIn's announcement, third-party vendors can apply for access at no cost via a form at
developer.linkedin.com. Postiz would need to apply for ther_member_postAnalyticspermission to surface this in the managed cloud product; self-hosted users could apply independently.Impact
linkedin(personal profile) integrationsReferences