Export Google Ads to JSON: What to Check Before You Reconcile
For solo traders reconciling Ads with a dashboard: report downloads have no JSON option, JSON comes from the REST API or a warehouse export, and month-end matching needs account time zone, conversion basis, and primary-action flags checked first.
Brand promotion: this article introduces Guangsuan's Google Ads management services.
A solo trader closing the month often needs one file that a personal dashboard can read: spend by campaign and day, matched to qualified actions. When the totals do not line up, the cause is usually set before download — the file lacks a stable key, mixes two date rules, or sums different conversion actions. Direct answer with conditions: for a closed-month reconciliation, record IDs and row grain, record range plus account time zone plus conversion-time versus click-time, limit the main total to primary actions, and handle micros once. Use CSV or XLSX for review, reserve JSON for the API or warehouse path, and check one action in one campaign group before changing bids.
Report downloads do not produce JSON
Google Ads report downloads do not include JSON; the download menu lists Excel CSV, TSV, PDF, XLSX, XML, and Google Sheets. 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 a one-off file, converting a CSV to JSON locally is often faster and has no vendor attached.
What each JSON path returns
The REST interface of the Google Ads API returns JSON representations of the same resources queried with GAQL. The Google Ads API supports two interfaces — gRPC and REST, and most official client libraries use gRPC while the REST interface uses JSON.
A GoogleAdsService query returns a list of rows carrying only the attributes, metrics or segments you selected. Field names use dotted names because they map directly to the GAQL fields you selected, for example campaign.id, campaign.name, metrics.clicks, metrics.conversions and metrics.cost_micros with segments.date for the period.
import json
# Field names mirror a GAQL query such as:
# SELECT campaign.id, campaign.name, metrics.clicks,
# metrics.conversions, metrics.cost_micros
# FROM campaign WHERE segments.date DURING LAST_30_DAYS
fixture_rows = [
{"campaign.id": "1234567890", "campaign.name": "Brand-Exact", "metrics.clicks": 412, "metrics.conversions": 18, "metrics.cost_micros": 26140000},
{"campaign.id": "1234567891", "campaign.name": "Generic-Long-Tail", "metrics.clicks": 903, "metrics.conversions": 11, "metrics.cost_micros": 88750000}
]
text = json.dumps(fixture_rows, indent=2)
print(text)Hypothetical teaching example with invented numbers, not a client result: the two rows above show shape only. Cost arrives in micros, so divide by one million once in account currency. The JSON validity check is genuine, but the numbers are invented teaching data.
The second JSON path is to land the data in a warehouse and export JSON downstream. If clicking through 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. That adds a project to maintain, so it suits a monthly routine better than a single file. For field background, see Guangsuan's guide to exporting Google Ads data to JSON.
Check dates and conversions before you reconcile
An export is only as good as the range and time zone behind it. Exports are dated in the account's time zone, which may not match your calendar or your CRM timestamps.
- Keep customer ID in the file, keep campaign ID next to campaign name because names are edited, and keep every split that defines a row, such as date, device and conversion action.
- Export the grain you will actually analyse. A monthly export can hide a bad week, while a daily export over a long range becomes hard to review.
- In a table or report, use the segment control to split data by day, week or month rather than exporting several ranges and joining them later.
- Name the file with account, report, range, basis and pull time, keep the raw download unchanged, and work in a copy.
Google Ads can attribute and report conversions on more than one basis, and the default column is not the only valid view. 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.
Only conversion actions marked as primary roll into the Conversions column and into 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.
Before you build a report on conversions, open the conversion settings and write down: the basis (conversion or click time), which actions are primary, the counting method and the attribution model. Changing any of them changes historical comparisons. If you rely on offline or CRM-confirmed leads, remember the export only shows what Google was able to record; sales-confirmed numbers live in your own system. For the general export workflow, see Guangsuan's guide to exporting Google Ads data and reading dates and conversions.
Fix the page first when clicks do not turn into enquiries
Before raising bids, separate whether traffic was off-target, the page did not carry the click, or the data was read without a clear basis. When search terms are too broad or regions do not match, review the search-terms report and adjust matching and negatives first.
When visits arrive but no enquiry follows, check landing-page fit before changing bids. If the ad promise and the page do not say the same thing, or product details, trust material or contact entry are thin, review page relevance, loading, product information and the enquiry path. An export is only useful if the campaign structure behind it is sound — clean naming, one intent per campaign, and conversion tracking that matches how leads actually arrive.
Hypothetical teaching illustration with invented figures, not a client outcome: an export logs 42 ad-recorded contacts in a month. Sales qualifies 14 under a written definition, 10 dated inside that month and 4 dated in the next month, with 2 reaching order. Each total describes a separate stage, so none contradicts another. When few contacts meet the written qualified mark, review query intent and page fit before adjusting bids.
Where Guangsuan fits
Guangsuan's Google Ads management service covers account structure, search terms, landing pages, conversion checks and reporting. Scope, fees and handoff are set in a contract, with no fixed enquiry promise. Details are on the Guangsuan Google Ads management service page. For a first review, bring the action list with primary flags plus one annotated export that shows basis and time zone.
FAQ
Can Google Ads download JSON directly?
No. Use the REST API path for automation, or a warehouse path for a recurring match.
Does a file that parses as JSON reconcile cleanly?
No. Parsing says nothing about row grain, micros handling, date rule, or which actions were summed.
Should a missing term be read as 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.