If you run campaigns on both Google Ads and Meta, you know the Monday morning ritual. Log into Google Ads, export. Log into Meta Business Manager, export. Paste it all into a spreadsheet and hope the columns line up. By the time the numbers make sense, it is Tuesday.
It eats a lot of hours. Dataslayer's marketing reporting guide says 82 per cent of marketers spend five or more hours a week on manual reports, crediting Meta research it does not link to, and Dataslayer sells reporting connectors, so read the number with that in mind. The bigger cost is that, with your numbers in separate dashboards, every budget call gets made on half the picture.
In this walkthrough, we will connect both platforms to a single dashboard using Make (formerly Integromat). You will pull campaign data from both APIs every night, normalise it, and feed it into Looker Studio for a dashboard that refreshes on its own. A free Make account covers a small setup, and the cost section below shows where it runs out.
What you need to build the dashboard
- A Make account (the free tier covers roughly 30 campaign rows a day; the arithmetic is further down)
- Google Ads account access (Manager or admin level)
- Meta Business Manager access with ad account permissions
- A Google account for Sheets and Looker Studio
Connect Google Ads to Make
In your Make dashboard, add a new scenario. Search for the Google Ads Reports app and select the Run a Campaign Report module. Authenticate with your Google Ads account and select the campaign fields you want to track: campaign name, impressions, clicks, cost, conversions, conversion value, and date.
Make's Google Ads Reports integration supports campaign, custom, and account-level reports. For a daily dashboard, set the date range to yesterday and schedule the scenario to run each morning.
Keep Google Ads in its own scenario. Make passes every bundle a module returns through each module after it, one at a time (Make's scenario execution docs walk through the same behaviour). A Google report with twelve campaigns returns twelve bundles, so a Meta module chained after it would run twelve times and write twelve copies of the Meta data. Two scenarios writing to one sheet avoid that, and each costs only the credits it uses.
Connect Meta Ads to Make
Create a second scenario. Meta's numbers come from the Facebook Insights app's Get Insights module, which returns insights for an ad, ad set, ad account or campaign. Set the level to campaign, the date to yesterday, and pick the fields that match what you pulled from Google: campaign name, impressions, clicks, spend, conversions. Earlier versions of this guide pointed to the Facebook Ads Campaign Management app, which is for managing campaigns; the insights module sits in Facebook Insights.
Make's Sync Facebook Ads data to Google Sheets template does this step for you. It runs at 8:00 every morning on the previous day's data, using Facebook Ads Campaign Management, Facebook Insights, Flow Control, Tools and Google Sheets.
Normalise the data in Make
Google Ads calls it "cost" and Meta calls it "spend", and the two count conversions over different windows. Map both onto one schema inside the Google Sheets module's field mapping, which does the same job as a separate Set variable module without spending an extra credit on every row:
Platform: "Google Ads" or "Meta Ads" Date: same format (YYYY-MM-DD) Campaign: campaign name from source Spend: cost (Google) or spend (Meta) Impressions: from source Clicks: from source Conversions: from source Cost per conversion: calculated field
This normalisation step is what makes the dashboard useful. Without it, you are comparing apples to slightly different-shaped apples.
Write to Google Sheets
Add a Google Sheets module set to Add a Row at the end of each scenario, pointing both at the same sheet with columns that match your normalised schema. Each run appends one row per campaign. On larger accounts, an Array aggregator followed by Bulk Add Rows (Advanced) writes the whole day in one call instead of one call per campaign.
Use a separate sheet as a raw data store and another sheet with SUMIF formulas for your weekly and monthly aggregates. This keeps your dashboard fast even as data grows.
Connect to Looker Studio
Open Looker Studio and create a new report. Add your Google Sheet as a data source. Build a dashboard with:
- Total spend across both platforms (single number card)
- Spend by platform (bar chart)
- Cost per conversion by platform (comparison chart)
- Week-over-week trend (line chart)
- Campaign-level performance table
Looker Studio is free and refreshes automatically from the sheet. Your Make scenario runs every morning, updates the sheet, and the dashboard reflects the latest numbers by the time you open it.
Add alerts and optional extras
Once the base dashboard is running, you can extend it with Make's scheduling and notification modules. Set up a Slack message when spend exceeds a threshold, or a weekly email summary to stakeholders. The data is already flowing, so adding outputs is just dragging in a new module. For a deeper look at how attribution changes when you connect those dots, read our guide to unified ad attribution across Meta, LinkedIn and Google Ads.
A Monday without manual exports
Before automation, your Monday morning was spent exporting, reconciling, and hoping nothing got misfiled. After, it looks like this:
- Open one dashboard instead of two or three platforms
- See total spend, CPA, and ROAS across both channels in one view
- Compare Google Ads and Meta performance on the same metrics
- Spot budget shifts the morning after they happen, once the scenarios have run
As the Cometly guide to unified marketing analytics puts it, the bigger cost of fragmented data is the revenue you miss because you are too slow to see what is working and scale it.
Where the merged numbers still drift from each platform
Once the scenario runs for a couple of weeks, the totals in your sheet will not exactly match what Google Ads and Meta each show on their own dashboards. The two platforms measure with different rulers, so the gap is expected, and knowing where they differ stops you from chasing phantom errors in your Make setup.
Google Ads defaults to a 30-day click-through conversion window, and conversions can be reported up to 90 days after the click if you have extended that window. Meta's standard attribution setting credits conversions up to 7 days after a click and up to 1 day after a view. Meta also narrowed what counts as a click on 3 March 2026: only link clicks now earn click-through credit, and conversions after a like, share or save are reported separately as engage-through. Meta's click column can drop after that date with no change to your campaigns. A conversion Meta stopped counting last week can still land in Google's numbers next week, and neither platform's total is final until its own window closes.
| Where they differ | Google Ads | Meta Ads |
|---|---|---|
| Attribution window | 30-day click default, extendable up to 90 days | 7-day click plus 1-day view; since March 2026 a click means a link click |
| When totals settle | Conversions keep arriving after the click; Google recommends ending report ranges at least 30 days back for complete data | Conversions keep arriving as click windows close, and modelled results update after the fact |
| Timezone | Reports in the account's timezone | Reports in the ad account's timezone |
Set both ad accounts to the same timezone, and judge performance on closed weeks rather than the last day or two. The sheet's job is to show direction early and totals accurately, and it does both once you stop expecting yesterday's number to be final.
How much does this cost?
Make's pricing page, read on 6 October 2026, lists a free plan with up to 1,000 credits a month and a paid Make plan at USD 9 a month for 5,000 credits. It also says each module action, such as adding a Google Sheets row, counts as one credit, while routers and error handlers count as none.
That rule makes the bill easy to work out. With fields mapped inside the Sheets module, each scenario spends one credit on the report and one per campaign row. Ten Google campaigns and ten Meta campaigns come to 22 credits a day, or about 660 over 30 days, which fits the free plan. Put a Set variable module in each scenario and the same accounts cost 42 credits a day, about 1,260 a month, which does not. This is our arithmetic from Make's published rule, so check the credits counter in your own scenario history after the first week.
| Option | Monthly cost | What it covers |
|---|---|---|
| Make free | $0 | 1,000 credits, about 30 campaign rows a day across both platforms |
| Make paid | USD 9 | 5,000 credits, about 160 campaign rows a day |
| Looker Studio | $0 | Dashboards and reports off the shared sheet |
| Supermetrics | USD 39 billed yearly, 49 monthly | Starter: one destination such as Looker Studio, two data sources, so Google Ads and Meta fit exactly |
A two-platform dashboard costs nothing on Make's free plan for a small account and USD 9 a month once the campaign count outgrows it.
Supermetrics' Starter plan covers the same two sources for USD 39 a month on a yearly bill, with the normalisation done for you. Make costs less and gives you control over every field, and the price of that is maintaining the mapping yourself when a platform renames a metric.
Frequently asked questions
Can I connect both Google Ads and Meta to one dashboard?
Yes. Make connects to both natively. One scenario runs the Google Ads Reports app and a second runs the Facebook Insights app; both map their fields onto one schema and write to the same Google Sheet, which feeds a Looker Studio dashboard.
How much does it cost to automate ad reporting?
Make's free plan gives 1,000 credits a month, which covers about 30 campaign rows a day across both platforms at one credit per row. The Make plan is USD 9 a month for 5,000 credits. Looker Studio is free.
How many hours does automated reporting save?
We could not find an independent measurement. Dataslayer, which sells reporting connectors, reports that 82 per cent of marketers spend five or more hours a week on manual reports. Your own saving is the time your team spends on exports and spreadsheet fixes today, so time one Monday before you build.
Is Looker Studio enough or do I need something more powerful?
Looker Studio with native connectors is free and enough if you only need to visualise Google Ads and Meta data. It falls short when you need to cross ad spend with real sales from your CRM or apply custom business rules. That is where a custom build adds value.
Do I need a developer to set this up?
No. The marketing team can set up Make scenarios using the visual drag-drop interface. Make has pre-built templates for syncing Facebook Ads data to Google Sheets. The steps in this guide walk through the entire setup with no coding required.
Once both scenarios run, Monday starts with a dashboard that already holds last week's numbers from both platforms, and the time that went on exports goes on deciding where the budget moves next.
This is something we do at Supernodes. If a unified ad dashboard sounds like something your team could use, speak with us about a two-week pilot. We audit your current setup, connect the platforms, and leave you with a dashboard that refreshes itself.