3de9143e469b5a9cb2d4b91c37d2d698281386e9
Turns out every individual post's own analytics page has an "Export" button (SinglePostAnalytics_<Name>_<id>.xlsx) giving exactly the detail that was being hand-logged: Profile Viewers/Followers Gained from the post, and the Reactions/ Comments/Reposts/Saves/Sends/Link/Premium-button breakdown behind the Aggregate Analytics file's single blended "Engagements" number. Matches each file to a post by its own "Post URL" field, not the numeric id in the filename - confirmed those two ids are actually different LinkedIn schemes, so filename-based matching would have been wrong. Loaded once per render (load_post_details) rather than re-parsed per table row. All 4 of Mckinley's real posts are now auto-covered (55/80/17/365 impressions), replacing the 1-of-4 hand-logged coverage from before. Kept showing both engagement numbers side by side in the table/report - the per-post export's own breakdown sum has been observed to disagree with the aggregate export's Engagements figure for the same post more than once now. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Languages
Python
50.8%
HTML
48.9%
CSS
0.3%