Google has made the Campaign Manager 360 API less cumbersome for teams that pull campaign data into dashboards, internal tools and reporting workflows. The new reportData.query method returns structured JSON directly from a synchronous request, instead of pushing developers through a saved report, a run, a polling loop and a file download. Google positions it for interactive analysis while keeping the existing Reports service for larger or scheduled jobs.
This reads like a developer update. For marketers, the practical story is reporting speed: when the technical work between “something changed” and “show me the data” gets shorter, teams investigate campaign performance sooner. The catch is that faster retrieval does not fix weak measurement.
What Google announced
On 12 August 2026, the Google Ads Developers Blog highlighted the new reporting route in the Campaign Manager 360 API. Google’s own API changelog dates reportData.query to 14 July, so the method appears to have been available before the wider August announcement. Search Engine Land reported the endpoint separately on 12 August.
The endpoint accepts dimensions, metrics, date ranges, filters and sorting criteria in the request body. A successful query returns column headers, rows, an aggregate total row and a pagination token as structured JSON. That makes Campaign Manager 360 reporting easier to plug into software without first creating and saving a Report resource.
The limits are worth reading before anyone plans around this. Queries run for a maximum of 60 seconds, and Google says requests that exceed the limit return a 503 error, with the recommendation to narrow the request or fall back to the asynchronous Reports service. A response returns up to 1,000 rows per page, with further pages retrieved through a page token. The endpoint is capped at 120 requests per minute per user and 10,000 requests per day per project.
The CM360 API therefore offers two clear reporting paths. The new query endpoint suits smaller, interactive requests. The existing Reports service still handles large datasets, recurring jobs and downloadable CSV or Excel files.
Why this matters for marketers
Reporting products become easier to build
The immediate gain is not a new metric. It is less reporting plumbing.
Under the traditional workflow, an application may need to create or manage a report configuration, run it, wait for completion, check status, then download a file. The new route compresses that into a direct request and response for queries that fit inside its limits.
That matters for marketing dashboards, client portals, QA tools, anomaly checks and internal reporting products. A team wanting last-seven-days performance grouped by advertiser and campaign can request that structure directly rather than manage a report file first. The direction is consistent with Google’s recent Ask Advisor reporting update, which also shortens the distance between a marketing question and a usable view of the data.
Automated reporting gets a cleaner input
Structured JSON is easier to pass into applications, workflow tools, data services and AI-assisted analysis than a file that has to be generated, downloaded, parsed and stored first. This guide to AI PPC reporting covers the broader move from manual report assembly toward automated analysis.
But the Campaign Manager 360 API does not interpret the data. It does not decide which KPI matters. It does not know whether a conversion was qualified pipeline. It does not connect CM360 to your CRM.
For B2B SaaS marketing, that distinction matters more than query speed. A dashboard returning impressions, clicks and conversions faster is useful. A dashboard that cannot separate a demo request from a sales-qualified opportunity can still push a team toward the wrong budget decision, only quicker.
Faster queries support faster campaign checks
For teams already running CM360 inside a larger ad stack, this can support tighter monitoring. A tool built on the CM360 API could request a narrow slice of campaign data when spend spikes, delivery falls or a client opens a dashboard.
That does not make the underlying measurement instant. Synchronous retrieval describes how the query executes and returns, not how quickly the platform processes events. Normal data availability rules still apply. This is the same reason measurement keeps coming first in AI performance marketing: automation gets more useful once the underlying events, naming conventions and business definitions are reliable.
The business value is engineering time, not prettier charts
The strongest case for this update is operational. A lean marketing or analytics team spends less engineering time on report-file management and more on interfaces, alerts and analysis. Agencies can build faster reporting experiences. SaaS teams can make internal campaign tools easier to maintain.
Google has been moving more campaign planning and measurement into connected systems, a direction covered in this Google Marketing Live 2026 analysis. This update fits the same pattern, but from the infrastructure side rather than the campaign interface.
How the new endpoint compares with other reporting approaches
| Approach | Best fit | Output | Main tradeoff |
|---|---|---|---|
| reportData.query | Ad-hoc queries, interactive tools, dashboards | Structured JSON | 60-second execution limit and API quotas |
| Reports service | Large datasets, scheduled reporting, recurring exports | CSV or Excel files | More steps to configure, run, poll and download |
| BigQuery Data Transfer | Warehousing and broader analysis across stored data | BigQuery tables | More setup and a different workflow from direct API queries |
Google’s documentation makes the distinction fairly clear. reportData.query is designed for synchronous exploration and retrieval, while the Reports service remains better suited to heavier file-based jobs. BigQuery Data Transfer stays a separate option for loading Campaign Manager data into a warehouse.
The new method does not replace the older options. It fills the gap between file-based reporting and heavier data-warehouse workflows. That makes it relevant to teams working across Google’s wider ad stack, a business problem this coverage of the DV360 and Walmart Connect integration looked at from another angle: activation and measurement get more useful when data moves cleanly between systems.
What marketing teams should watch next
Start with one narrow Campaign Manager 360 reporting workflow. If a dashboard or internal tool currently waits for a generated CM360 report file, test the same use case through the Campaign Manager 360 API query endpoint and compare response time, development effort, reliability and completeness of the result.
Do not move every reporting job because the endpoint is newer. Large historical exports and scheduled data jobs still belong in the workflows Google recommends for them. The 60-second execution limit is a design boundary, not a challenge to engineer around.
Watch the quota as well. Interactive dashboards generate more requests than expected when several users refresh, filter or paginate at once. A sound implementation handles 429 and 503 responses rather than treating them as surprises.
Most importantly, keep the business definitions outside the API. Decide what counts as a qualified lead, an opportunity, pipeline contribution and a revenue event before automating reporting around them. A structured Google Ads audit is useful for the same reason: reporting quality depends on tracking quality before it depends on dashboard speed.
OneMetrik Takeaway
This update removes unnecessary steps from a specific part of advertising operations. That is useful, especially for teams building custom reporting systems or client-facing tools.
It is not a new attribution model and it is not an AI analyst. It is a cleaner pipe.
At OneMetrik, the practical test would be simple: use reportData.query for one high-frequency, narrow reporting task and measure whether it gets the team to a verified answer faster. If it does, expand from there. If the data model is messy, fix that first. For B2B SaaS marketing teams especially, the reporting layer is rarely the bottleneck. The Campaign Manager 360 API can shorten the path from request to report. The advantage still comes from asking the right question and connecting the answer to pipeline.