Linkedin Release Notes

Product & Platform Announcements

• Creatives API: New metadata field:

  Starting with the 202610 version, the /creatives endpoint supports a new read-only metadata field that returns descriptive information about a creative: adFormat, adHeadline, adIntroductionText, adLine, landingPage, and assetURL. Previously, retrieving this information required calling a different API depending on the creative's content type. The field is derived on read from the creative's underlying content and isn't stored, and fields that don't apply to the creative's ad format are omitted. metadata isn't returned by default; request it explicitly using the fields query parameter when retrieving a single creative, as described in Retrieve Creative Metadata. It isn't returned by the creatives finders. This is an additive, backward-compatible change; versions 202609 and below don't return this field.

• Company Intelligence API: New jobFunction filter:

  Starting with the 202610 version, the accountIntelligence endpoint finder now supports filtering results by the optional jobFunction field under filterCriteria. Supported job-function buckets are INFORMATION_TECHNOLOGY, PRODUCT, SALES, MARKETING, OPERATIONS, FINANCE, HUMAN_RESOURCES, and OTHER. The field accepts these bucket values directly, rather than a standardized job-function URN or numeric ID. Only one of campaign, campaignGroup, objectiveType, seniority, or jobFunction can be passed in filterCriteria. The jobFunction filter is supported only with the LAST_90_DAYS lookback window. It applies to member-attributable paid and organic engagement metrics; paidQualifiedLeads, conversions, and costInLocalCurrencyPerPaidQualifiedLead aren't broken down by job function. This field is request-only and doesn't change the response schema. Versions 202609 and below don't support this filter.

• Creatives API: New enriched content fields:

  Starting with the 202610 version, /creatives responses can return new read-only standardUpdateAd and videoAd members within content. standardUpdateAd includes reference and an optional contentAuthor field; videoAd includes reference, an optional contentAuthor, and an optional preRollMetadata field. Earlier API versions continue returning content.reference. Clients using 202610 should continue supporting content.reference, because it may still be returned when enriched content is unavailable. These fields are read-only and don't change Creative create requests.

• Ads Reporting API: New memberFollows and memberProfileClicks metrics:

  Starting with the 202610 version, the /adAnalytics endpoint's metrics schema supports two new optional metrics: memberFollows, which returns the count of sponsored member profile follows, and memberProfileClicks, which returns the count of clicks on the profile of the member who owns the sponsored post. Both metrics exist only for Sponsored Updates and member follower display ads, such as Thought Leader Ads.

• Boost API: New Member and Company Page post boost endpoints:

  Starting with the 202610 version, four new Boost API endpoints are available for both Member and Company Page (organization) posts: Boost Init, Boost Hydrate, Boost Post, and Boost Status. These APIs enable partners to embed LinkedIn Boosting directly into their content and publishing workflows, connecting organic content to paid amplification within their platform. The endpoints are available under the existing Advertising API product.

Breaking Changes

• Campaign Management API: New required surface field for publisher lists (action required):

  Starting with version 202611 (November 2026 release), publisher lists (/adPublisherRestrictions) require a surface field that sets the list's placement type: LAN (LinkedIn Audience Network) or CTV (Connected TV). Requests on version 202611 or later that create a publisher list without a valid surface will fail with a 400 error. Existing partner API accounts have a migration window that ends on December 15, 2026. After that date, campaigns (/adAccounts/{id}/adCampaigns) and account trust preferences (/adAccountTrustPreferences) can only use publisher lists whose placement type matches the campaign. Requests that don't meet this rule will fail with a 400 error on every API version. Lists already attached to campaigns will keep working. Please update your integration before December 15, 2026.

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.

• 202510 - Oct 15, 2026
• 202511 - Nov 16, 2026

Original source

Sales Navigator user updates

Act on intelligence without leaving your workflow

Sales Navigator for Microsoft Teams

Sales Navigator for Microsoft Teams delivers high-priority buying signals directly in the flow of work to help sellers act on key decision-maker changes. With this integration, Sales Navigator alerts will appear in Microsoft Teams with one-click deep links back to Sales Navigator, helping revenue teams increase pipeline, protect deals, and drive faster follow-up on the moments that matter most. Setting up Sales Navigator for Microsoft Teams requires steps at both the IT admin and end user seller levels.

Who can use this feature?

Sales Navigator for Microsoft Teams is only available with a Sales Navigator Advanced Plus subscription, and only available in English. No alerts about people located in the European Economic Area (EEA), Switzerland, and the UK are currently provided.

CRM Embedded Experiences: Lead IQ

Tap into the full power of Sales Navigator’s AI-driven Lead IQ directly into your system of record. Get the insights you need to personalize outreach and show up prepared without ever leaving your CRM.

Key signals, now on LinkedIn.com

Key signals now come through LinkedIn notifications. Sales Navigator alerts sent to your LinkedIn notifications include a saved lead being promoted or moving companies, a senior hire at a saved or CRM account, and new saved search results.

Act on these alerts without leaving LinkedIn.com, catching decision-maker moves as they happen.

Sharper signals that move deals forward

Personalized onboarding

New Sales Navigator users answer four questions about their goals, what they sell, their ideal buyers, and their target accounts. Seller responses are used to tailor onboarding guidance, lead recommendations, recommendation rankings, alerts, and content to how each seller works. Early personalization helps sellers reach relevant workflows faster, without creating meaningful onboarding friction. These preferences can help power increasingly tailored recommendations, search, alerts, AI-powered experiences, and workflows across Sales Navigator over time.

Personalized onboarding is only available to Advanced and Advanced Plus users who purchased their subscription through an account representative.

Improved alerts and notifications

• The weekly catch-up email has been rebuilt to round up alerts you didn't see and draws from 22 types of alerts. Clicking the card takes you straight to the alert.
• Alerts span more of your book of business. Update alerts from a single lead are now consolidated.

Reach the right buyers more easily

Better performing search

• Find leads even when your searches return no results - If a lead search returns no results, Sales Navigator might adjust a filter to show the closest matching leads while preserving your search intent. Rather than displaying an empty results page, Sales Navigator identifies which filter was adjusted and shows the closest matching leads.
• Search understands intent - Describe the buyer you're looking for and Sales Navigator finds people who match, rather than only profiles carrying your exact words.

More paths to warm introductions

• Easier discovery of warm introductions - New badges displayed on leads in search to make it easier to see potential warm paths in.
• Prioritized list of warm introductions, with rationale on the recommendation - List of potential warm paths in to the lead prioritized directly in search, rather than on the Lead page. Sorted by strength of relationship, and rationale for why they're a good path in.
• Account level warm introductions - New badge when searching for leads on a single account that allows you to see all your potential warm paths into leadership at that company.
• Prioritized list of leaders at the account with potential intro path - List of leaders at the account with potential warm paths in, sorted by strength of relationship.

Who viewed my Company Page filter

In the Lead search pane, use the Viewed your Company Page recently filter to search for leads that have viewed your Company Page within the past 90 days, enabling warmer, better-timed outreach to buyers who are showing interest.

Additional enhancements

More flexibility with cross-company Relationship Maps

Cross-Company Relationship Maps allow you to map the whole corporate family, not just one company.

Find and save leads across a parent and its subsidiaries onto a single relationship map, giving you the complete end-to-end picture of how your buying committee is connected.

Sales Navigator admin updates

Additional enhancements

Admin Center activity logging controls

Admins can turn notes and calls logging on or off for every user from a single settings page.

Feature availability

• Sales Navigator for Microsoft Teams: Advanced Plus only
• CRM Embedded Experiences: Lead IQ: Advanced Plus only
• Key signals, now on LinkedIn.com: Core, Advanced, Advanced Plus
• Personalized onboarding: Core, Advanced, Advanced Plus
• Improved alerts and notifications: Core, Advanced, Advanced Plus
• Better performing search: Core, Advanced, Advanced Plus
• More paths to warm introductions: Core, Advanced, Advanced Plus
• Who viewed my Company Page filter: Core, Advanced, Advanced Plus
• More flexibility with cross-company Relationship Maps: Advanced, Advanced Plus
• Admin Center activity logging controls: Advanced Plus only

Original source

Product & Platform Announcements

• Company Intelligence API: New campaignGroup, objectiveType, and seniority filters:

  Starting with the 202609 version, the accountIntelligence endpoint finder now supports filtering results by the following optional fields under filterCriteria: campaignGroup, objectiveType, or member seniority, in addition to the existing campaign filter. Only one of campaign, campaignGroup, objectiveType, or seniority can be passed in the filterCriteria parameter. Organic metrics are 0 when campaign, campaignGroup or objectiveType filter is used. The seniority filter is supported only with LAST_90_DAYS lookback window and when campaign, campaignGroup, and objectiveType aren't used in the filterCriteria. These fields are request-only and do not change the response schema. Versions 202608 and below do not support these filters.

• Ads Reporting API: New MEMBER_DESIGNATED_MARKET_AREA pivot:

  Starting with the 202609 version, in the adAnalytics endpoint's analytics finder, pivot.value parameter now supports MEMBER_DESIGNATED_MARKET_AREA, letting partners request analytics reports grouped by Nielsen Designated Market Area (DMA), consistent with other member demographic pivots such as MEMBER_REGION_V2. Pivot items are returned as urn:li:geo:{id} URNs. You may use the /adTargetingEntities resource to resolve these geo URNs to DMA region names. When displaying results grouped by this pivot, you must display a "circle R" notice of registration immediately following each display of the DMA marks (that is, DMA®) and the statement "DMA® is a registered service mark of The Nielsen Company."

• Conversions API: New hashedFirstName and hashedLastName fields:

  Starting with the 202609 version, the userInfo object for the /conversionEvents endpoint supports two new optional fields for matching: hashedFirstName and hashedLastName, in addition to the existing plain text firstName and lastName fields. Before hashing, normalize the value to lowercase with no spaces or punctuation, and encode special characters as UTF-8. The result should be a SHA-256 HEX-encoded string of exactly 64 characters. A valid userInfo combination requires either firstName or hashedFirstName, together with either lastName or hashedLastName.

• Conversions API: New 180-day attribution window option:

  The postClickAttributionWindowSize and viewThroughAttributionWindowSize fields on the Conversion Rule schema in /conversions endpoint now support a 180-day value, in addition to the existing 365-day option, for the following conversion types: SUBMIT_APPLICATION, PURCHASE, ADD_TO_CART, QUALIFIED_LEAD, LEAD, MARKETING_QUALIFIED_LEAD, and SALES_QUALIFIED_LEAD. This update is available on all active versions. MARKETING_QUALIFIED_LEAD and SALES_QUALIFIED_LEAD conversion types are available starting with the 202608 version onwards.

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.

• 202510 - Oct 15, 2026
• 202511 - Nov 16, 2026

Original source

Product & Platform Announcements

• Matched Audiences API: Generally available to all qualified developers:

  Starting August 2026, the Matched Audiences API is now generally available for application to all qualified developers. You can apply for access directly from the Developer Portal.

• DMP Segments API: Cap on number of DMP Segments in ad account:

  Starting August 2026, each sponsored account is restricted to a maximum of 1,000 DMP segments for Matched Audiences (USER, COMPANY, LIST_UPLOAD) and Predictive Audiences. Requests to the /dmpSegments endpoint from ad accounts that exceed this threshold return a 429 error with the code SEGMENT_LIMIT_EXCEEDED. This update applies to all versions. To allocate space for additional segments, delete unused segments before creating new ones. See Delete DMP Segment for details.

• Dynamic UTM API: Ad account-level tracking parameter support:

  Starting with the 202608 version, the /adTrackingParameters endpoint now supports setting dynamic UTM tracking parameters at the ad account level using the sponsoredAccount member of the adEntity key, in addition to the existing sponsoredCampaign. Account-level parameters apply to creatives across all campaigns in the account. This is an additive, backward-compatible change.

• Conversions API: New conversion types for Marketing & Sales Qualified Leads:

  Starting with the 202608 version, the /conversions endpoint now supports MARKETING_QUALIFIED_LEAD and SALES_QUALIFIED_LEAD as granular conversion types in addition to the existing QUALIFIED_LEAD. Conversion events streamed on conversion rules with these new types are used in the qualified leads optimization goal for deeper funnel campaign optimization, similar to QUALIFIED_LEAD. See Qualified leads optimization goal for details.

• Conversions API: Additional use cases:

  Additional use cases published for the Conversions API, including qualified leads optimization, retargeting audiences, source data for predictive audiences, and conversion lift testing.

• Ad Accounts API: New productType and originatingCustomer fields:

  Starting with the 202608 version, the /adAccounts endpoint returns productType (MARKETING_SOLUTIONS, TALENT_SOLUTIONS, LINKEDIN_ON_LINKEDIN) and originatingCustomer (a urn:li:customer:{id} URN). Both fields apply to ENTERPRISE accounts only and are immutable once set at account creation. This is an additive, backward-compatible change.

• Campaign Groups API: New billing, beneficiary, and buying type fields:

  Starting with the 202608 version, the /adCampaignGroups endpoint supports billingReference, billingParentReference, beneficiaryReference (a union of company or organization), and buyingType (AUCTION or RESERVATION). All four fields are immutable once set at campaign group creation; billingReference and billingParentReference apply to ENTERPRISE accounts only. In earlier versions, these fields are rejected with a 422 error. This is an additive, backward-compatible change.

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.

• 202508 - Aug 17, 2026
• 202509 - Sep 15, 2026
• 202510 - Oct 15, 2026

Reminders

• Change to Developer Support path:

  Please 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 on June 30th. Please use the form for all new requests as we transition.

Original source

Product & Platform Announcements

• Matched Audiences API: Generally available to all qualified developers:
  Starting August 2026, the Matched Audiences API is now generally available for application to all qualified developers. You can apply for access directly from the Developer Portal.

• DMP Segments API: Cap on number of DMP Segments in ad account:
  Starting August 2026, each sponsored account is restricted to a maximum of 1,000 DMP segments for Matched Audiences (USER, COMPANY, LIST_UPLOAD) and Predictive Audiences. Requests to the /dmpSegments endpoint from ad accounts that exceed this threshold return a 429 error with the code SEGMENT_LIMIT_EXCEEDED. This update applies to all versions. To allocate space for additional segments, delete unused segments before creating new ones. See Delete DMP Segment for details.

• Dynamic UTM API: Ad account-level tracking parameter support:
  Starting with the 202608 version, the /adTrackingParameters endpoint now supports setting dynamic UTM tracking parameters at the ad account level using the sponsoredAccount member of the adEntity key, in addition to the existing sponsoredCampaign. Account-level parameters apply to creatives across all campaigns in the account. This is an additive, backward-compatible change.

• Conversions API: New conversion types for Marketing & Sales Qualified Leads:
  Starting with the 202608 version, the /conversions endpoint now supports MARKETING_QUALIFIED_LEAD and SALES_QUALIFIED_LEAD as granular conversion types in addition to the existing QUALIFIED_LEAD. Conversion events streamed on conversion rules with these new types are used in the qualified leads optimization goal for deeper funnel campaign optimization, similar to QUALIFIED_LEAD. See Qualified leads optimization goal for details.

• Conversions API: Additional use cases:
  Additional use cases published for the Conversions API, including qualified leads optimization, retargeting audiences, source data for predictive audiences, and conversion lift testing.

Original source

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.

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.

• 202507 - Jul 15, 2026
• 202508 - Aug 17, 2026
• 202509 - Sep 15, 2026

Original source

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.

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.

• 202506 - Jun 15, 2026
• 202507 - Jul 15, 2026
• 202508 - Aug 17, 2026

Reminders

• Member Post Statistics API: New creator analytics metrics

  Starting with the 202604 version, 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.

Original source