Export Google Ads to JSON for Month-End Reconciliation: Routes, Dates and File Checks
For month-end reconciliation: Google Ads has no JSON download button, the two realistic JSON routes, and which date, conversion and field notes to lock before matching CRM.
Brand promotion: this article introduces Guangsuan's Google Ads management service for reporting and reconciliation help.
If you close the month as an independent trader and need Google Ads data next to conversions, write one question before opening Google Ads. Example: which campaigns spent in the closed month for which conversion actions, and under which date rule? That sentence fixes the period, the row detail and the action list before any download.
No JSON button in the interface
You cannot export Google Ads data to JSON from the interface, because there is no JSON button. The native download offers spreadsheet and XML formats, and XML is not JSON.
Google Ads Help, in Create, save, and schedule reports from your statistics tables, lists the download formats you get when you click the download icon above a table and choose Download: "Available formats include Excel CSV, TSV, PDF, XLSX, XML, and Google Sheets." JSON is not one of them.
XML is the closest native format and is easy to confuse with JSON, but they are different languages with different audiences. If a downstream tool insists on JSON, converting XML or CSV to JSON is a local programming step, not an export option.
For the native options and the API route in full, see Guangsuan's guide to exporting Google Ads data to JSON.
Two realistic JSON routes
If you genuinely need JSON — for a script, a data pipeline, or an app — there are two realistic routes: query the Google Ads API through its REST interface, which returns JSON, or land the data in a warehouse and export JSON downstream.
1. REST API returns JSON
The Google Ads API supports two interfaces — gRPC and REST. The REST interface uses JSON representations of the same resources. Queries are written in the Google Ads Query Language (GAQL), and a GoogleAdsService query returns a list of GoogleAdsRow instances, each carrying the attributes, metrics or segments you selected.
You need a developer token and an authenticated client. Keep the developer token and credentials in a secured file or secret store, and apply for a higher access level only when test limits no longer fit production use.
2. Warehouse then JSON
If the API is more engineering than you want, the data can land somewhere else first — a BigQuery transfer, or a reporting connector — and you export JSON from there. This is a legitimate route, but it adds a dependency: a vendor, a project, or a scheduled transfer that you now maintain.
For a one-off file, converting a CSV to JSON locally is often faster and has no vendor attached. Keep that script versioned and test it on a small slice checked by hand.
What the JSON shape looks like
What we can show honestly is the JSON shape a query produces. The example below does not call the API and contains no credentials.
import json
rows = [{"campaign.id": "550201", "campaign.name": "Demo-Brand", "metrics.clicks": 180, "metrics.conversions": 7, "metrics.cost_micros": 12400000}]
print(json.dumps(rows, indent=2))The above is a hypothetical teaching illustration with invented figures, not account data. The keys use dotted names because they map directly to the GAQL fields you selected. Cost arrives in micros in account currency, so divide once by one million in a noted place.
Date, conversion and field notes to lock first
An export is only as good as the range and time zone behind it. Record both with the file.
- Range and grain: set date range first, then add day, week or month segments where a time series is needed. Export the grain you will actually analyse. Keep account ID, campaign ID beside campaign name, and each split that defines a row, such as date, device and conversion action where used.
- Time zone: exports are dated in the account's time zone, which may not match your calendar or your CRM timestamps. Write the zone on the file and check one date row after opening.
- Conversion basis: Google Ads can attribute and report conversions on more than one basis. Conversion-time reporting counts a conversion in the period when it happened; click-time reporting counts it in the period when the click happened. If a customer clicks on the last day of the month and buys a week later, the two bases put that conversion in different months. Keep one basis on both sides and record window, counting method and attribution model beside the file.
- Which actions count: only primary actions feed the Conversions column used for bidding. Secondary actions — often micro-conversions such as a page view or a click-to-contact — are reported separately and should be labelled as such in your export. The export only shows what Google was able to record; sales-confirmed numbers live in your own system.
File check before you reconcile
- Range, level and totals: is the range closed, is the level account, campaign or group as intended, and do totals for clicks and cost match the interface summary?
- Open cleanly: open CSV through Data > From Text/CSV, force UTF-8, confirm delimiter, turn cost and clicks from text into numbers, and check one date row before trusting day-month order.
- Join keys: keep raw download unchanged, work in a copy, and name the copy with account, range, basis and pull time so a retry replaces the same slice.
- Narrow first pass: limit to one primary action, one campaign group and one closed period plus first days of next month to catch late entries. Check counting and repeated uploads before calling a remainder unexplained. Leave any leftover gap marked as open.
When reports are hard to read because structure, search terms or tracking are unclear, Guangsuan Google Ads management covers account structure, search terms, landing pages, conversion checks and reporting, with scope and fees set in a contract and no fixed enquiry promise.
FAQ
Can I download JSON directly? No. Use the REST API path or a warehouse path, or convert a one-off CSV locally with a versioned script.
Does a file that parses as JSON reconcile cleanly? No. Parsing says nothing about grain, micros, zone, basis or which actions were summed.
Does a missing term mean zero? Not yet. Very quiet rows can drop from a filtered view, so confirm filters and grain first.
Trade with the toolkit the desks use.
Join 41,000+ active traders running institutional-grade scanners, calculators, and risk dashboards — accessible from any browser, refreshed in under 200ms.