Google has added a reportData.query endpoint to the Campaign Manager 360 API that returns reporting data in one synchronous request. Developers can define dimensions, metrics, and filters in the request body and receive structured JSON. Creating a report resource, starting the job, polling its status, and downloading a file are no longer required for suitable queries.
The change matters to agencies and enterprise teams connecting media performance to dashboards and decision systems. Interactive reporting, campaign-health checks, and support tools can answer focused questions with fewer operational steps. The new endpoint does not retire the existing Reports service. Traditional reporting remains the preferred path for large datasets, scheduled jobs, and CSV or Excel output.
How does the new endpoint work?
reportData.query requests Campaign Manager 360 reporting data synchronously. A request can specify date range, dimensions, metrics, filters, sorting, and pagination. The response arrives as JSON rather than a downloadable file, allowing an application to transform it directly into a table, alert, or analytical layer.
The clearest difference is the absence of the report-resource lifecycle. In the traditional flow, an application creates a report configuration, starts a run, polls until completion, and downloads the result. For an appropriate query, the new flow completes in one request-response cycle.
Queries can run for up to 60 seconds. That limit shows this is not an invitation to request an entire history every time a user opens a page. The strongest use case is a controlled date range with focused dimensions. Combining a huge advertiser, campaign, creative, and daily breakdown in one query can still create timeout or pagination pressure.
This text-free Fark Studio diagram compares one synchronous query with the create, wait, and download report workflow. It is not an API console.
Who is affected?
Agency engineering teams, marketing data teams, BI developers, media operations, and enterprise advertisers using Campaign Manager 360 as a data source are directly affected. A small team that works only in the Google Ads interface may see little immediate value. This is a data-access infrastructure update, not a campaign optimisation setting.
An agency can use the endpoint to show the last 24 hours of delivery in a client portal, compare plan with actuals, or investigate a creative anomaly without waiting for a prebuilt file. A support team can also ask a narrow question while diagnosing an issue.
Applicability in Türkiye depends on existing CM360 adoption. For a brand that does not use the platform, the update is informational. For a regional agency or advertiser that already moves CM360 data into a warehouse, it can reduce integration complexity and dashboard latency.
Does the new method replace traditional reporting?
No. Google's documentation recommends the Reports service for large datasets, scheduled reporting, and workflows that require downloadable CSV or Excel files. reportData.query is better suited to interactive and focused requests. Many systems will use both.
A nightly ETL job that archives the previous day for every account may stay on the classic report path. A summary that loads when a user changes a date filter can use the new endpoint. Teams should compare latency, volume, repetition, and output format instead of forcing every job onto one method.
This Fark Studio decision visual routes small, fast requests to an interactive dashboard and larger scheduled loads to a file archive. It is not an official architecture diagram.
What is confirmed and what remains uncertain?
The endpoint is available in Campaign Manager 360 API v5, returns synchronous JSON, does not require a report resource, permits up to 60 seconds of query execution, and coexists with the Reports service.
The real speed and cost benefit will vary. Query width, account structure, quota use, network latency, and application caching all matter. Google does not promise one response time or cost reduction for every dashboard.
Data parity also requires testing. If the old file report and new JSON query use different dates, time zones, filters, conversion definitions, or dimensions, different totals are expected. That difference should not automatically be blamed on the endpoint.
What should teams in Türkiye do now?
1. Classify current CM360 report jobs as interactive, scheduled, or archival. 2. Choose three narrow, high-latency questions for a pilot. 3. Match date, time zone, filter, dimension, and metric definitions exactly between old and new methods. 4. Build automated checks for row counts, totals, nulls, and pagination. 5. Split queries approaching the 60-second limit by date or account scope. 6. Monitor quota use, errors, latency, and retry behaviour. 7. Apply short caching to interactive requests and durable storage to archival jobs. 8. Keep the Reports flow until the pilot proves parity and operational value. 9. Display the dashboard's last-updated time and avoid turning “real time” into a zero-latency promise.
Where should teams wait?
Do not migrate the entire reporting estate at once. Prove parity and operational benefit in a focused use case. Do not convert large CSV exports into synchronous queries only because the endpoint is new. Keep the rollback path until production behaviour under quota and the 60-second limit is understood.
Integration inventory should not wait. A team cannot choose the right API path if it does not know which reports serve interaction, archive, billing, or audit needs.
Fark Studio perspective
“Real time” often creates a promise of faster decisions before measurement quality is established. The real value is asking a necessary question with fewer operational steps while keeping its scope explicit. A fast, poorly defined metric can be more dangerous than a slow report.
Digital marketing, performance marketing, and web development teams should own the metric dictionary and integration choice together. If you want to separate CM360 reporting into dashboard, archive, and alert use cases, plan a measurement-architecture review with Fark Studio.
Sources
Google Ads Developers Blog, Query report data with Campaign Manager 360, August 12, 2026; official endpoint announcement.
Google for Developers, Query report data, updated July 14, 2026; request structure, fields, and implementation detail.
Google for Developers, Reporting overview, updated July 14, 2026; official guidance for choosing synchronous queries or the Reports service.
Search Engine Land, Google adds real-time reporting endpoint to Campaign Manager 360 API, August 12, 2026; industry summary of the impact.
