Google introduced a new reportData.query endpoint for the Campaign Manager 360 API, letting developers retrieve campaign performance data without generating downloadable reports. It targets real-time reporting, dashboards, and ad-hoc analysis.
The endpoint queries campaign performance data synchronously and returns structured JSON directly in the API response.
| Existing Reports API | reportData.query | |
|---|---|---|
| Setup | Requires creating a Report resource | None |
| Flow | Run report → poll for completion → download file | Define dimensions, metrics, filters in the request body |
| Response | CSV / Excel file | JSON returned directly |
| Constraint | Suited to large datasets | Queries run up to 60 seconds |
The old workflow required creating a report configuration, running it, polling for completion, and downloading the generated file. Four steps collapse into one request.
Google was explicit about where the traditional Reports service remains preferred:
This is a split by use case, not a replacement. The 60-second query ceiling makes clear the new endpoint was not designed for bulk extraction.
Tooling for catching gaps in ad data pipelines before they propagate is also expanding — see Google Adds a Campaign Data Import Validation Report.
The move from file-based reporting toward API-native querying is the broad direction of ad data infrastructure. Lower implementation cost does not make a dashboard useful — that is still a metric design problem.
It removes the need to create a Report resource first. Dimensions, metrics, and filters go in the request body, and structured JSON comes back synchronously in the response.
Queries can run for up to 60 seconds, a limit set for interactive reporting and real-time applications.
No. Google says the traditional Reports service remains preferred for large datasets, scheduled reporting jobs, and applications that depend on downloadable CSV or Excel files.
For internal dashboards, ad-hoc analysis, and short-interval metric monitoring. Bulk data backfills are still better served by the existing Reports API.
To apply what you just read to your own site, start with a free audit of where things are now.
A strategist replies within 24 hours on business days.
From August 20, Naver Place Ads appear in Naver Maps transit and address detail views, starting with restaurants — up to 2 per screen, single image, existing bidding unchanged.
LLM visibility depends on your whole digital footprint, not your website. Teams are still built by channel. Mordy Oberstein's uncomfortable advice: do not reach for an action plan yet.
Review content incrementality is the metric affiliate platforms cannot give you. Here is how one creator ends up paid four times over, and the six questions that separate acquisition from margin leakage.