Beyond the News
Sign in
Web DevelopmentMarketing & DistributionDeveloper ToolsPaid Acquisition Active dossier

LinkedIn Ads API adds a 1,000-segment audience cap as Legacy Geo shuts down August 31

LinkedIn’s 202608 Marketing API release makes two operational constraints explicit: ad accounts are capped at 1,000 DMP/Matched Audience segments across all API versions, and campaigns using Legacy Geo targeting stop being creatable after August 31.

Reviewed and published by Lars Jansen Updated 4 min read
Comment
First published

Key details

  1. LinkedIn Marketing API version 202608 is the latest August 2026 release.
  2. Each sponsored account is capped at 1,000 DMP segments for Matched and Predictive Audiences.
  3. The cap applies to all API versions.
  4. Attempts above the limit return HTTP 429 with `SEGMENT_LIMIT_EXCEEDED`.
  5. Legacy Geo targeting stops being supported on August 31, 2026.
  6. Campaign writes using Legacy Geo can return HTTP 400 with `INVALID_VALUE_FOR_FIELD`; developers must migrate to Bing-geo.
  7. The Matched Audiences API is now generally available for application by qualified developers.
  8. Version 202608 adds sponsored-account-level Dynamic UTM tracking parameters.

What builders should take away

  1. Count existing audience segments per ad account before deploying new automation, and add cleanup/retention rules so transient campaigns do not consume the 1,000-segment budget indefinitely.
  2. Replace Legacy Geo IDs before August 31 and run campaign-creation tests against production-like payloads rather than waiting for the cutoff error.
  3. Do not rely on API-version pinning to avoid the segment cap; LinkedIn says the limit applies across versions.
  4. Handle 429 segment-limit errors as a resource-governance condition rather than retrying blindly.
  5. If you adopt account-level Dynamic UTMs, document precedence and compare generated landing-page parameters before migrating attribution templates.

What changed

LinkedIn's August 2026 Marketing API release introduces a hard account-level limit of 1,000 DMP segments used for Matched Audiences and Predictive Audiences. The limit applies across API versions; accounts above it receive HTTP 429 with `SEGMENT_LIMIT_EXCEEDED` when trying to create more segments and must delete unused segments first. The same release reiterates a separate August 31 cutoff: LinkedIn will completely stop supporting Legacy Geo for Ads Targeting, and campaign creation using old geography identifiers will return a 400 `INVALID_VALUE_FOR_FIELD`. LinkedIn also says the Matched Audiences API is now generally available for application by qualified developers.

Why it matters

Ad-tech integrations often treat audience segments and geography dictionaries as durable resources. LinkedIn is making both assumptions unsafe at once: segment stores now need lifecycle management to stay below a fixed ceiling, and old geography IDs become invalid for campaign writes after August 31. Agencies, CDPs and SaaS tools that provision campaigns programmatically can therefore fail even when their authentication and API version remain valid. The new GA application path for Matched Audiences also means more developers can build against the audience API, but they inherit these operational constraints immediately.

The 1,000-segment cap applies across API versions

LinkedIn says each sponsored ad account can have at most 1,000 DMP segments across USER, COMPANY and LIST_UPLOAD Matched Audiences plus Predictive Audiences. Creating another segment above the threshold returns HTTP 429 and `SEGMENT_LIMIT_EXCEEDED`. This is not avoided by pinning an older Marketing API version.

Legacy Geo stops working for new campaign targeting on August 31

LinkedIn says it will completely stop supporting Legacy Geo for Ads Targeting from August 31. Campaign-creation requests using the old geography values return `400 INVALID_VALUE_FOR_FIELD`, and developers must use the newer Bing-geo identifiers.

Audience APIs are opening to more developers

The Matched Audiences API is now generally available for application to qualified developers through LinkedIn’s Developer Portal. That expands access beyond previously approved partner paths but does not relax consent, data-use or audience-resource limits.

The release also adds account-level Dynamic UTM configuration

Marketing API version 202608 adds support for dynamic UTM tracking parameters at the sponsored-account level, extending the existing campaign-level surface. That can simplify consistent attribution templates across campaigns, but integrations should migrate deliberately rather than coupling the tracking change to the mandatory geo/audience fixes.

What to watch next

  • Whether LinkedIn adds segment-usage reporting or bulk cleanup tools for accounts near the 1,000 limit.
  • Post-August-31 edge cases in the Legacy Geo to Bing-geo migration.
  • Approval criteria and rollout friction for developers applying to the now-open Matched Audiences API.
  • Further account-level tracking or audience-governance controls in subsequent Marketing API versions.

Still unclear

  • The effective impact of the 1,000-segment cap varies widely with how aggressively an advertiser creates temporary or highly granular audiences.
  • LinkedIn's documentation establishes the API behavior but does not provide broad independent evidence on how many existing accounts are already above or near the limit.
  • Access to Matched Audiences remains subject to LinkedIn qualification even though applications are now generally open.

Sources

Direct reading behind this dossier.

1 sources
Recent Marketing API Changes
LinkedIn / Microsoft Learn primary documentation

Primary source for Marketing API 202608, Matched Audiences GA application, 1,000 DMP-segment cap, Dynamic UTM support and August 31 Legacy Geo cutoff.

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment
Continue reading
Web Development

Reddit is moving third-party apps off its Public Data API and onto Developer Platform

Reddit has made the direction of its API platform explicit: existing API apps should register now, with an August 30 cutoff for possible $1,000 porting-bounty eligibility and a broader September 30 registration request. The actual migration is later, but builders need to inventory dependencies and missing Devvit capabilities now.