Brand promotion: this article introduces Guangsuan's Google Ads management service.
A B2B paid-media owner asks for Google Ads data in JSON, loads the file, and finds totals that do not line up with the CRM. The file can be valid JSON and still not be reconcilable. A reconcilable file is decided before download: which question it answers, which fields define a row, which date rule it uses, and which conversion actions it counts.
Short answer with conditions: Reporting downloads in Google Ads do not include JSON; JSON comes from the API REST interface or from a warehouse layer that exports downstream. Before either path is used for attribution, fix customer and campaign IDs plus row grain, record range with account time zone and click-time versus conversion-time, separate primary actions from secondary steps, and convert micros once. Then reconcile one action, one campaign group, and one closed period.
Start from the attribution question
Write one sentence before you open Google Ads. Example: which campaign groups produced sales-accepted requests in the closed month, and at what spend. That sentence selects range, detail, and the conversion action carried forward.
A campaign total answers spend. A campaign-by-day split answers timing. Search terms placed beside the bought keyword answer intent. Those are different grains and need different files. Do not force them into one table.
There is no JSON button in the interface
When you download a table in Google Ads, the available formats are spreadsheet, XML, PDF, and Google Sheets formats. JSON is not one of them. XML is near JSON in a menu but is read by different tools.
If a downstream tool asks for JSON, converting a downloaded CSV or XML file locally is an allowed route. It is also a route you own: keep that script under version control, name an owner, and test it on a small slice checked by hand.
Route 1: the 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, and a query returns rows carrying only the attributes, metrics, or segments selected.
That has a direct consequence for attribution: the JSON contains what the query asked for. If campaign ID, date segment, or conversion action is missing from the query, no downstream join restores it.
Access needs a developer token, and its access level sets daily operation limits. A new project starts at Test Account Access, which works on test accounts, before you apply for a higher level. Permissible use decides which features you are allowed to call. Keep tokens and credentials in a secured store and never paste them into a report.
Route 2: land the data in a warehouse, export JSON downstream
A BigQuery transfer or reporting connector can hold the data and produce JSON from there. That route adds a dependency that someone maintains: a vendor, a project, or a scheduled transfer.
For a single file, local CSV-to-JSON conversion is the shorter path. For a recurring join against CRM revenue, the warehouse route keeps history and lets two people reproduce the same total. For the field definitions behind both routes, see Guangsuan guide to exporting Google Ads data to JSON.
Fix identity and grain before the file leaves the account
Display names are edited; IDs are not. Keep customer ID in the file. Keep campaign ID beside campaign name. Keep every split that defines a row, such as date, device, network slice, geographic slice, and conversion action where used.
A campaign total and a campaign-by-day-by-device file are different grains. A key that ignores that difference lets valid rows overwrite each other. Export the grain you will actually analyse. Name the file with account, report, range, basis, and pull time. Keep the raw download unchanged and do analysis in a copy, so a retry replaces the same slice instead of doubling spend and clicks.
Put time zone and conversion basis in writing
Exports are dated in the account time zone, which may not match calendar or CRM timestamps. Write the time zone on the file, not in a chat message. A lead recorded late on the last evening can fall into different months on the two sides without anyone making a mistake.
Google Ads can report conversions on more than one basis. Click-time reporting places the event where the click happened. Conversion-time reporting places it where the conversion happened. Neither basis is wrong. What breaks a comparison is mixing them in one period comparison.
Before you build a report on conversions, open conversion settings and write down basis, window, counting method, and attribution model. Changing any of them changes historical comparisons. Secondary actions are reported separately and should be labelled as such in the export, because a total that mixes primary and secondary actions describes more actions than the business agreed to count.
Cost in API rows arrives as micros in account currency, so convert once by dividing by one million in a noted place. Do not add raw totals across currencies. For the general download workflow and date reading, see Guangsuan's companion routine for exporting Google Ads data and reading dates and conversions.
Reconcile in a fixed narrow order
Keep clicks, platform conversions, qualified enquiries, and closed revenue as four separate counts. An export from Google Ads shows what Google was able to record. Sales-confirmed numbers stay in your own system.
- Select one primary action, one campaign group, and one closed period plus the first days of the next month to catch late entries.
- Align basis, range, and time zone on both extracts.
- Separate ad-sourced records from organic and referral records.
- Check counting settings, filters, and repeated uploads before calling a remainder unexplained. A filtered view can omit very quiet rows.
As a hypothetical teaching illustration with invented figures, not a client outcome: an extract logs 34 ad-recorded contacts in a closed window. Sales accepts 12 as qualified under a written definition, 9 dated inside that window and 3 dated in the first days after it, with 2 reaching order. Each total describes a different stage, so the file and the CRM can both be right while showing different numbers.
Where Guangsuan fits
Guangsuan's Google Ads management service covers account structure, search terms, landing pages, conversion checks and reporting. Scope and fees sit in a contract, with no fixed enquiry promise. That matters here because some causes sit in the account, not the file: a conversion action recording the wrong step, a landing page that does not match the query, or tracking deployed but never checked.
For a first review, bring the action list with primary status marked plus one annotated extract that shows basis and time zone. Details are on the Guangsuan Google Ads management service.
FAQ
Can I export JSON directly from Google Ads? No. Use the API REST path or a warehouse path, or convert a CSV locally under version control.
Does a file that opens cleanly join cleanly? No. Readable layout says nothing about grain, money units, date basis, or which actions were summed.
Click time or conversion time for month-end? Use the basis that answers the opening sentence and keep it on both sides, with window and account time zone written on the file.