Skip to main content
Use the @bijection/connectors/microsoft-advertising entrypoint to declare Microsoft Advertising 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.

​
Daily performance reports

​
daily: Daily performance rows from asynchronous report requests, one per pass

The following example matches configuration campaigns.

​
Configuration: campaigns

Case: microsoft-advertising/performance/daily/campaigns. Connection and resource configuration are declared by this exact case. Credential kind: microsoft-advertising. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: performance
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. Read-only daily performance observations from the Reporting API v13, which is asynchronous only. Each pass submits one report request (POST Reporting/v13/GenerateReport/Submit, Aggregation: Daily, a custom date range of windowDays, default 31, scoped to the bound account, CSV with FormatVersion 2.0 and the report header and footer excluded), polls POST GenerateReport/Poll every pollSeconds (default 120; Microsoft suggests two to fifteen minutes) until Status is Success, and reads the one CSV file of the ZIP archive at ReportDownloadUrl. Error ends the pass with a typed gap; a successful report with no rows names no URL and ends the pass. The download URL is short-lived storage on a domain Microsoft says not to depend on, so it is read as a prepared result: no credential or declared header travels to it. level selects the report type (account, campaign, adGroup, ad, keyword); rows are keyed by (AccountId, TimePeriod, the level’s identifiers, breakdowns among DeviceType and Network). Metrics (Impressions, Clicks, Spend, Conversions, Revenue, AllConversions, AllRevenue) are published as exact decimal text; a value in another spelling fails the page. A row naming another account fails the page. Report windows: a pass reads one window from where the last one left off. While history is being caught up the next pass begins after the window; once a window reaches today, the next pass begins restatementDays back, so those days are read again. Microsoft states data is generally complete three hours after a click, that invalid-traffic adjustments can take a week or more, and credits conversions to the click’s day within the conversion window. It states no per-row finality, so settled is true only for a day at least restatementDays old when read: 30 days with a conversion metric, else 14, both recipe choices. A row missing from a later read is not withdrawn. Limits: a report file is read whole and published 128 rows per read, so a file of more rows is downloaded once per 128 rows, and every download must happen within the five minutes Microsoft keeps the URL valid after the poll; a file beyond 1,024 rows or the host’s response bound fails the pass. Narrow the level, the breakdowns or windowDays for large accounts. Connection microsoft-advertising (microsoftAdvertising.credential): an OAuth 2.0 bearer whose envelope also writes the application’s DeveloperToken header; setup customerId (the manager account, sent as CustomerId) and accountId (sent as CustomerAccountId and as the report scope). Identity reads POST CustomerManagement/v13/Account/Query under the connection’s customerManagement role, bound to https://clientcenter.api.bingads.microsoft.com/CustomerManagement/v13 with the same credential, and requires its Account.Id to be the bound account. Nothing here has run against Microsoft Advertising 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.