# Changelog of LinkedIn Profile Engagement Scraper (Company and Profile) (`ahmed-khaled/linkedin-engagement-scraper`) Actor

- **URL**: https://apify.com/ahmed-khaled/linkedin-engagement-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/ahmed-khaled/linkedin-engagement-scraper.md

## Changelog

### 1.1 (October 2026)

#### Session safety

- The Actor now works with its own LinkedIn session (created in an Incognito window), so your everyday LinkedIn tab no longer shares a session with a run.
- Detects immediately when LinkedIn ends the session (deleted cookie, login redirect, rejected API calls), stops and keeps the posts already scraped; every run reports whether the session is still active.
- Uses the full LinkedIn cookie export and refuses to run with `li_at` alone.
- New **Your browser's user agent** input; the browser's platform, screen size and client hints match it.
- Residential proxy by default, with the same IP kept for the whole run and a browser time zone matching the proxy country.
- Full (non-headless) Chrome on the platform, human-like scrolling and pauses.

#### New

- Scrape several profiles and company pages in one run (`urls`).
- `maxPosts` per URL replaces the scroll-based `limit`.
- New fields: `postedAt` (exact publish time), `urn`, `authorName`, `isRepost`, `sourceUrl`, `sourceType`.
- New **Engagement summary** output view.
- Debug screenshot and HTML saved when a URL returns no posts, or on demand with the new `debug` option.

#### Fixed

- You are now charged only for posts actually saved to the dataset. In 1.0, some runs charged for posts that were rejected by the dataset schema.
- Post URLs are read from the post itself instead of the "Copy link" menu, which was slow and could return the previous post's link.
- Posts containing "Sign in" or "Join now" no longer stop the run with a false "cookies expired" error.
- An expired cookie now reports "cookie expired" instead of a navigation error.
- Impressions are read from LinkedIn's current analytics link.
- Counts like "1.2K" and "Jane and 41 others", and Arabic digits, are parsed correctly.

#### Compatibility

- The `url` and `limit` inputs from 1.0 still work for existing API integrations.

### 1.0 (August 2026)

- Moved to pay-per-event pricing (per post scraped).
- Accepts a `li_at` value or `li_at=...` cookie string.

### 0.x (2024–2025)

- Initial release: engagement of profile and company posts, scroll limit, stealth browser.