Meta Ads and Google Ads Data to Excel: A Practical Guide

Ad platforms hold the numbers you need for a report. Here are the practical ways to get them into a table.

Open the API Response to Table

Marketing reports usually start with impressions, clicks, spend, conversions and revenue per campaign and day. The platforms show these in their own screens, but a report needs them in one table that you can filter, join and chart.

There are two routes. The first is the report export. Both Meta Ads Manager and Google Ads can download a report as CSV or Excel. This needs no code and is the safest route for most teams. The second is an API. If an endpoint accepts a GET request with a bearer token or an API key, API Response to Table can call it and turn the JSON into a table. Some APIs only accept POST requests, which this tool does not support, so check the documentation of the endpoint you need and use the export when it does not fit.

Whichever route you use, expect to clean the data. Dates may come as text in different formats, currency values may carry symbols or thousands separators, and the same campaign may appear under two spellings. Data Transformation can trim spaces, change the date format, find and replace values and remove duplicate rows, and every step is recorded.

Then calculate your own metrics. CTR is clicks divided by impressions, CPC is spend divided by clicks and ROAS is revenue divided by spend. Calculate them from the totals, not by averaging row-level ratios, because an average of ratios gives the wrong answer when volumes differ. Compare your totals with the platform screen before you share the report.

Report files can contain personal data if they include lead or customer fields. Mask those columns before you share the file. Everything runs in your browser, but the figures are only as good as the export, so keep the original file next to the cleaned one.

Open the API Response to Table

Related tool pages

  • JSON API Response to CSV: Turn the JSON from an API into a CSV file. Nested fields become columns and you pick which list to use. Free, in your browser, with an optional token.

How to use the API Response to Table: step by step

  1. Export the report or call the API endpoint with API Response to Table.
  2. Open Data Transformation and trim spaces and fix the date format.
  3. Remove duplicate rows and rename columns to match your report.
  4. Download the file and compare the totals with the platform.

When to use the API Response to Table

  • Combine Meta and Google exports into one table
  • Convert an API response with ad insights to Excel
  • Prepare a weekly report file
  • Check that totals match the platform

Example

Input: GET https://api.example.com/users + Bearer token

Output: id,name,address.city 1,Ada,London

Frequently asked questions

How does the token work?

Choose Bearer token, API key in a header, or username and password, and paste the value. It is sent only to the API you call, kept in memory, and never saved or written to Data Lineage.

What if the API blocks the request?

Some APIs do not allow calls from other websites (CORS), so the browser blocks the request. Use an API that allows browser access, or ask its owner to enable CORS.

What happens to nested fields?

Nested objects are flattened into columns such as address.city. If the response has several lists, you can choose which one becomes the table.

Is it safe to use a token in API Response to Table?

Your token goes only to the API you call, straight from your browser. Data Utility never receives it or the response. It is kept in memory for that request, not saved, and not written to Data Lineage. Use a token with read-only access when you can.

Tip: Calculate CTR, CPC and ROAS from summed totals. Averaging row-level ratios gives the wrong answer.