How to Build a Marketing Dashboard in Looker Studio, Step by Step

How do you build a marketing dashboard in Looker Studio?

A Looker Studio marketing dashboard is built by connecting Google Ads and GA4 as native data sources, then adding charts, a date range control, and calculated fields such as ROAS or CPA on top of them. Looker Studio itself carries "No charge," stated verbatim on Google's pricing page as of August 12, 2026, so the entire build runs on free native connectors until a team chooses to add a paid pipeline.

This guide covers what to have ready before opening Looker Studio, a page-one KPI layout split by audience, the full build sequence, the calculated-field formulas that turn raw rows into ROAS and CPA, the mistakes that quietly break a working dashboard, native automation and sharing, and how Looker Studio's unpublished native limits compare to paid pipelines like Supermetrics and Windsor.ai. Readers who want to see a finished Google Ads source next to other channels can start with the Google Ads integration page.

What do you need before building a marketing dashboard in Looker Studio?

Building a marketing dashboard in Looker Studio requires a Google account with access to both the Google Ads account and the GA4 property, a Looker Studio account signed in under that same identity, and a decision on which KPIs belong on page one before adding a single chart. No coding, API key, or developer token is required for the native connector path.

• A Google account with Google Ads and GA4 access. View-only access on both is enough to build a report -- the connector inherits whatever permission level the signed-in Google account already has.
• A free Looker Studio account. Tied to the same Google identity, with no separate signup step and no charge, per Google's pricing page, as of August 12, 2026.
• The specific Google Ads account (or MCC ID) and GA4 property ID. An MCC (manager account) lets you add several child accounts as separate data sources and blend them later, the same way multiple GA4 properties can sit in one report.
• A decision on page-one KPIs. Deciding this before building avoids reworking scorecards and charts after the fact.
• Optionally, a Google Sheets source. Useful for manual targets or budget figures that don't live in either Google Ads or GA4.

View-only access on both Google Ads and GA4 is genuinely enough to build a working report; the connector never asks for more than the signed-in account already holds. An MCC setup adds one more layer: instead of a single Google Ads account, several child accounts can each be added as their own data source, then blended together inside the report. None of this requires code or a developer token -- direct Google Ads API access outside Looker Studio's interface carries its own rate limits. Looker Studio's catalog includes Google Ads and thousands of other data sources through native and community connectors, including the Google Analytics integration most marketing dashboards pair it with.

What KPIs belong on a marketing dashboard for an SMB owner vs. an agency client?

A marketing dashboard's page one should differ by audience: an SMB owner needs a handful of outcome metrics -- spend, conversions, CPA, and ROAS -- at a glance, while an agency client report typically adds a channel-by-channel breakdown, campaign-level trends, and a period-over-period comparison. Both layouts pull from the same blended Google Ads and GA4 data; only the depth of detail differs.

An SMB owner's page one works as scorecards for total spend, conversions, CPA, and ROAS, plus the top-performing campaign, with one trend line comparing the current period to the prior one -- all on a single page a busy owner can scan in under a minute. An agency client report keeps those same core scorecards but adds a channel or campaign breakdown table, a period-over-period comparison control, a branded header, and often a second page for channel-level detail that a marketing manager will actually dig into.

Both layouts rely on the same three formulas, defined in plain terms rather than sourced from any one vendor: CPA (cost per acquisition) equals Cost divided by Conversions, ROAS (return on ad spend) equals Revenue divided by Ad spend, and CTR (click-through rate) equals Clicks divided by Impressions. Readers who want the fuller ROI picture beyond these three formulas -- how to weigh CPA and ROAS against margin, lifetime value, and channel mix -- can continue with marketing ROI reporting rather than having every formula re-derived here.

How do you build a marketing dashboard in Looker Studio, step by step?

Building a marketing dashboard in Looker Studio starts with creating a new report, adding Google Ads and GA4 as data sources, then placing scorecards, a time-series chart, and a breakdown table on page one with a date range control -- the whole first version takes under 30 minutes and needs no code. Each step works independently, so you can follow this walkthrough whether or not you've read the rest of the article first.

1. 1

   Create a blank report

   Click Create > Report in Looker Studio and start from a blank report rather than a template.

2. 2

   Add the Google Ads connector

   Add the Google Ads connector as your first data source and authorize the Google account with access to the ad account.

3. 3

   Add the GA4 connector

   Add a second data source for the GA4 property and authorize it under the same or a linked Google account.

4. 4

   Place page-one scorecards

   Add scorecards for the KPIs chosen in the layout step -- typically spend, conversions, CPA, and ROAS.

5. 5

   Add a trend chart and breakdown table

   Place a time-series chart plus a table broken down by campaign or channel on the same page.

6. 6

   Add date range and filter controls

   Add a date range control and a filter control once -- every chart on the page inherits them automatically.

7. 7

   Blend Google Ads and GA4

   Use Add data > Blend data to join the two sources on a shared key, such as campaign name or date.

8. 8

   Apply a theme and set sharing

   Apply a theme for consistent colors and fonts, then configure sharing or scheduled delivery.

The date range control and filter control are native Looker Studio components: applied once on page one, both are inherited by every chart on that page without being configured chart by chart. Once these eight steps are done, the dashboard already shows blended Google Ads and GA4 numbers with working filters. Blending mechanics and formulas are covered in more depth below. Anyone building the Google Ads side of this from scratch can also follow the dedicated walkthrough for connecting Google Ads to Looker Studio.

How do you blend Google Ads and GA4 data and add calculated fields like ROAS or CPA?

Blending Google Ads and GA4 data in Looker Studio means joining the two data sources on a shared key -- usually campaign name, date, or a UTM-based source/medium field -- with the built-in Blend data feature. Calculated fields then turn the blended rows into KPIs like ROAS, CPA, and conversion rate without leaving the report editor.

1. ROAS = Revenue / Ad spend. Combines GA4 revenue with Google Ads cost to show return per dollar spent.
2. CPA = Cost / Conversions. Shows the average cost behind each conversion, whichever source records the conversion.
3. CTR = Clicks / Impressions. A Google Ads-only ratio that doesn't require blending.
4. CPC = Cost / Clicks. The average price paid per click.
5. Conversion rate = Conversions / Clicks. Ties ad engagement to the outcomes that follow it.

Adding one of these in Looker Studio means opening the field editor, naming the field, and writing the formula using existing field names from the blended data source -- once saved, the field becomes reusable across every chart in the report rather than something rebuilt per chart. Blending itself depends on a consistent join key: UTM parameters (source, medium, campaign) on outbound Google Ads links make it possible to match Google Ads spend rows with GA4 session and conversion rows on the same campaign identifier. Readers unfamiliar with how those tags are structured can start with UTM parameters before building the join.

Before building a ROAS field specifically, confirm that Google Ads cost and GA4 revenue are recorded in the same currency -- USD throughout this guide -- since blended calculated fields in Looker Studio don't auto-convert currencies for you. Native blending handles Google-to-Google joins like this one well; blending many non-Google channels alongside Google Ads and GA4 becomes practical with a paid pipeline, which is discussed in the connector-comparison section.

What common mistakes ruin a Looker Studio marketing dashboard?

The most common mistakes are mismatching the date range or currency between Google Ads and GA4, blending data sources on a join key that doesn't actually match, and cramming every available metric onto page one instead of the handful an SMB owner or agency client actually needs. Each one is a setup error, not a Looker Studio limitation.

• Mismatched date range defaults between charts. Fix by setting one report-level default date range that every chart on the page inherits.
• Blending on a join key that doesn't match. Fix by normalizing campaign names on both sides, or joining on a shared UTM field instead of a free-text name.
• Overloading page one with every available metric. Fix by keeping page one to the KPIs chosen in the layout step and pushing campaign- or keyword-level detail to page two.
• Mixing currencies between Google Ads and GA4. Fix by confirming both sources use the same currency before building any ROAS or revenue-based field.
• Sharing view access without checking underlying data access. A viewer needs their own Google account access to the Google Ads account and GA4 property, or the shared report shows an error or a blank view regardless of the Looker Studio share link settings.

Fixing these before publishing a dashboard saves the back-and-forth of stakeholders questioning numbers that were correct all along. A dashboard built on consistent dates, matching join keys, and a single currency is also the one worth feeding into marketing attribution models, where small mismatches upstream compound into wrong credit assigned downstream.

How do you automate and share a marketing dashboard in Looker Studio?

Automating a Looker Studio marketing dashboard means setting a data refresh schedule so charts update on their own, then using Looker Studio's built-in scheduled email delivery or a shareable link so stakeholders see current numbers without asking for an export. Once the dashboard spans more than Google Ads and GA4, a consolidation platform replaces maintaining each connector by hand.

Looker Studio's own refresh schedule, set per data source, keeps Google Ads and GA4 numbers current without anyone manually reconnecting either one. On top of that, built-in scheduled email delivery sends the report as a link or a file on a recurring schedule, and view-only sharing links or embedding cover the rest of single-team distribution. For a dashboard built on Google Ads and GA4 alone, this native combination is the entire automation story -- no third-party scheduling tool required.

Teams managing many accounts, or blending in non-Google channels like Meta Ads, TikTok Ads, or CRM data, outgrow that single-connector setup. Paid pipelines such as Supermetrics and Windsor.ai provide a consolidation layer that automates data collection from multiple sources instead of maintaining each connector by hand. Agencies sending these dashboards to clients on a schedule can go further with automating client marketing reports, which covers branded templates, scheduled delivery, and per-client pricing.

For teams whose real need is broader marketing automation and analytics, not only a Looker Studio dashboard, AdMetric is an AI marketing automation and analytics platform built for small and mid-size businesses. It runs a 7-day free trial with no credit card required.

When do you need a paid connector instead of Looker Studio's native ones?

A paid pipeline like Supermetrics or Windsor.ai is worth adding once a dashboard needs to blend Google Ads and GA4 with non-Google channels in one destination, or needs an explicit published row cap for planning usage -- something Looker Studio's native connectors don't publish at all. Supermetrics starts at $55 per month and Windsor.ai runs a $0 per month Free plan, both as of September 6, 2026.

Neither the Google Ads connector nor the GA4 connector publishes a row or data-volume limit on Google's official pages, as of August 12, 2026 -- that's a gap in what Google discloses, not proof that no ceiling exists, so it's written here as "not published" rather than "unlimited." GA4's standard tier does publish related caps that affect dashboard queries: a 1-million-event daily BigQuery export limit and sampling in Explorations above 10 million events per query, same date. Direct Google Ads API access outside Looker Studio's UI -- for a custom connector, say -- is separately capped at 2,880 operations per day on Explorer access and 15,000 operations per day on Basic access, also as of August 12, 2026; that's a Google Ads API quota, not a Looker Studio limit, and most dashboards built through the native connector never touch it.

Both Supermetrics and Windsor.ai list Looker Studio explicitly among their supported destinations, so switching to either one doesn't mean leaving Looker Studio as the reporting layer -- it means feeding Looker Studio from a different pipeline instead of the native connectors. The practical way to use this comparison is to count two numbers first: how many non-Google channels need to land in the same dashboard, and how many separate Google Ads accounts or GA4 properties need to be blended together. Match those counts against the plan tiers in the comparison, rather than against marketing copy, before deciding between Supermetrics alternatives and Windsor.ai alternatives as a next step.

Frequently asked questions about building a marketing dashboard in Looker Studio

The following seven questions cover what people ask most when building a marketing dashboard in Looker Studio: cost, blending Google Ads with GA4, page-one KPIs, multi-account setups, scheduled delivery, row limits, and the native-versus-paid-pipeline choice. Each is answered using sourced facts from earlier sections, including AdMetric's pricing for teams comparing a broader platform to a single dashboard.