What LinkedIn shipped
LinkedIn Marketing API added predictive audience API ID responses and expanded Conversions API matching with SHA256_IP_ADDRESS in July 2026, tightening B2B advertisers' ability to track conversions and target audiences as browser-based tracking continues to degrade.
Starting with version 202607, fetching a Predictive Audience now returns its read-only ID, enabling partners to obtain the ID for audiences created in Campaign Manager or the API and use it to update them. The 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, available on all active API versions.
The IP matching update sits alongside the existing PLAINTEXT_IP_ADDRESS already available in plain text format, giving advertisers two parallel methods to pass IP data for identity resolution. Currently, only IPv4 addresses are supported.
Why this matters now
The timing reflects a structural shift. B2B marketing teams relying solely on client-side tracking are now losing 20 to 40% of their attribution data to browser restrictions, ad blockers, and consent decline. Browser-based pixels lost 20% to 40% of signal from iOS users, while server-side attribution using conversion APIs, first-party data, and print tracking maintains near-full accuracy because it runs outside the browser, making server-side tracking the 2026 standard.
Identity graph match rates dropping below 70% in Q1 2026 are affecting 60%+ of marketing teams, with third-party cookie blocking and consent rejection now affecting 60%+ of traffic across Safari, Firefox, and Chrome, while server-side tracking captures 25 to 35% more conversions than pixel-only implementations by bypassing ad blockers and browser restrictions.
For B2B advertisers specifically, the gap is wider. The LinkedIn server-side tag sends conversion events to LinkedIn's CAPI endpoint, and B2B advertisers benefit disproportionately because LinkedIn's professional audience has high ad blocker rates.
LinkedIn's SHA256 IP matching expands the identifiers advertisers can send server-side to improve match rates when email or other PII is unavailable or degraded. The hashed format addresses compliance requirements while still enabling the platform to resolve user identity.
The attribution infrastructure LinkedIn is building
The July API updates build on infrastructure LinkedIn has rolled out over the past year to help B2B advertisers measure performance outside the browser.
LinkedIn introduced the Company Intelligence API on September 23, 2025, enabling B2B marketers to track entire organisations through attribution partners, with the API enabling advertisers to track how entire organisations engage with their brand across paid and organic touchpoints through certified attribution partners.
The Company Intelligence API delivers company (target account)-level data for all companies engaged through LinkedIn, providing metrics such as engagement score, paid impressions, paid clicks, leads, paid qualified leads, conversions, paid video views, organic impressions, and organic engagements, designed to support attribution tools with accurate company-level data to gain insights, improve targeting, and measure how companies across ad accounts interact with brands on LinkedIn.
The shift to account-based measurement acknowledges how B2B buying actually works. Modern buying committees average 6 to 10 people with sales cycles often extending beyond 200 days, making lead-level tracking insufficient for accurate measurement.
I can see a 3x increase in companies reached via LinkedIn Ads.
Luke Fielding, Head of DemandGen, EftsurePredictive Audiences, which now return read-only IDs via the API, form another part of the stack. Predictive Audiences allow customers to combine their first-party or third-party data with LinkedIn's predictive AI modelling to build a high-intent audience tailored to their business, with LinkedIn's AI combining millions of engagement signals with customer data to identify members most likely to convert based on business objectives.
Data sources must have 300 or more members to create a predictive audience, with users able to select multiple sources within a data source type to reach 300 members, for example selecting multiple Lead Gen Forms to reach 300 members.
The addition of read-only IDs means developers and marketing platforms can now programmatically retrieve predictive audience identifiers created elsewhere and update them through the API, closing a workflow gap for enterprise teams managing audiences at scale.
What advertisers should do
The SHA256 IP matching update is available now across all active API versions. Advertisers already using LinkedIn's Conversions API should add SHA256_IP_ADDRESS to their event payloads where IP data is available, especially for conversion events where email or other strong identifiers are missing.
Starting with the 202410 version, LinkedIn introduced an optional externalIds field to the user object in the request payload on POST /conversionEvents for Streaming Conversion Events, allowing unique custom identifiers such as external cookie IDs or unique advertiser owned user IDs, improving signal quality, identity resolution, and match rates in cases where other matching parameters are available for some events or channels.
Teams should audit what percentage of their conversion events are currently matched via email versus IP or other identifiers. If match rates are below 70%, implementing SHA256 IP alongside existing identifiers should improve coverage.
For predictive audiences, the ID return is most valuable for teams using attribution platforms or marketing automation tools that need to manage audience membership programmatically. If audiences are being created in Campaign Manager but updated via external systems, retrieving the ID via API now removes a manual step.
This is not optional infrastructure. No single ad attribution tracking model gives the full picture post-iOS 14, with first-party server-side data via Meta CAPI or Google Enhanced Conversions the non-negotiable foundation. LinkedIn's Conversions API now sits in the same tier.
The signal loss isn't getting better. By mid-2026, third-party cookies are gone in Safari and Firefox and effectively unreliable in Chrome under user-choice controls, with mobile identifier deprecation well into its second wave and signal loss a measurable line item in every paid media budget for two years, while teams that adapted their tracking stack early are running roughly the same campaign efficiency they had in 2023.
The compliance layer
Hashed IP matching does not bypass privacy regulation. Consent must still be respected, with server-side tracking not allowing advertisers to ignore users who rejected analytics cookies; if a CMP says no, servers should not forward that event, and treating server-side as a way to bypass consent accumulates regulatory risk rather than solving measurement.
Under specific conditions, analytics cookies can now operate without prior consent if the sole purpose is collecting aggregate statistics, users receive clear information about tracking, and a simple, free opt-out mechanism is available, but this does not apply to advertising cookies or any tracking used for ad platform attribution, with full Consent Mode v2 compliance remaining mandatory in the UK and EEA for Google Ads and Meta conversion tracking.
The privacy framework governing B2B advertising is tightening, not loosening. 88% of advertisers believe privacy regulations significantly impact their ability to deliver personalised advertising, with 61% pointing to audience targeting as the hardest hit, and the challenge even greater for B2B marketers due to smaller audience sizes compared to consumer markets.
Server-side tracking via Conversions API is the compliant path because it captures events without relying on third-party cookies, respects user consent signals, and gives advertisers direct control over what data is sent and when.
Where LinkedIn is heading
The pattern across these updates is clear. LinkedIn is building the server-side measurement stack that lets B2B advertisers track performance when browser-based methods fail, while giving them programmatic control over AI-driven audience tools.
The Predictive Audiences API allows customers to combine first-party or third-party data with LinkedIn's predictive AI modelling to build audience segments tailored to specific business needs, with customers able to use company or contact lists as a seed source to identify prospects likely to engage and have high conversion propensity, improving campaign efficiency and enabling automation of audience expansion for bottom-funnel advertising strategies such as account-based marketing, re-engagement of valuable accounts, and activation of AI-scored segments.
The Company Intelligence API launched last September. Predictive Audiences are now fully accessible programmatically. Conversions API keeps expanding the identifiers it accepts for matching. The throughline is moving measurement and targeting decisively away from browser pixels and toward server-to-server data pipelines controlled by the advertiser.
That infrastructure is now the baseline for B2B ad performance on LinkedIn. Teams still relying on Insight Tag alone are measuring a shrinking fraction of their actual results.