Linkedin Release Notes

Product & Platform Announcements

• Predictive Audiences API: id field available in the response:

Starting version 202607, fetching a Predictive Audience (single or list) now returns its read-only id. Partners can now obtain the id for audiences created in Campaign Manager or the API, and use it to update them.

• Conversions API: New user identifier available for matching:

A new optional user identifier SHA256_IP_ADDRESS is available in the userIds object in the Conversion Event User Schema for /rest/conversionEvents to match with the hashed IP address of the user using SHA256. This update is available on all active versions. This is in addition to the existing PLAINTEXT_IP_ADDRESS already available in plain text format. Currently, only IPv4 addresses are supported.

• Create and Manage Campaigns: creativeSelection in SPONSORED_INMAILS type campaigns with LEAD_GENERATION objective for Message & Conversation Ads:

Starting July 2026, the adCampaigns API will support, as the default, OPTIMIZED for creativeSelection in SPONSORED_INMAILS type campaigns (Message Ads and Conversation Ads) with the LEAD_GENERATION objective. Previously, this combination was rejected with a 400 validation error and forced to ROUND_ROBIN. If your integration creates or updates SPONSORED_INMAILS campaigns with the LEAD_GENERATION objective without explicitly setting creativeSelection, the behavior will default to OPTIMIZED starting with the July 2026 release and will apply to all versions. To preserve even ad rotation, explicitly set creativeSelection as ROUND_ROBIN. Note: OPTIMIZED is only valid for the SPONSORED_INMAILS type with the LEAD_GENERATION objective — all other objectives in this type still reject it with a 400 error.

Product & Platform Announcements

• Company Intelligence API: 365-Day Lookback and Company Attribute Decoration:

Starting with the version 202606, the /accountIntelligence endpoint adopts the following changes:

• filterCriteria.lookbackWindow: A new value LAST_365_DAYS is now supported alongside the existing LAST_7_DAYS, LAST_30_DAYS, LAST_60_DAYS, LAST_90_DAYS, and LAST_180_DAYS. When supplied, engagement and conversion metrics are aggregated over the trailing 365 days from the data calculation date, giving partners a full year of engagement history per target company. Versions 202605 and earlier continue to cap the window at 180 days.

• companySize: A StaffCountRange enum field representing the range of the number of staff employed by the target company. Possible values are: SIZE_1, SIZE_2_TO_10, SIZE_11_TO_50, SIZE_51_TO_200, SIZE_201_TO_500, SIZE_501_TO_1000, SIZE_1001_TO_5000, SIZE_5001_TO_10000, and SIZE_10001_OR_MORE. The field is response-only, included in the default projection, and defaults to $UNKNOWN when the target company has not declared a staff size.

• industry: An IndustryUrn field identifying the industry the target company is associated with based on its primary business activities and products (e.g., urn:li:industry:1). The field is response-only, included in the default projection, and defaults to urn:li:industry:0 when no industry has been assigned.

• countryCode: A string field representing the ISO country code of the target company's headquarters (e.g., "US", "GB"). The field is response-only, included in the default projection, and defaults to an empty string when the headquarters country is not available.

• costInLocalCurrencyPerPaidQualifiedLead: A double type field representing the cost per paid qualified lead (CPQL) attributed to the target company, in the advertiser's local currency. Derived as the ratio of total ad spend over the number of paid qualified leads collected from members of the target company within the lookback window. The field is response-only, included in the default projection, and defaults to 0.0 when no paid qualified leads have been attributed to the target company within the lookback window.

• Dynamic UTM API: Added dynamic tracking parameter support for CREATIVE_NAME:

Starting with the version 202606, the /adTrackingParameters endpoint now supports CREATIVE_NAME in addition to existing parameter values in dynamicTrackingParameters field. This will allow advertisers to track creative names along with their creative ID using Dynamic UTM that uses placeholder parameters which are automatically replaced with relevant values when an ad is served. Within Campaign Manager, this is already available within the URL tracking parameters under the Placement tab as {{CREATIVE_NAME}}.

• Conversation Ads API: Not Interested Call-to-Action (CTA):

A Not Interested CTA is automatically rendered on the firstMessageContent for SponsoredConversations. The CTA is applied to new and existing ads at render time and is not exposed in the API. Use test sends to preview the behavior. For ads created from Campaign Manager, GET requests to /conversationAds/{sponsoredConversationURN}/sponsoredMessageContents will now return a new NOT_INTERESTED value in the replyType field.

• Message Ads API: Not Interested Call-to-Action (CTA):

A Not Interested CTA is automatically rendered on Message Ads. The CTA is applied to new and existing ads at render time and is not exposed in the API. Use test sends to preview the behavior.

This release notes article lists the feature and content updates for Sales Navigator users and admins from April to June 2026.

Sales Navigator user and admin updates

Salesforce updates to external client app authentication

Effective May 2026, Salesforce is introducing new security requirements for external client apps used by partner integrations. As part of these updates, partners are required to implement:

• Proof Key for Code Exchange (PKCE)
• Refresh Token Rotation (RTR)

These controls improve the security of OAuth authentication flows and help protect against token misuse.

What’s changing for Sales Navigator admins?

Sales Navigator admins must enable new OAuth security controls:

• PKCE must be enabled and can’t be turned off once activated.
• RTR must be enabled, which changes how refresh tokens are issued and used.

These updates are required for continued compliance. Sales Navigator admins are advised to review the Salesforce communications and complete the recommended next steps.

Salesforce CRM user seat connections and inactivity limits

To improve security and reliability, Salesforce enforces a 30‑day inactivity limit on refresh tokens for user seat connections. If a user doesn’t have Salesforce CRM activity for 30 consecutive days, their connection expires. The data is not lost; the connection is just paused. When the user returns and attempts a CRM action, they’ll be prompted to reconnect, after which time, they can sync and access their CRM data.

Get Started guide to help prospect by finding and saving leads

Saving a lead in Sales Navigator lets you track a prospect and receive updates that can help you plan outreach. The Get Started guide can help you start finding leads in Sales Navigator and save leads from your search results to monitor and reach out to leads at the right time.

Sales Navigator user and admin updates

Salesforce updates to external client app authentication

Effective May 2026, Salesforce is introducing new security requirements for external client apps used by partner integrations. As part of these updates, partners are required to implement:

• Proof Key for Code Exchange (PKCE)
• Refresh Token Rotation (RTR)

These controls improve the security of OAuth authentication flows and help protect against token misuse.

What’s changing for Sales Navigator admins?

Sales Navigator admins must enable new OAuth security controls:

• PKCE must be enabled and can’t be turned off once activated.
• RTR must be enabled, which changes how refresh tokens are issued and used.

These updates are required for continued compliance. Sales Navigator admins are advised to review the Salesforce communications and complete the recommended next steps.

Salesforce CRM user seat connections and inactivity limits

To improve security and reliability, Salesforce enforces a 30-day inactivity limit on refresh tokens for user seat connections. If a user doesn’t have Salesforce CRM activity for 30 consecutive days, their connection expires. The data is not lost; the connection is just paused. When the user returns and attempts a CRM action, they’ll be prompted to reconnect, after which time, they can sync and access their CRM data.

Get Started guide to help prospect by finding and saving leads

Saving a lead in Sales Navigator lets you track a prospect and receive updates that can help you plan outreach. The Get Started guide can help you start finding leads in Sales Navigator and save leads from your search results to monitor and reach out to leads at the right time.

Learn more

• Sales Navigator release notes

Product & Platform Announcements

• Events Management API: Off-Platform Event Support and Required End Dates

Starting with the 202605 version, the /rest/events endpoint adopts the new Event schema with the following changes:

• hasDarkUgc: A boolean field indicating whether the event is backed only by a dark UGC post created through sponsored ad workflows. When true, the event has no LinkedIn Events Detail Page and is suppressed from all organic surfaces regardless of discoveryMode. The field is CREATE ONLY and defaults to false for regular page-backed events.

• endsAt: Now a required field on all event types. Create requests that omit endsAt will be rejected with a validation error. This is a breaking change introduced from 202605; versions 202604 and below continue to treat endsAt as optional.

• Event Ads API: Off-Platform Event Ads and Lead Generation Campaign Objective

Starting with the 202605 version, the Event Ads API (/rest/adAccounts/{adAccountId}/adCampaigns with format: SPONSORED_UPDATE_EVENT) adds the following capabilities:

• objectiveType: LEAD_GENERATION is now a supported objective for Event Ad campaigns, alongside the existing BRAND_AWARENESS, WEBSITE_VISITS, and ENGAGEMENT objectives. The referenced event must have a lead gen form attached (event.leadGenForm) and be published (event.ugcPost populated).

• Off-platform Event Ads: A new end-to-end flow is available for advertisers who want to run Event Ads without a LinkedIn Events Detail Page. Create the backing event with hasDarkUgc: true, then proceed with the standard campaign, dark post, and Event Ad creative steps. The ad redirects to the external URL regardless of event lifecycle stage.

• Conversions API: New user identifiers available for matching, updated required field validation for lead, and a new request parameter to fetch cross-account shared conversion rules

New optional user identifiers in the userIds object in the Conversion Event User Schema for /rest/conversionEvents to improve match rates and attribution performance. This update is available on all active versions.

• PLAINTEXT_IP_ADDRESS: IP address of the user in plain text format. Currently, only IPv4 addresses are supported.
• GOOGLE_AID: The Google Advertising ID (GAID), a unique, user-resettable, and anonymous identifier for Android devices.

Updated the required field validation in the Conversion Event User Schema for /rest/conversionEvents to allow sending conversion events with only lead as the user identifier. Previously, this returned a 400 validation error. This update is available on all active versions.

The Find Conversion Rules by Ad Account API on /rest/conversions finder by account now supports an optional array parameter conversionOwnershipTypes accepting two possible values: OWNED and SHARED. The response body includes a new field ownershipType with one of those values in the conversion object. This allows fetching both owned conversions for the ad account and shared conversions across ad accounts within the same Business Manager. If this query parameter is not passed, only OWNED conversions are returned by default, preserving existing behavior for version 202604 and earlier.

• Predictive Audiences API: New method to Get all predictive audiences in the account

Starting with the 202605 version, the Predictive Audiences API supports the GET_ALL method on /rest/dmpSegments/{dmpSegmentId}/businessObjectiveBasedAudiences, which retrieves all predictive audiences under a given parent DMP segment as a paginated collection.

• Ad Analytics API: New metric available for Appointments Scheduled from Lead Gen Forms

Starting with the 202605 version, the AdAnalytics API supports a new metric appointmentsScheduled in the response for /rest/adAnalytics. This metric measures the number of appointments booked through Lead Gen campaigns.

• Company Intelligence API: Paid Video Views Metric

Starting with the 202605 version, the /accountIntelligence endpoint now includes the following new field for campaign insights at the company level:

• paidVideoViews: A long type field representing the total count of paid video ad views from members of the target company. Counts are aggregated over the window specified in filterCriteria.lookbackWindow. The field is response-only, included in the default projection alongside the existing engagement metrics, and defaults to 0 when no paid video views have been attributed to the target company within the lookback window.

• Change to Developer Support path

Starting May 15, 2026, contact Developer Support via the Developer Support Request Form. This will be the primary way to reach Developer Support going forward. The Zendesk support path will sunset soon. Use the form for all new requests as we transition.

• Reapply to API Products from your Developer Portal

Developers can now resubmit expired API access requests (that expire after 21 days) or those declined for insufficient details directly in the Developer Portal. A Reapply CTA replaces "Access denied", reloads the original form for edits, and creates a new case—no need to recreate the app or contact support.

• Member Post Statistics API and Member Video Statistics API: Starting with the 202605 version, the /memberCreatorPostsAnalytics and /memberCreatorVideoAnalytics endpoints change the format of metricType in the response body from object to string to simplify parsing.

Product & Platform Announcements

• Member Post Statistics: New Creator Analytics Metrics

The /memberCreatorPostAnalytics endpoint now supports new metrics:

• POST_SEND: Number of times post entities were sent via LinkedIn messaging.

• POST_SAVE: Number of times post entities were saved.

• LINK_CLICKS: Number of clicks on links within post entities.

• PREMIUM_CTA_CLICKS: Number of clicks on premium call-to-action buttons.

• FOLLOWER_GAINED_FROM_CONTENT: Number of new followers gained from post entities.

• PROFILE_VIEW_FROM_CONTENT: Number of profile views generated from post entities.

• Company Intelligence API: New 180-Day Lookback Window

Starting with the 202604 version, the /accountIntelligence endpoint now supports a LAST_180_DAYS lookback window, extending the maximum range for filtering impression and engagement data from 90 to 180 days.

• New Integration Requirements Pages

New requirement pages are now available to guide developers on the technical criteria for integrating with LinkedIn Marketing Solutions APIs. These requirements must be met as part of an organization pursuing partner certification.

• Breaking Changes

The monthly API versions below will be sunset and removed from the platform on the dates listed. For information on all the supported versions, refer to the migrations documentation. To avoid disruptions to your platform, please migrate to the latest API version launched today.

• Version Sunset

The monthly API versions below will be sunset and removed from the platform on the dates listed. For information on all the supported versions, refer to the migrations documentation. To avoid disruptions to your platform, please migrate to the latest API version launched today.

Product & Platform Announcements

• Member Post Statistics: New Creator Analytics Metrics

The /memberCreatorPostAnalytics endpoint now supports new metrics:

• POST_SEND: Number of times post entities were sent via LinkedIn messaging.

• POST_SAVE: Number of times post entities were saved.

• LINK_CLICKS: Number of clicks on links within post entities.

• PREMIUM_CTA_CLICKS: Number of clicks on premium call-to-action buttons.

• FOLLOWER_GAINED_FROM_CONTENT: Number of new followers gained from post entities.

• PROFILE_VIEW_FROM_CONTENT: Number of profile views generated from post entities.

• Company Intelligence API: New 180-Day Lookback Window

Starting with the 202604 version, the /accountIntelligence endpoint now supports a LAST_180_DAYS lookback window, extending the maximum range for filtering impression and engagement data from 90 to 180 days.

• New Integration Requirements Pages

New requirement pages are now available to guide developers on the technical criteria for integrating with LinkedIn Marketing Solutions APIs. These requirements must be met as part of an organization pursuing partner certification.

• Breaking Changes

Starting with the 202605 version, the /memberCreatorPostsAnalytics and /memberCreatorVideoAnalytics endpoints change the format of metricType in the response body from object to string to simplify parsing.