Included as LinkedIn's B2B advertising integration surface: campaign and creative management, professional-demographic reporting, lead retrieval, conversion ingestion, and audience workflows are exposed through separately approved API products and scopes.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Advertising API objects include ad accounts and account users, campaign groups, campaigns, creatives and ad formats, and analytics. Separately approved products expose Lead Sync forms and leads, conversion rules and events, and matched-audience segments; these are not one undifferentiated permission surface.
Read administered ad-account structure, users and roles, campaign groups, campaigns, creatives, and analytics; retrieve clicks, impressions, spend, and professional-demographic metrics at account, campaign, or creative level. Lead, conversion, audience, and company-intelligence reads require their own approved product and permission set.
With Advertising API approval and rw_ads, create or update supported ad accounts, campaign groups, campaigns, creatives, and ad formats within the app tier and member's ad-account roles. Lead retrieval is read-only under its scope; conversion uploads and matched-audience management use separately approved rw_conversions and rw_dmp_segments products.
LinkedIn Marketing permissions are member permissions using three-legged OAuth consent. Advertising commonly uses r_ads, r_ads_reporting, and rw_ads; rw_ads is restricted to ad accounts where the authenticated member is an ACCOUNT_BILLING_ADMIN, ACCOUNT_MANAGER, CAMPAIGN_MANAGER, or CREATIVE_MANAGER. Lead Sync, Conversions, and Matched Audiences use separate scopes and product approval.
Record the developer app, approved API product, access tier, version header, consenting member, and effective role for each ad account. Keep lead, conversion, organization, and matched-audience data in their own permission and retention workflows rather than treating Advertising approval as universal access.
Advertising Development tier reads administered accounts without an account-count cap but edits at most five ad accounts and can create only one test ad account; Standard removes those account-count limits, and all tier calls operate on production data. An ad account supports up to 5,000 campaigns and 15,000 creatives. Marketing API versions ship monthly and are supported for at least one year. Daily application and member quotas vary by endpoint and are visible in the Developer Portal, with 429 responses on throttling.
First-party access
Agent access
Support: No official MCP server located
Read scope: No first-party MCP read surface verified.
Write scope: No first-party MCP write surface verified.
Authentication: LinkedIn documents member-consented API products, not a Marketing provider MCP authentication flow. A customer-built adapter would use three-legged OAuth and request only the scopes provisioned to its approved products.
Approval boundary: Preview and confirm campaign status, budget, creative, audience, lead-routing, and conversion changes against the specific ad account and member role. Do not let approval for the Advertising API stand in for Lead Sync, Conversions, Matched Audiences, or other separately approved products.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that LinkedIn ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
First-party API reference or API overview recorded for this platform.
Targeted first-party core-access review
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party webhook, event, SDK, embedded-app, or extension documentation.
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
