![\"Flow](\"https:\/\/www.lukaswojcik.com\/blog\/wp-content\/uploads\/diagrams\/performance-dashboard-en.png\")
Step 1: Connecting Both Ad Platforms<\/h2>\n
Google Ads has a native Looker Studio connector that exposes Cost, Conversions, Conversion Value, and Date directly. Meta does not ship a first-party Looker Studio connector; the practical path is a certified partner connector (or a scheduled export into a sheet or table Looker Studio can read) that surfaces the same shape of data from Meta Ads \u2014 Spend, Results, Conversion Value, and Date. Both data sources need to reach the dashboard as their own connections before anything gets combined.<\/p>\n
Step 2: Building the Blend<\/h2>\n
Blend Data (under Resource, or from the toolbar depending on the Looker Studio version) creates a new table by joining data sources on one or more shared dimensions \u2014 Date is the natural join key here, since campaign names rarely match across platforms. Each source in the blend is aggregated on its own before the join runs, so Cost and Conversions should be added as SUM-aggregated metrics from each source rather than left at their default aggregation, which avoids inflating totals through row duplication on the join.<\/p>\n
Step 3: The Join Gap That Loses Days<\/h2>\n
A blend behaves like a left join anchored on the first table added: dates present in the second source but missing from the first can disappear from the blended result instead of showing up as zero. This surfaces in practice as a paid dashboard whose weekly total quietly excludes a day where, say, Meta Ads had spend but Google Ads happened to have none. The reliable fix is picking whichever platform has guaranteed daily activity as the first table in the blend \u2014 or joining both against a small calendar table containing every date in the reporting range, so every day survives the join regardless of which platform spent on it.<\/p>\n
Step 4: Calculating Blended ROAS and CPA<\/h2>\n
With Cost and Conversions available from both platforms inside the blended table, three calculated fields produce the whole-business view:<\/p>\n
Blended Cost = SUM(Google Ads Cost) + SUM(Meta Ads Spend)\nBlended Conversions = SUM(Google Ads Conversions) + SUM(Meta Ads Results)\nBlended Conversion Value = SUM(Google Ads Conv. Value) + SUM(Meta Ads Conv. Value)\n\nBlended ROAS = Blended Conversion Value \/ Blended Cost\nBlended CPA = Blended Cost \/ Blended Conversions<\/code><\/pre>\nEach platform’s own conversion value field needs to be normalized to the same currency before this addition means anything \u2014 a blend does not convert currencies on its own.<\/p>\n
Step 5: Laying Out the Dashboard<\/h2>\n
Four scorecards \u2014 Blended Cost, Blended Conversions, Blended ROAS, Blended CPA \u2014 give the top-line business number at a glance. A time series chart plotting Google Ads cost, Meta Ads spend, and Blended Cost together shows how much of the trend is driven by which platform. Underneath it, a table broken down by date keeps the daily detail available. Nobody has to leave the dashboard to look up either platform’s own interface.<\/p>\n
Staying Inside the Guardrails<\/h2>\n
A blended total is a reporting convenience, not a cleaned-up measurement. When someone sees both a Google and a Meta ad before buying, both platforms count that same purchase as their own conversion. This is a common outcome. The blended figure adds the two together and therefore counts the purchase twice, which makes blended CPA look better than it would after the double count is removed.<\/p>\n
The right use for the blended dashboard is a fast read on total spend and a rough sense of direction on combined ROAS. A cross-channel figure that will hold up needs a shared identifier instead: an order ID, or a single analytics platform both channels report into. A Looker Studio blend on date alone will not do it.<\/p>\n