LinkedIn's September API Release Lets You Filter Engaged Accounts by Seniority — and Adds a 180-Day Attribution Window

LinkedIn published version 202609 of its Marketing API this month, and three of the changes matter to anyone measuring B2B pipeline from LinkedIn.

The headline change is in the Company Intelligence API. Starting with 202609, the accountIntelligence finder accepts three new optional filters — campaignGroup, objectiveType and member seniority — alongside the existing campaign filter, according to LinkedIn's developer documentation. Only one can be passed per request. The seniority filter is the notable one: it works only with a LAST_90_DAYS lookback window, and only when none of the campaign, campaign group or objective-type filters are in use. Versions 202608 and below do not support any of them.

Two further changes:

• Conversions API now accepts hashed names. The userInfo object on /conversionEvents supports new optional hashedFirstName and hashedLastName fields next to the existing plaintext ones. Values must be lowercased, stripped of spaces and punctuation, UTF-8 encoded, then SHA-256 hashed to exactly 64 hex characters. A valid userInfo needs either firstName or hashedFirstName, plus either lastName or hashedLastName.

• A 180-day attribution window. postClickAttributionWindowSize and viewThroughAttributionWindowSize on the conversion rule schema now accept 180 in addition to 365, for conversion types including QUALIFIED_LEAD, LEAD, MARKETING_QUALIFIED_LEAD, SALES_QUALIFIED_LEAD, SUBMIT_APPLICATION, PURCHASE and ADD_TO_CART. This one is available on all active versions, not just 202609.

Separately, teams still running old versions have a clock: LinkedIn's versioning page carries a deprecation notice that Marketing Version 202510 sunsets on October 15, 2026.

Why it matters

Company Intelligence exists because LinkedIn's ad reporting is account-shaped, not person-shaped: it returns company-level engagement score, paid impressions, clicks, leads, paid qualified leads, conversions, CPQL and organic engagements for companies that engaged with your brand. The seniority filter changes what you can ask of it. "Which target accounts engaged" is an ABM question. "Which accounts had senior people engaging in the last 90 days" is a prospecting question — it is the difference between a heat map and a call list.

The hashed-name fields are the quieter signal. LinkedIn has spent the last several releases moving conversion matching toward hashed identifiers and tighter consent handling — the same direction every major ad platform has taken. If your CAPI implementation still ships plaintext names, this is a privacy-review item with a deadline attached, not an optional upgrade.

The 180-day window is an admission about B2B reality. Long cycles broke the default attribution math, and 365 days was too blunt an instrument for most teams. Choosing 180 changes reported conversion counts, so pick it deliberately and note the date you switched, or your quarter-over-quarter numbers will move for reasons that have nothing to do with performance.

The limit of account-level data

Even with the new filters, this is still aggregate data about companies, resolved at best to a seniority band, in 90-day buckets, for people who touched your paid media. It tells you an account is warm. It does not tell you which human to write to, what they looked at, or whether they came back.

That last part is where most LinkedIn pipeline actually comes from. Someone who engages with three or more posts in 30 days behaves nothing like a single-touch engager, and no account-level report separates them. LinkedIn intent data is individual-level by nature: a named person, a specific action, a timestamp. The API gives you the company. The engagement gives you the contact.

traxy watches who engages with your LinkedIn content, checks each engager against your ICP, and routes qualified matches to Slack or your CRM — individual-level intent to sit underneath the account-level picture LinkedIn reports. Try it free — 200 credits a month.

Sources: Microsoft Learn, "Recent Marketing API Changes — LinkedIn" (Version 202609); Microsoft Learn, "Company Intelligence API"; Microsoft Learn, "LMS API Documentation Versioning."