Paid Media Guide

LinkedIn Ads in 2026: Qualified Leads in the Conversions API, and Every Other Change B2B Teams Need

LinkedIn will now optimise lead generation for the leads your sales team actually wants, if you tell it which ones they were, fast enough. Here is how it works, the rules that decide whether the signal counts, and how to report on it honestly.

Distk Editorial Nov 2026 22 min read

A qualified lead in LinkedIn's Conversions API is a lead your business has judged worth pursuing, reported back as a conversion so LinkedIn optimises for pipeline rather than form fills. Version 202602 added MAX_QUALIFIED_LEAD as an optimisation target for Lead Generation campaigns, and 202608 added MARKETING_QUALIFIED_LEAD and SALES_QUALIFIED_LEAD types. LinkedIn requires qualified-lead data to be shared within 30 days to count for optimisation, recommends five or more qualified leads within a two-week learning phase, rejects events older than 90 days, and advises using either the Conversions API or CRM Sync, not both. In September 2026 a 180-day attribution window joined 365 days for qualifying conversion types, while defaults stay at 30 days post-click and 7 days view-through. LinkedIn itself warns cost per lead may rise as cost per qualified lead falls, so report on CPQL and pipeline. Three other 2026 changes are covered below: Message Ads gained a Not Interested button and optimised rotation by default for lead generation InMail, each ad account is capped at 1,000 DMP segments as legacy geo targeting is retired, and Marketing API versions 202510 and 202511 reach sunset on 15 October and 16 November 2026.

What Is a Qualified Lead in the LinkedIn Conversions API in 2026?

A qualified lead, in LinkedIn's terms, is a lead your own business has judged worth pursuing after it arrived, reported back to LinkedIn as a conversion event. LinkedIn's schema defines QUALIFIED_LEAD as "Identified lead as a qualified lead", and adds two finer types from version 202608: MARKETING_QUALIFIED_LEAD, where "The user filled out a lead generation form, and has been filtered by the advertiser to be a marketing qualified lead", and SALES_QUALIFIED_LEAD, the same at sales stage.

The point of sending that judgement back is optimisation. LinkedIn's help page describes the qualified leads optimisation goal as one that "helps provide you with high-quality leads using qualified lead data from your LinkedIn Conversions API (CAPI) or when you connect your CRM". In plain terms, instead of telling LinkedIn to find people who fill in a form, you tell it to find people who become pipeline.

Explain It Like I Am Five

The simple version

Imagine LinkedIn is a fishing boat that brings you fish. Normally it counts every fish as a success, even the ones you throw back. A qualified lead is you shouting back to the boat, "this one was good, this one was not." After a couple of weeks of that, the boat learns where the good fish swim and goes there more. You may get fewer fish overall, but more of the ones you actually wanted. If you never shout back, the boat keeps chasing whatever bites most.

Why Does Qualified-Lead Optimisation Matter for B2B Teams in 2026?

Because lead form volume is a weak proxy for B2B revenue, and optimising for it rewards the wrong people. LinkedIn's own guidance acknowledges the trade-off directly: with this goal "You might see an increase in qualified leads at a lower cost per qualified lead (CPQL), although the overall cost per lead (CPL) might increase as a result." It recommends "focusing on CPQL and the quality of leads generated rather than CPL and total leads."

That sentence is the commercial heart of the change. A B2B team still reporting LinkedIn performance on cost per lead will see this goal look worse on its dashboard while it performs better on pipeline. Switching the optimisation without switching the reporting is how good campaigns get paused.

CapabilityVersion or dateWhat LinkedIn documents
MAX_QUALIFIED_LEAD optimisation target202602Supported for optimizationTargetType in /adCampaigns and /adBudgetPricing with the LEAD_GENERATION objective
MARKETING_QUALIFIED_LEAD and SALES_QUALIFIED_LEAD types202608Used in the qualified leads optimisation goal, "similar to QUALIFIED_LEAD"
SHA256_IP_ADDRESS identifierJuly 2026, all active versionsHashed IPv4 address for matching
180-day attribution windowSeptember 2026, all active versionsFor qualifying conversion types, alongside 365 days
hashedFirstName and hashedLastName202609Hashed name fields for matching
costInLocalCurrencyPerPaidQualifiedLead202606Cost per paid qualified lead in Company Intelligence

How Does Qualified-Lead Bidding Work on LinkedIn?

You run a Lead Generation campaign, choose the qualified leads goal, and feed LinkedIn the downstream outcome. LinkedIn's changelog for version 202602 says MAX_QUALIFIED_LEAD "optimizes lead generation campaigns to target high-quality leads using qualified lead data sent from Conversions API (where conversion rule type must be QUALIFIED_LEAD) or CRM data shared from Business Manager." Version 202608 extended that to the MQL and SQL types.

LinkedIn's help page lists the setup when creating the ad set: choose the lead generation objective, select the qualified leads optimisation goal, and "Choose qualified lead conversions from one event source." It also notes that "members who click on your ad are sent to a Lead Gen Form pre-filled with their LinkedIn profile data", so this goal runs on LinkedIn's native forms.

The two event sources, and why you should pick one

LinkedIn accepts qualified-lead signals from the Conversions API, through a direct build or partner integration, or from CRM data connected through Business Manager using CRM Sync, where LinkedIn says "we'll auto-create conversions based on that data" and "it can take up to 72 hours to create the conversion." Its strong recommendation is to use one, not both: "We recommend you don't use both Conversions API (CAPI) and CRM data connected through your Business Manager using CRM Sync qualified lead events". If both exist, "the system automatically associates CAPI events for optimization", and selecting events from both "can result in duplication in reporting and double counting of conversions."

What Are the Timing Rules That Make or Break It in 2026?

Speed of qualification decides whether the signal counts. LinkedIn's help page is explicit: "Qualified leads data must be shared with LinkedIn within 30 days to be included in the optimization of the ad set." The Conversions API itself rejects old events, with a validation message that the "Conversion time should be within 90 days." A lead qualified six weeks later may still be reportable, but it no longer teaches the campaign.

RuleLinkedIn's wordingImplication for B2B ops in 2026
Optimisation window"must be shared with LinkedIn within 30 days to be included in the optimization"Sales teams must qualify within weeks, not quarters.
Learning phase"Optimization requires a two-week learning phase for peak performance"Do not judge or change the ad set in its first fortnight.
Volume recommendation"uploading five or more qualified leads within two weeks"Low-volume niches need patience or a looser qualification rule.
Event age limit"Conversion time should be within 90 days"Backfilling old CRM history will be rejected.
Reporting delay"There might be a delay in reported performance metrics for qualified leads"Early dashboards undercount; read them later.

What Changed With Attribution Windows in 2026?

LinkedIn added a 180-day window for long B2B cycles. Its September 2026 note says the postClickAttributionWindowSize and viewThroughAttributionWindowSize fields "now support a 180-day value, in addition to the existing 365-day option" for SUBMIT_APPLICATION, PURCHASE, ADD_TO_CART, QUALIFIED_LEAD, LEAD, MARKETING_QUALIFIED_LEAD and SALES_QUALIFIED_LEAD, and that "This update is available on all active versions."

The defaults have not changed, which matters for anyone who never set them. LinkedIn's schema lists the post-click default as 30 days and the view-through default as 7 days, with allowed values of 1, 7, 30 and 90, plus 180 and 365 for the limited types above. A B2B team with a four-month sales cycle that left the defaults in place is only crediting LinkedIn with a fraction of what it influenced.

Attribution counting is a separate setting. The schema's attributionType defaults to LAST_TOUCH_BY_CAMPAIGN, where conversions "are counted once for each campaign to which they can be attributed", with LAST_TOUCH_BY_CONVERSION as the alternative. Decide deliberately, because the default can count one conversion against several campaigns.

How Do You Set Up the LinkedIn Conversions API for Qualified Leads?

LinkedIn's requirements are three steps: "Create a Conversion Rule", "Associate campaign(s) to the conversion rule", and "Stream conversion events." The rule is created on the /conversions endpoint with conversionMethod set to CONVERSIONS_API, one rule per conversion type, and LinkedIn notes two headers on every request:

X-Restli-Protocol-Version: 2.0.0
Linkedin-Version: {yyyymm}

Each event must identify the person. LinkedIn's validation error lists the accepted options: "SHA256_EMAIL or LINKEDIN_FIRST_PARTY_ADS_TRACKING_UUID or ACXIOM_ID or PLAINTEXT_IP_ADDRESS or GOOGLE_AID or (firstName and lastName) or externalIds or lead". For leads from LinkedIn's own forms, the lead identifier is a Lead Gen form response URN, which ties the qualified outcome back to the exact form submission. From 202609, hashed names also qualify; LinkedIn specifies normalising "to lowercase with no spaces or punctuation" before producing "a SHA-256 HEX-encoded string of exactly 64 characters."

  1. Agree the definitions of MQL and SQL with sales before writing any code.
  2. Move to API version 202608 or later to use the MQL and SQL types; see the version sunset section.
  3. Create one conversion rule per type with CONVERSIONS_API as the method.
  4. Set the attribution window to match your real sales cycle, using 90, 180 or 365 days where allowed.
  5. Send the lead URN for Lead Gen form leads where available, plus hashed email.
  6. Automate the trigger from your CRM stage change, so qualification reaches LinkedIn within the 30-day window.
  7. Choose one event source per ad set, CAPI or CRM Sync, never both.

How Should B2B Teams Report on Qualified-Lead Campaigns in 2026?

Report on cost per qualified lead and pipeline, not cost per lead. LinkedIn has started exposing the metric at account level too: from version 202606 the Company Intelligence API returns costInLocalCurrencyPerPaidQualifiedLead, "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." For ABM teams that means cost per qualified lead can be read per target account, not just per campaign.

Two related 2026 changes affect what these campaigns look like. Inbox lead generation campaigns now default to optimised rotation and carry an automatic Not Interested button, covered in the Message Ads changes section. And every ad account is now capped at 1,000 audience segments, covered in the segment cap and geo section.

What Changed in LinkedIn Message Ads and Conversation Ads?

Two changes in 2026 affect LinkedIn's inbox ad formats, and neither needed advertiser action, which is why many teams have not noticed. In June 2026 LinkedIn began automatically rendering a "Not Interested" call-to-action on Message Ads and Conversation Ads. In July 2026 it changed the default ad rotation for lead generation inbox campaigns from even rotation to optimised rotation. Both alter results without anyone touching a campaign.

Both changes sit inside what LinkedIn's API calls the SPONSORED_INMAILS campaign type, which covers Message Ads and Conversation Ads. They apply to ads created in Campaign Manager as well as through the API, so they matter to every advertiser using these formats, not only to developers.

ChangeWhenWhat LinkedIn saysWho it affects
Not Interested CTAJune 2026 (version 202606 release)"Automatically rendered" on Message Ads and on Conversation Ads' first messageNew and existing ads, at render time
OPTIMIZED rotation defaultJuly 2026OPTIMIZED becomes the default creativeSelection for SPONSORED_INMAILS with LEAD_GENERATIONCampaigns that do not set creativeSelection explicitly, on all versions

What Is the Not Interested CTA on LinkedIn Message Ads?

It is a button LinkedIn adds to your inbox ads automatically. The changelog for Message Ads says: "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." The Conversation Ads note says the same CTA "is automatically rendered on the firstMessageContent for SponsoredConversations."

Three details from that wording matter in practice in 2026:

There is one API-visible trace. For Conversation Ads created in Campaign Manager, LinkedIn states that GET requests to /conversationAds/{sponsoredConversationURN}/sponsoredMessageContents "will now return a new NOT_INTERESTED value in the replyType field." Any integration that reads reply types and expects only the options it created should be checked so the new value does not break parsing.

Why Does a Not Interested Button Change Your Reporting?

Because it gives recipients a third outcome besides engaging and ignoring. LinkedIn's changelog does not describe how the button affects delivery or metrics, and this guide does not speculate about that. What can be said is practical: a visible decline option changes the mix of responses you see, so any comparison of Conversation Ad or Message Ad performance before and after June 2026 is not like for like.

What Changed About Ad Rotation for Lead Generation InMail?

The default switched from even rotation to optimised rotation. LinkedIn's July 2026 note says: "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."

The consequence is spelled out directly: "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."

SettingBefore July 2026From July 2026
creativeSelection not set, LEAD_GENERATION inbox campaignROUND_ROBIN (OPTIMIZED was rejected with a 400 error)OPTIMIZED by default, on all versions
creativeSelection set to ROUND_ROBINEven rotationEven rotation, preserved
creativeSelection set to OPTIMIZED on other objectives in this typeRejectedStill rejected with a 400 error

How Should You Handle the Rotation Change?

Decide which behaviour you want and set it explicitly, rather than inheriting a default that changed underneath you. LinkedIn's guidance for keeping the old behaviour is direct: "To preserve even ad rotation, explicitly set creativeSelection as ROUND_ROBIN." It also notes that "OPTIMIZED is only valid for the SPONSORED_INMAILS type with the LEAD_GENERATION objective", and "all other objectives in this type still reject it with a 400 error."

What Does This Mean for B2B Lead Generation?

It means inbox formats need to be treated as changed channels, not continuing ones. Taken together, the two updates mean a lead generation Message Ad or Conversation Ad campaign running today behaves differently from the same campaign in May 2026, even with identical creative and budget. That matters most to B2B teams whose LinkedIn reporting rolls inbox results into blended cost per lead figures over long periods.

Question for your team in 2026Why it matters
Are we comparing inbox ad results across June 2026?The Not Interested CTA changed the response options mid-period.
Did any creative test start after July 2026 without ROUND_ROBIN?Its result may reflect optimised delivery rather than message strength.
Does our tooling read Conversation Ad reply types?A new NOT_INTERESTED value can appear.
Do we know how leads from these campaigns qualify downstream?Quality, not volume, is the honest measure; see our qualified leads guide.

What Are the Common Mistakes?

What Are LinkedIn's 2026 Audience Segment Cap and Geo Targeting Changes?

Two targeting rules tightened in August 2026. First, every LinkedIn ad account is now capped at 1,000 DMP segments, the audience objects behind Matched Audiences and Predictive Audiences. Second, from 31 August 2026 LinkedIn stopped accepting legacy geo locations for ad targeting entirely, so campaigns must use the Bing geo locations it has been migrating to for years. Both changes reject requests outright rather than degrading quietly.

Neither is a headline feature, which is exactly why they cause trouble. Account-based marketing teams and agencies that have been uploading lists for years can be near the segment ceiling without knowing it, and an old campaign template or tool with hardcoded legacy locations will now fail when it tries to create a campaign.

ChangeEffectiveWhat happensError returned
1,000 DMP segment capAugust 2026, all versionsNew segments blocked once an ad account holds 1,000429 with SEGMENT_LIMIT_EXCEEDED
Legacy geo removed31 August 2026Campaign creation with legacy geo rejected400 with INVALID_VALUE_FOR_FIELD
Profile location field removedSame reminderTop-level location in /v2/me and /v2/people may come back empty or nullNot an error, a missing value

What Exactly Is the 1,000 DMP Segment Limit?

It is a hard per-account ceiling on stored audience segments. LinkedIn's changelog states: "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." It also states that "This update applies to all versions", so upgrading the API version does not change it.

When an account is full, LinkedIn returns a 429 response. Its documentation shows the message text:

"code": "SEGMENT_LIMIT_EXCEEDED",
"message": "Account has reached the maximum limit of 1000 segments. Please delete unused segments before creating new ones.",
"maxValue": 1000
"status": 429

Note the status code. A 429 is usually how APIs signal rate limiting, and many tools respond to a 429 by waiting and retrying. Retrying will not help here. The account is full, and only deleting segments frees space, so tools that treat every 429 as a temporary throttle will loop rather than fail clearly.

Who Is Most Likely to Hit the Segment Cap?

Teams that create a new audience for every campaign, client or upload and never clean up. ABM programmes refreshing target account lists monthly, agencies managing many campaigns in one client account, and CRM integrations that sync a new list on a schedule rather than updating an existing one are the usual sources of segment sprawl.

How Do You Free Up Segment Capacity?

Delete segments you no longer use, carefully, because deletion is broader than it looks. LinkedIn states the delete call returns "204 No Content if the deletion succeeds" and that "Everything related to this DMP segment will be deleted altogether as well, including the DMP segment destinations, the corresponding Ad segment, the DMP segment list (if there's any)." You also need write access to the sponsored account, otherwise LinkedIn returns "403 Forbidden".

  1. Count segments in each ad account before the cap becomes a surprise.
  2. Map segments to live campaigns. Never delete a segment a running campaign targets.
  3. Archive the source list outside LinkedIn before deletion, since the list goes with it.
  4. Delete in batches and record what was removed and why.
  5. Change the upload pattern so integrations update a standing segment rather than creating a new one each run.

What Changed With Legacy Geo Targeting?

Legacy geo is gone for campaign creation. LinkedIn's August reminder says: "Starting Aug 31, 2026, LinkedIn will completely stop supporting Legacy Geo for Ads Targeting. Requests to create campaigns using legacy geo will result in a 400 error with the INVALID_VALUE_FOR_FIELD code. All partners and developers must use Bing-geo as previously published in this migration guide."

The migration itself is old. LinkedIn's guide describes a three-phase move whose final phase says "Only Bing geo locations will be accepted in ad campaigns. Legacy locations can no longer be used for campaign creation, campaigns with legacy locations will be rejected." The guide frames the benefit in scale: roughly "~6k standardized locations, primarily in US" under the old system against "around 2.6 million locations" with Bing geo, including "a large number of international locations". For Indian advertisers targeting specific cities and regions, that broader coverage is the upside.

LinkedIn's guide also notes that use of Bing Maps location data is subject to Microsoft's terms, which "are now incorporated into our LinkedIn Marketing API Program Terms." Agencies building tooling on these locations should read those terms.

How Do You Check Whether Your Tools Still Use Legacy Geo?

Look for campaign templates, saved configurations or code that hardcode old-style location values. LinkedIn's guide gives "urn:li:country:us" as an example of a legacy location returned in the earliest migration phase. Anything still constructing campaigns from stored legacy values will fail at creation time with a 400 error.

What Are the Common Mistakes?

What Is Changing in the LinkedIn Marketing API?

Two LinkedIn Marketing API versions are being switched off. LinkedIn's changelog lists "202510 - Oct 15, 2026" and "202511 - Nov 16, 2026" under Version Sunset, and its developer pages carry a standing banner: "The Marketing Version 202510 (Marketing October 2025) will be sunset on October 15, 2026." That date has now passed. Any tool still sending either version after those dates stops getting normal responses.

This is routine for LinkedIn, which releases a new API version every month, but it lands hard on agencies and B2B teams because almost nobody using LinkedIn ads through software knows which version their tools call. Reporting dashboards, CRM connectors, audience sync tools and in-house scripts all send a version, and the oldest ones in production are usually the ones nobody has touched in a year.

Version headerReleasedSunset date (LinkedIn's wording)Status on 2 October 2026
202509September 2025Sep 15, 2026Already sunset
202510October 2025Oct 15, 2026Sunsets in 13 days
202511November 2025Nov 16, 2026Sunsets in about six weeks
202601January 2026January 15, 2027Active
202609September 2026September 15, 2027Active, latest

One correction worth making explicit. Some automated summaries of LinkedIn's changelog have mislabelled these as 202610 and 202611. Those versions do not exist yet. The page's own sunset lists name 202510 and 202511, the October and November 2025 releases, and the migration status table confirms both dates.

How Does LinkedIn Marketing API Versioning Work?

LinkedIn versions its Marketing API by month and identifies each version with a request header. Its versioning page says: "Include a request header with the key 'Linkedin-Version' and set the value to the version (format: YYYYMM)." It adds that "These API versions are supported and stable for a minimum of one year before sunset." Each version is therefore a dated contract with roughly a twelve month life.

The header in LinkedIn's own example looks like this:

-H 'Linkedin-Version: 202601' \

Two behaviours matter for anyone running production tooling in 2026. LinkedIn states that "An error response is returned when the version header is missing in the request", and that "An error response is returned when the version header is deprecated (e.g., 202401)." There is no silent fallback to a newer version. A tool sending a sunset version gets an error, not slightly different data.

Who Is Affected by the 202510 and 202511 Sunsets?

Anyone whose software calls the LinkedIn Marketing API with either version header, which is a wider group than developers. Agencies and in-house teams are affected even if they never write code, because the tools they rely on make the calls on their behalf. The risk sits with whoever built or maintains the integration, but the consequence shows up in the marketing team's reports and campaigns.

How Do You Check Which Version Your Tools Use?

Look for the header value. For code you own, search the codebase and any configuration for the string Linkedin-Version and read the value next to it. For tools you do not own, ask the vendor which Marketing API version they currently send and when they plan to move. The answer you want is a version from 2026, not 202510 or 202511.

  1. Inventory every LinkedIn integration touching your ad accounts: reporting, CRM, audiences, automation, and any freelancer-built scripts.
  2. Search owned code and config for Linkedin-Version, including environment variables and scheduled jobs.
  3. Email each vendor and ask for the version in use and their migration date, in writing.
  4. Check error logs for version errors after any earlier sunset, such as 202509 on 15 September 2026. An integration that broke then and was patched quietly may be close to the line again.
  5. Note which tools depend on newer features, because some 2026 capabilities only exist on recent versions.

What Should You Do Now?

Move every integration to a current version, ideally the latest. LinkedIn's migration guidance is that "To migrate your app from an older version to a later version, simply update the older version's YYYYMM formatted value in the header to the newer version's value." Changing the header is trivial. Testing what changed between versions is the real work. Version 202510 passed its sunset on 15 October 2026 and 202511 follows on 16 November 2026, so any tool still on either needs that testing now.

StepWhat to do in 2026Why
1Pick a target version, normally 202609The latest buys the longest runway, to 15 September 2027 per LinkedIn's table.
2Read the release notes between your version and the targetFields and behaviours change monthly.
3Change the header in a test environment firstErrors appear before they reach client reports.
4Re-run the key reports and compare totalsConfirms nothing silently changed in the numbers.
5Deploy and diarise the next sunsetEvery version you adopt has a known end date.

If you have questions, LinkedIn routes them through its Developer Support Request Form. The changelog notes that "The Zendesk support path will sunset on June 30th", so older support links in internal runbooks may no longer work.

Why Is Upgrading Worth More Than Avoiding an Outage?

Because several of LinkedIn's most useful 2026 changes only exist on recent versions. Staying on an old header does not just risk a shutdown. It also leaves capabilities unused that matter for B2B performance, particularly around lead quality and measurement.

What Are the Common Mistakes?

What Are the Common Mistakes in 2026?

Key Takeaways for 2026

Distk helps B2B teams across India and internationally wire CRM outcomes back into LinkedIn, agree MQL and SQL definitions with sales, and report campaigns on pipeline rather than form volume. If your LinkedIn optimisation still stops at the form, that is the conversation to have. Related reading: LinkedIn lead generation for B2B SaaS in India and choosing a B2B lead generation partner.

Every version number, date, field name and error code in this guide is quoted from LinkedIn's own developer documentation on Microsoft Learn as read on 2 October 2026. LinkedIn updates these pages monthly, so confirm against the live changelog before acting.

Sources

LinkedIn Qualified Leads and CAPI in 2026: FAQs

What is a qualified lead in the LinkedIn Conversions API?

A lead your business has judged worth pursuing, sent back to LinkedIn as a conversion. LinkedIn defines QUALIFIED_LEAD, and from version 202608 also MARKETING_QUALIFIED_LEAD and SALES_QUALIFIED_LEAD for leads filtered by the advertiser after a lead generation form.

How does MAX_QUALIFIED_LEAD work?

Introduced in version 202602, it is an optimizationTargetType for Lead Generation campaigns that optimises toward high-quality leads using qualified-lead data from the Conversions API or CRM data shared from Business Manager.

How quickly must we send qualified leads to LinkedIn?

LinkedIn says qualified leads data must be shared within 30 days to be included in the ad set's optimisation, and recommends sharing as soon as it is available. Conversion events older than 90 days are rejected.

Should we use the Conversions API and CRM Sync together?

No. LinkedIn recommends not using both, because selecting events from both sources can double count conversions. If both exist, LinkedIn automatically associates Conversions API events for optimisation.

Why did our cost per lead go up after switching to qualified leads?

LinkedIn warns this can happen: qualified leads may rise at a lower cost per qualified lead while overall cost per lead increases. It recommends focusing on CPQL and lead quality rather than CPL.

What attribution windows can LinkedIn conversions use in 2026?

Allowed values are 1, 7, 30 and 90 days, with 180 and 365 days for limited types including QUALIFIED_LEAD, MQL and SQL. The 180-day option was added in September 2026. Defaults are 30 days post-click and 7 days view-through.

What is the Not Interested CTA on LinkedIn Message Ads?

A call-to-action LinkedIn automatically renders on Message Ads and on the first message of Conversation Ads from June 2026. LinkedIn says it is applied to new and existing ads at render time and is not exposed in the API.

What is LinkedIn's DMP segment limit in 2026?

Since August 2026 each sponsored account can hold a maximum of 1,000 DMP segments for Matched Audiences (USER, COMPANY, LIST_UPLOAD) and Predictive Audiences. LinkedIn says this applies to all versions.

When do LinkedIn Marketing API versions 202510 and 202511 sunset?

LinkedIn lists "202510 - Oct 15, 2026" and "202511 - Nov 16, 2026" in its September 2026 changelog. Its developer pages also state the October 2025 version will be sunset on October 15, 2026.

Optimise for pipeline, not form fills

Distk connects your CRM outcomes back to LinkedIn, agrees MQL and SQL definitions with your sales team, and reports LinkedIn campaigns on cost per qualified lead and pipeline instead of raw lead volume.

Start the conversation →