Skip to main content
Use the @bijection/connectors/linkedin-ads entrypoint to declare LinkedIn Ads resources.

​
Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

​
Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

​
Ad analytics

​
daily: Daily adAnalytics rows by account, campaign group, campaign or creative

The following example matches configuration campaigns.

​
Configuration: campaigns

Case: linkedin-ads/analytics/daily/campaigns. Connection and resource configuration are declared by this exact case. Credential kind: linkedin-ads. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: analytics
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Configuration: account

Case: linkedin-ads/analytics/daily/account. Connection and resource configuration are declared by this exact case. Credential kind: linkedin-ads. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: analytics
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. Daily ad analytics from the LinkedIn Marketing API’s GET /rest/adAnalytics?q=analytics&timeGranularity=DAILY, one request per UTC day, read as restated report observations. Each row aggregates one pivot (ACCOUNT, CAMPAIGN_GROUP, CAMPAIGN, the default, or CREATIVE) of the bound ad account and is keyed by (pivot value URN, day). LinkedIn states dates in UTC. Every request names LinkedIn-Version: 202610 and X-Restli-Protocol-Version: 2.0.0. dateRange, accounts and campaigns are Rest.li 2.0 values, such as dateRange=(start:(year:2026,month:10,day:1),end:(year:2026,month:10,day:1)) and accounts=List(urn%3Ali%3AsponsoredAccount%3A502840441); the host renders them from JSON and fields as a raw comma list. The accounts facet is always the binding’s own adAccountId; campaignIds narrows it further (LinkedIn is expected to intersect the two facets, which is not confirmed). metrics names at most 18 metrics, since fields also names dateRange and pivotValues and LinkedIn accepts at most 20. Count metrics are exact integers; costInLocalCurrency, costInUsd and conversionValueInLocalCurrency arrive as decimal text ("19.91833") and are kept as that exact text. A value spelled any other way, such as exponent notation, fails the page. adAnalytics does not page and answers at most 15,000 elements. A response of 15,000 elements fails the page rather than publish a day that may be missing rows: list campaignIds to narrow it. A day with many rows can also exceed the host’s page bound (at most 1,024 rows, and rows times declared fields within its claim budget) well before 15,000; that fails the page too. LinkedIn states no per-row finality and documents no restatement bound, so settled is the declared window’s basis. With a conversion metric (externalWebsite*Conversions, oneClickLeads, conversionValueInLocalCurrency), restatementDays defaults to 32: conversion rules attribute for at most 30 days after a click or view. Otherwise it defaults to three days; LinkedIn calls performance metrics near real-time and the three days are not a documented bound. The connection holds a linkedin-ads OAuth 2.0 bearer credential (linkedinAds.credential, three-legged, scopes r_ads_reporting for reporting and r_ads for the identity read); setup names adAccountId, the numeric sponsored account id. Identity reads GET /rest/adAccounts/{adAccountId} and requires its id to be that account. Nothing here has run against LinkedIn or been qualified.

​
Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

​
Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.