From 6ed3e2f5a630333b174371caed74f70d8afa6978 Mon Sep 17 00:00:00 2001 From: Kjell Tore Guttormsen Date: Sat, 30 May 2026 00:28:23 +0200 Subject: [PATCH] fix(linkedin-studio): honest saves/dwell wording, no false tracking claim MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Wave 2 / Step 7 of the remediation plan (research/02 D2/D4). The tool parses the LinkedIn analytics CSV export, which has no saves/dwell — and there is no self-serve API to pull them. Stop implying it tracks them: - report.md: replace "Saves (10x weight) and expert comments (7-9x) are the highest-impact signals" with honest wording — saves rank highest in the engagement ORDER (cite references/algorithm-signals-reference.md, not a restated coefficient), but are visible only in native LinkedIn post analytics (count-only, ~Sept 2025+) with no self-serve API, so this tool does not auto-track them; dwell is internal to LinkedIn for organic posts. - types.ts: document why PostMetrics intentionally omits saves/dwell (no ingest source) so a future contributor does not "add the missing fields". - strategy.md: reconcile two saves references (signature-content criterion + authority scorecard) to say the count is read from native LinkedIn analytics, not captured by this tool. No new metric field, no manual-entry feature (operator Q3). Verify: report.md has no "Saves (10x"/"highest-impact signals" and does say "no self-serve API"; tsc --noEmit clean; analytics suite 106/106; structural lint 0 failed (report.md cites the reference, so stat-consistency stays green). Co-Authored-By: Claude Opus 4.8 --- plugins/linkedin-studio/commands/report.md | 2 +- plugins/linkedin-studio/commands/strategy.md | 4 ++-- .../linkedin-studio/scripts/analytics/src/models/types.ts | 5 +++++ 3 files changed, 8 insertions(+), 3 deletions(-) diff --git a/plugins/linkedin-studio/commands/report.md b/plugins/linkedin-studio/commands/report.md index af144ac..bba28d7 100644 --- a/plugins/linkedin-studio/commands/report.md +++ b/plugins/linkedin-studio/commands/report.md @@ -236,7 +236,7 @@ Compare current week's `aggregateMetrics` against baseline means and standard de 🔴 **Critical: Engagement rate declining** Your engagement rate has dropped from 4.2% to 2.8% over the last 3 weeks. → **Action:** Review recent post hooks. Consider more provocative angles or questions. -→ **Reference:** Hook length should be <140 chars. Saves (10x weight) and expert comments (7-9x) are the highest-impact signals. +→ **Reference:** Hook length should be <140 chars. In the engagement order (see `references/algorithm-signals-reference.md`), saves rank above shares, then quality comments, then reactions. Saves are visible in your native LinkedIn post analytics (count-only, ~Sept 2025 onward) but there is no self-serve API to pull them — so this tool does not auto-track saves; read them in LinkedIn directly. Dwell time is internal to LinkedIn for organic posts (not exposed anywhere this tool can read). 🟢 **Positive: New impression record** Your post on [topic] achieved 12,500 impressions — a personal best! diff --git a/plugins/linkedin-studio/commands/strategy.md b/plugins/linkedin-studio/commands/strategy.md index 2b85eaa..860eab3 100644 --- a/plugins/linkedin-studio/commands/strategy.md +++ b/plugins/linkedin-studio/commands/strategy.md @@ -296,7 +296,7 @@ For the canonical profile-alignment audit (headline/About/Experience/Featured/Sk Ask the user to identify their top-performing posts (or read analytics from `${CLAUDE_PLUGIN_ROOT}/assets/analytics/`). **Signature content criteria:** -- High saves (people bookmarking = authority signal) +- High saves — bookmarking is a strong authority signal; read the count from your native LinkedIn post analytics (this tool does not capture saves) - Quality comments from target audience - Profile visits generated - Shares/reposts by others @@ -404,7 +404,7 @@ Suggest tracking these monthly: Authority Scorecard: [Month] Content Impact: -- Posts with 100+ saves: [count] +- Posts with 100+ saves: [count] _(read from native LinkedIn analytics — not auto-tracked by this tool)_ - Expert comments received: [count] - Profile visits from content: [count] diff --git a/plugins/linkedin-studio/scripts/analytics/src/models/types.ts b/plugins/linkedin-studio/scripts/analytics/src/models/types.ts index 77b323f..d85ba5c 100644 --- a/plugins/linkedin-studio/scripts/analytics/src/models/types.ts +++ b/plugins/linkedin-studio/scripts/analytics/src/models/types.ts @@ -14,6 +14,11 @@ export interface PostMetrics { shares: number; clicks: number; engagementRate: number; // (reactions+comments+shares+clicks)/impressions * 100 + // NOTE: `saves` and `dwell` are intentionally absent. They are NOT in the + // LinkedIn analytics CSV export this tool parses, and there is no self-serve API + // to pull them. Saves are visible (count-only) in the native post analytics UI + // (~Sept 2025 onward) — read them there; dwell is internal to LinkedIn for + // organic posts. Do not add these fields without a real ingest source. } export interface AnalyticsBatch {