Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Warning
Deprecation Notice: The Marketing Version 202510 (Marketing October 2025) will be sunset on October 15, 2026. We recommend that you migrate to the latest versioned APIs to avoid disruptions. For information on all the supported versions, refer to the migrations documentation. If you haven’t yet migrated and have questions, submit a request on the LinkedIn Developer Support Portal.
Note
To get better understanding on the integration best practices refer here.
Q: Which segment statuses are allowed in campaign targeting?
Segments with BUILDING, UPDATING, READY or ARCHIVED are allowed to be included/excluded in a campaign's targeting. Archived segments with 0 audience count won't become Ready even after being added to an active campaign.
Q: Which segment statuses are not allowed in campaign targeting?
Segments with EXPIRED, FAILED or ERROR status are not allowed to be included/excluded in a campaign's targeting.
Q: How to find expired segments?
From the Finder API, iterate through all the segments status with expired for a given sponsored account.
FINDER Example for dmpSegments
GET https://api.linkedin.com/rest/dmpSegments?q=account&account=urn:li:sponsoredAccount:516848833
From the response, check the status value from destinations object.
GET https://api.linkedin.com/rest/adSegments?q=accounts&accounts=urn:li:sponsoredAccount:511910281&start=0&count=5
From the response, check the status value for adSegments.
Q: What happens if campaign attempts to use an expired segment?
When a campaign attempts to use a segment that's expired, API returns a 400 error response with a detailed validation message.
Q: Can expired segment be updated again?
Yes. But please note that when an segment is expired, the input and resolved data is purged due to our data retention policy and compliance to GDPR. Bring a segment back to BUILDING status by uploading another list, or stream new users or companies to it. The segment will be in BUILDING status, but it's essentially a new segment with the same segment ID.
Q: Why is a segment stuck in BUILDING status and not updated?
A segment is considered unused and set to ARCHIVED after it's not continuously used for 30 days in a draft or active campaign. Because of this, a segment may appear "stuck" in BUILDING when updates are streamed to an ARCHIVED segment, thus pushing it into the BUILDING state, and right before it's archived again, new updates are streamed to the unused segment.
Q: What data can be used to match?
Users can be matched with hashed email addresses and other identifiers.
Companies can be matched on companyname, companydomain, and other identifiers.
Q: What hash methods are acceptable for email addresses?
SHA256 and SHA512 are accepted when using the streaming API. CSV uploads accept SHA256 only.
Before hashing, capital letters and whitespace must be removed.
Q: I sent a request to remove a company from my audience segment but it wasn't removed, why?
Ensure that the same metadata sent to add the company is also sent to remove the company. If there's not a high enough confidence that the company attempting to be removed is a match, it won't be removed.
Q: I sent a batch request to add multiple users to my audience segment but the audience size is still 0, why?
If the segment status is in a READY state and the audience size is 0, there are two potential reasons:
- No matches were found.
- There were multiple matches with low relevance scores between match candidates. In this scenario, it's determined that who the advertiser was trying to target was unclear and thus no matches are returned.
Q: Can users be added or removed in batch?
Yes, the DMP Segments Users endpoint allows both batch creation and removal. See DMP Segment Users for more information.
Q: What match feedback/reach projections are available?
Audience size and matched count are returned as documented under DMP Segment Destinations.
Q: What limits exist on audience size?
The minimum audience size that can be used in a campaign is 300 members matched. The maximum size of a CSV list upload is 300,000 hashed email addresses.
Q: How is the 1,000 limit on DMP segments counted?
The limit counts all DMP segments in the sponsored account regardless of status — including active, expired, and archived segments — not just segments that are actively being used. For more information on segment statuses, see Matched Audiences statuses and definitions.
Q: What happens when I reach the 1,000 limit on DMP segments?
You won't be able to create new DMP segments in that sponsored account until you delete existing ones. Your existing segments remain available and any live campaigns using them keep running — nothing is deleted for you.
Q: How do I stay within the 1,000 limit on DMP segments?
Review your segments and delete the ones you no longer use. Start with expired segments — they're no longer collecting members and are usually the safest to remove. See Delete DMP Segment for details.
Q: Will my existing audiences or campaigns be affected if I reach 1,000 DMP segments?
No. Only the creation of new DMP segments is blocked when your sponsored account reaches 1,000 DMP segments. Existing segments keep working and active campaigns are unaffected.
Q: How many users can be passed in a single API call?
Up to 5,000 hashed emails can be sent in a single call to DMP Segment Users.
Q: Are DMP Segments viewable in the LinkedIn UI?
Yes, the Matched Audiences page within Campaign Manager has this information.
Q: Is it possible to create multiple DMP Segments with the same name?
Yes, segment names are not required to be unique.
Q: Can DMP Segments be deleted or made inactive?
Delete DMP Segments and the users, companies, and list uploads added to a DMP Segment. Matches are also automatically removed after 90 days. For details on deleting a DMP segment, see Deleting DMP Segments
Q: Can multiple CSV list uploads be associated with a single DMP Segment?
No, a DMP Segment can only have one list upload.
Q: Can list upload DMP Segments (sourcePlatform of LIST_UPLOAD) receive streamed users or companies?
No, a list upload segment can only receive list uploads.
Q: Are there rate limits on DMP API usage?
Since October 31, 2022, we have introduced 1-minute rate limit per user (member) for our DMP streaming APIs Users and Companies to prevent abuse, ensure service stability, and consistent API availability. These limits will be enforced in addition to your current daily limits, which can be found through Developer Portal > My Apps > App > Analytics > Quotas and usage.
For the /users endpoint, an application will have a 1 minute limit of 600 requests per user. This means, that at any given minute, an application can make up to 600 requests on behalf of a single user.
For the /companies endpoint, an application will have a 1 minute limit of 300 requests per user.
If your application calls /dmpSegments/users or /dmpSegments/companies, you may get an HTTP 429 response while calling the endpoints too frequently, indicating that you're exceeding the rate limits.
If your application makes a large amount of automated, bulk data pushes that exceed tens of millions of calls, you can expect to see frequent throttling. While this might affect the throughput of your API calls, you won't see any differences in the matched audience processing SLA.
Q: How do I handle API calls that are rate limited?
Your application should be catching errors when making calls to /dmpSegments/users and /dmpSegments/companies.
Example response for 1 minute per user level throttling.
How to handle? Retry in 1 minute.
{
"serviceErrorCode": 101,
"message": "Too Many Requests",
"status": 429
}
Example response for 24 hour per user level throttling and application level throttling (what's experienced today for daily limits).
How to handle? Slow down the frequency of requests. A common practice is exponential backoff, where the time between requests starts off small (a few seconds, for example), then doubles before each retry. This is continued until a request is successful or a reasonable maximum time between requests is reached (5 minutes, for example).
{
"serviceErrorCode": 101,
"message": "Resource level throttle APPLICATION_AND_MEMBER DAY limit for calls to this resource is reached",
"status": 429
}
{
"serviceErrorCode": 101,
"message": "Resource level throttle APPLICATION DAY limit for calls to this resource is reached",
"status": 429
}
Q: Can I get my application's rate limits increased?
No, the limits we intend to enforce won't be customizable at an application level. However, the limits will be enforced such that there's minimal interruption to existing applications and their users.
Q: Why am I seeing "Audience too small" even when the matched count is more than 300?
Upon processing the matched count, there's another filter that runs to finalize the audience count based on their privacy settings. If the member prefers to opt out of third-party data settings, then these members will be filtered out of the total audience count.
Q: Why can’t I delete certain DMP segments?
DMP segments that are being used as the seed of a predictive audience cannot be deleted. Attempting to delete them will result in an error.
Q: Why must desiredAudienceCount be greater than 300 for predictive audiences?
Predictive audiences require a minimum population size to ensure member privacy. If desiredAudienceCount is set to 300 or below, the system will reject the request.
Q: What targeting facets are supported for predictive audiences?
A geo filter is mandatory for predictive audiences to build correctly. Currently, the predictive audience targeting criteria only support geo-based filtering, meaning no other filter types are accepted.