A Microsoft API that provides programmatic access to Microsoft Advertising to manage large campaigns or to integrate your marketing with other in-house systems.
Unique reach and Average impression frequency per user are not available as Reporting API v13 columns in either SOAP or REST, so there is currently no supported API request or alternate column name for retrieving them.
1. Reporting API availability
Reporting v13 accepts only the columns defined by the value set for the selected report request. For example:
-
CampaignPerformanceReportRequest.Columnsmust contain values fromCampaignPerformanceReportColumn. ^1^ - The campaign and account column value sets define their supported attributes and statistics; neither contains a unique-reach or frequency metric. ^2^ ^3^
- The cross-report performance-statistics catalog likewise does not define these metrics. ^4^
REST does not expose a broader set of reporting fields than SOAP here: both serialize the same v13 report request model and its column value sets. Consequently, raw JSON/XML values such as UniqueReach, Reach, or AverageImpressionFrequencyPerUser are not hidden alternatives to the SDK enums.
MaxUniqueReach, which appears in recent SDKs, is unrelated to reporting. It is a Campaign Management optimization-goal value added with ReachOptimizationGoalSetting, not a performance-report column. ^5^
Your aggregation test is also conclusive for the proposed workaround: additive Impressions cannot be converted into de-duplicated reach. Frequency requires the distinct-user denominator, which the API does not return.
2. Roadmap and timeline
There is no publicly documented Reporting API delivery date for either metric. The published v13 release notes through September 2026 list recent Reporting API additions but do not announce unique-reach or average-frequency columns. ^5^
For future changes, monitor the API release notes and Microsoft Advertising developer announcements. Microsoft identifies those as the public channels for API changes. ^6^
A roadmap commitment or non-public target date would need to come directly from Microsoft Advertising Support or your account representative; it cannot be inferred from the UI availability.
3. Programmatic export and scheduling
The supported Reporting API export workflow is asynchronous:
- Submit a typed report request with
SubmitGenerateReport. - Poll it with
PollGenerateReport. - After the status becomes
Success, download the ZIP file from the returned URL. ^7^
That workflow can be scheduled externally—for example, with a cron job or cloud scheduler—but it can export only fields present in the API report schema. It therefore cannot export the UI-only reach columns.
The public Reporting v13 documentation does not describe an API for creating or downloading Microsoft Advertising web-UI scheduled reports. There is also no documented supported endpoint for automating the UI export. At present, the practical supported options are:
- Export the reach/frequency report manually from the Microsoft Advertising UI.
- If the UI offers scheduling for that report in your account, use it as a UI delivery mechanism, but do not assume its output can be retrieved through Reporting v13.
- Contact Microsoft Advertising Support and request confirmation of whether scheduled delivery is enabled for these particular columns, plus submit a Reporting API feature request. The API FAQ directs cases not resolved through public documentation or Q&A to Support. ^6^
Microsoft Monetize/Invest has a separate Buyer Reach and Frequency API, but that belongs to the Xandr platform and is not an alternative endpoint for Microsoft Advertising campaign/account Reporting v13 data.
References
- CampaignPerformanceReportRequest Data Object - Reporting - Microsoft ...
- CampaignPerformanceReportColumn Value Set - Reporting
- AccountPerformanceReportColumn Value Set - Reporting
- Report Attributes and Performance Statistics
- Bing Ads API Release Notes
- Frequently asked questions
- SubmitGenerateReport Service Operation - Reporting - Microsoft ...