policyAug 01, 2026· Impact: medium
Deadline August 31: LinkedIn retires legacy geo targeting for good
LinkedIn ends support for legacy geo targeting in Ads on August 31, 2026. Campaigns still created with legacy geo after that date fail with an HTTP 400 error and the code INVALID_VALUE_FOR_FIELD; all partners must move to Bing-geo. The "location" field is also removed from /v2/me and /v2/people responses — affected integrations need to migrate to the "geoLocation" field with the geo~ projection.
BR
Bluebench editors
Brief
What it means for you
- Check the Safety Score of your current tools in the index.
- Pause aggressive outreach sequences until the situation settles.
- Subscribe to the newsletter for the weekly digest.
Keep reading
Other news
Sep 20, 2026
featureLinkedIn replaces post enhancement with Post Proofreader
LinkedIn has introduced a Post Proofreader for Premium members, replacing the AI post enhancement feature it removed the month before. The tool does not rewrite posts but suggests corrections to an existing draft, with changes marked inline so users can accept or reject them individually. The move follows criticism of AI-generated content, after LinkedIn received more than a million reports through its new AI slop button within three weeks.
medium
Sep 01, 2026
policyDSA report: LinkedIn detects 46% more inauthentic activity
In its EU transparency report under the Digital Services Act, LinkedIn reports a 46% increase in detected instances of inauthentic activity in the first half of 2026 compared with the second half of 2025. Named categories include engagement pods, external apps offering automated posting, and fake profiles. For users of third-party tools this means automation that manufactures engagement is increasingly being detected and acted on.
high
Sep 01, 2026
policyMarketing API 202609: DMA reporting, hashed names and 180-day attribution
Version 202609 of the LinkedIn Marketing API brings four changes: the Ads Reporting API supports a new MEMBER_DESIGNATED_MARKET_AREA pivot for reports grouped by Nielsen DMA regions, the Conversions API accepts the new hashedFirstName and hashedLastName fields (SHA-256) and allows a 180-day attribution window, and the Company Intelligence API gains campaignGroup, objectiveType and seniority filters. Versions 202510 and 202511 sunset on 15 October and 16 November 2026 respectively.
medium
Aug 20, 2026
policyOne million reports: LinkedIn's first numbers on the AI slop button
LinkedIn says more than one million members used the "seems like AI slop" report in its first two weeks. Content flagged as slop now gets around 40% fewer views than before the feature launched. Chief Product Officer Hari Srinivasan stresses that a single report does not automatically cut a post's reach; it primarily affects the feed of the member who reported it. Authors who collect many reports will start receiving a notice.
high