On November 3, 2026, Social Media Today reported that LinkedIn was adding a Post Performance Table to its creator analytics. The reported additions also include follower attribution, saves and sends, and views from connections versus non-connections.
The New View
The report describes a consolidated interface alongside expanded audience and response metrics:
- A post-level listing: The Post Performance Table brings post information and key performance metrics into one listing rather than requiring users to open each post’s analytics separately.
- Viewing metrics together: Impressions, views and watch time appear together in the table to support comparisons across posts.
- Follower attribution: The expanded analytics cover followers gained from a post, including information about which members followed.
- Saves and sends: LinkedIn describes saves as bookmarks and sends as content shared with a friend.
- Network-source views: The reported metrics distinguish views from connections and non-connections.
LinkedIn’s Sam Corrao Clannon said the table is intended to make comparisons easier without opening analytics for each post individually. That is the central interface change: a consolidated place to review performance rather than a sequence of separate post views.
Adjust the Review
For Faryen, the relevant principle is visibility without losing context. Its product direction brings together a clear publishing plan, separate outcomes for each destination and analytics that respect the data each network provides.
This LinkedIn update fits that approach as a change to the review process. Keep the publishing schedule in place while assessing how the native table can improve the way content decisions are made.
Confirm Account Access
The report does not specify a rollout schedule or universal availability. It also does not establish exports, publishing API changes or external analytics integrations. The reported metrics come without validation that they prove business impact or predict future reach.
Confirm that the table appears in the relevant account before making it a required reporting step. For multi-brand teams, make that check at the account level rather than treating access in one account as confirmation for the entire portfolio.
The immediate operational adjustment is modest: establish where the new view is available and use it there. Keep the existing review approach for accounts without access so the reporting routine remains workable across the full schedule.
Review Posts Together
The table’s stated purpose supports reviewing posts in batches. Instead of opening every post’s analytics as the default starting point, begin with the consolidated listing when it is available.
Use that view to identify which posts deserve closer attention. A post may stand out on watch time while another attracts saves or followers. The useful review question is what each signal adds to the content decision, not which post can be declared the overall winner.
Keep the account and post context attached to any review notes. If the team later discusses a finding outside LinkedIn, the note should still make clear which content produced it and which metric prompted the discussion.
For creators, this can remain a compact native review. For multi-brand operators, the same approach should preserve separate account observations before moving into a broader content discussion.
Match Signals to Questions
The expanded metrics support different questions. Treating them as separate inputs makes the review more useful than replacing an impressions-only assessment with another single preferred measure.
A practical discussion can follow the distinctions reported in the update:
- Impressions, views and watch time: What does the viewing information show for the posts under review?
- Followers gained: Which posts were associated with new followers, and what member information does LinkedIn show?
- Saves: Which posts were bookmarked?
- Sends: Which posts were shared with a friend?
- Connection status: How do views from connections compare with views from non-connections?
Choose the question before selecting the metric that answers it. If the discussion concerns follower growth, bring follower attribution into the review rather than letting impressions answer a different question.
Likewise, keep saves and sends distinct in the reporting language. LinkedIn gives them different meanings, so combining them into an undefined measure would remove useful detail.
This is also the basis of comparing performance without flattening important differences. A clearer interface should make distinctions easier to retain, not encourage a single score that hides them.
Keep Scheduling Deliberate
The practical scheduling response is to connect the review to future content choices rather than immediately changing posting frequency. Start with the question the metrics raise and decide which part of the next content plan deserves attention.
For example, a review focused on bookmarks should keep the discussion about saved content. A review focused on follower attribution should examine the posts associated with those follows. These are different planning conversations even when they concern the same account.
Record the interpretation as a hypothesis for future content rather than as a permanent scheduling rule. That keeps a useful observation from becoming a requirement that the evidence has not established.
An adaptable editorial calendar provides room for those decisions without rebuilding the whole publishing plan. The goal is to connect a specific observation with a considered content adjustment while keeping the rest of the schedule understandable.
Preserve Destination Context
Multi-brand teams need to keep the native review attached to its source account. A consolidated LinkedIn view is useful within that context; portfolio reporting still needs to preserve which destination produced each observation.
Faryen’s product direction includes multiple accounts per network and a separate publishing result for each destination. Apply that same clarity to the review: identify the account first and then discuss the performance information available for it.
Keep publication status separate from audience response. A delivery result answers whether a destination needs publishing attention. Performance metrics belong to the later question of how the content was received.
Maintaining that distinction supports a workflow that separates readiness from publishing authority. It also keeps an analytics discussion from obscuring an unresolved operational task on another destination.
The useful outcome is a review in which the team can identify both the content decision and the account it belongs to.
Update Reporting Language
Before adding the new fields to a recurring report, agree on the labels the team will use. Preserve LinkedIn’s distinction between saves and sends and identify connection-based views explicitly.
Keep the metric attached to its provider context when it moves into a cross-network discussion. A LinkedIn field should retain its meaning rather than being placed under a broad label that suggests all networks supply equivalent data.
This matches Faryen’s analytics direction: show provider-specific data honestly and mark unavailable metrics as unavailable. For reporting purposes, an unavailable field should remain visibly different from a reported zero.
The same discipline applies to the written summary. Describe the observation before adding an interpretation so the reader can distinguish the recorded metric from the team’s judgment.
A useful report should support reading social analytics in context rather than simply collecting more fields. Add a metric because it answers a recurring review question, not because another column is available.
Keep Decisions Visible
Close the native review with a clear statement of what the team intends to learn or change. The result might be a content question to revisit or a planned adjustment tied to a particular account.
Keep that decision separate from the metric itself. This preserves a readable chain from the reported observation to the editorial judgment and then to the next planned action.
That is the useful operational shift for creators and multi-brand teams: make the comparison easier to inspect while keeping responsibility for the interpretation clear. More visible data should support a more understandable plan.
Next Technical Signal
The next technical milestone to watch is documentation clarifying whether these native LinkedIn metrics will become available through approved analytics integrations.
