How to Connect Facebook Ads Reporting to Google Sheets Automatically

What you'll need

• Access to the Facebook ad account (and Business Manager admin rights, or someone who has them)
• A Meta developer app, used to generate an access token for the Marketing API
• A Google account with the destination spreadsheet
• An automation tool; this guide uses n8n, but the same flow works in Make or custom code

Step-by-step

1. 1Get an access token. In your Meta app, generate a token with the ads_read permission. For ongoing reporting, use a long-lived token, ideally for a Business Manager system user, so it doesn't expire after a few hours.
2. 2Decide the metrics and breakdown. Typical fields are campaign name, spend, impressions, clicks, CTR, CPC, results and cost per result, broken down by day or campaign.
3. 3Create a schedule trigger. In n8n, add a Schedule Trigger node, for example every morning, or hourly for live dashboards.
4. 4Call the Insights endpoint. Use an HTTP Request node to call the ad account's insights endpoint with your chosen fields, date range (such as yesterday or the last 7 days) and level (campaign, ad set or ad).
5. 5Transform the response. Flatten nested values, convert currency and percentages to plain numbers, and add the report date so every row is traceable.
6. 6Write to Google Sheets. Use the Google Sheets node to append new rows, or update rows keyed by date and campaign so reruns don't create duplicates.
7. 7Add a summary (optional). Post a short Slack message with yesterday's spend and top campaigns, linking to the sheet.
8. 8Handle errors. Route failures to an alert channel so an expired token or API change is noticed the same day.

Common pitfalls

• Expiring tokens: short-lived user tokens stop working quickly. Use a long-lived or system-user token and alert on authentication errors.
• Attribution windows: recent days' results can still change as conversions come in, so re-pull the last few days rather than only yesterday.
• Duplicates: appending blindly on every run duplicates data. Upsert by a unique key such as date plus campaign ID.
• Rate limits: large accounts or frequent runs can hit API limits. Request only the fields you need and avoid running more often than necessary.

Why automate it

Manual exports are slow and easy to get wrong, and they're only as fresh as the last person who ran them. An automated pipeline keeps numbers current, removes copy-paste errors and frees the team to act on the data instead of assembling it. I built this kind of pipeline for the Facebook Ads Data Live Report automation.

FAQ