Looker Studio (Now Data Studio) Reporting: Dashboards Built on BigQuery, With Governance

Most marketing dashboards fail quietly. Numbers don't match the ad platform, charts time out on Monday morning, and nobody knows who can see what. John Williams builds Data Studio reports that load fast, define every metric once, and show the same number the finance team would.

By John Williams · Updated 2026-10-11 · 8 min read

12 h fixed refresh for Google Ads and Search Console connectors

5 tables maximum in a single blend

14,000 GA4 API tokens per project per property per hour (standard)

TL;DR

Google renamed Looker Studio back to Data Studio in April 2026. Existing reports, data sources, and users moved over automatically, and Looker Studio Pro is now Data Studio Pro (Google Cloud blog).
For anything beyond a single-source report, we land the data in BigQuery first and build reporting tables there. Data Studio then reads clean, pre-joined tables instead of blending live API calls.
We set data freshness deliberately. Google's own marketing connectors refresh every 12 hours and that can't be changed, while BigQuery sources can refresh in minutes.
Direct GA4 connections share a fixed API quota, and quota increases aren't available for standard properties, so busy dashboards move to the BigQuery export.
Access is designed, not inherited: who owns each data source, whose credentials it runs on, and who can see client-level rows.

Who this is for

Marketing teams whose weekly report is a spreadsheet someone rebuilds by hand.
Agencies and in-house teams with Data Studio reports that time out, show quota errors, or disagree with the ad platforms.
Businesses that want ad spend, GA4, and CRM revenue on one page with one definition of a conversion.
Organizations that need to control which people and clients can see which rows.

What's included

Metric dictionary. One written definition per metric (what counts as a lead, which revenue, which attribution), agreed before any chart exists.
Data model. BigQuery tables for ad spend, GA4 events, and CRM outcomes, joined at the right grain, refreshed on a schedule.
Dashboards. An executive summary page, channel pages, and a diagnostic page for analysts, each with a stated audience and question.
Freshness and cost settings. Data freshness per source, BI Engine where it pays for itself, and BigQuery cost controls.
Access model. Data source ownership, credential type, sharing settings, and row-level access where clients or regions must stay separate.
Handover. A short guide to adding a chart or a source without breaking definitions, plus a review session with the people who'll use it.

How John builds a Data Studio reporting stack

Start with the decisions

We ask each audience what they decide weekly and which number would change their mind. A CFO and a paid search manager need different pages. Anything that doesn't support a decision is left out.

Write the metric dictionary

Google Ads conversions, GA4 key events, and CRM leads are three different things. We name each one, write how it's calculated, and decide which is the source of truth for each question.

Land the data in BigQuery

Google Ads data comes in through the BigQuery Data Transfer Service (Google Cloud), GA4 through its native export (Analytics Help), and CRM and other ad platforms through a connector or a scheduled job. Everything lands in one project, in partitioned tables.

Model reporting tables

We build daily, pre-aggregated tables (spend, clicks, conversions, revenue by date, channel, and campaign) so Data Studio reads small tables instead of raw events. Joins happen here, in SQL we can test, not in a blend.

Build the report

Pages follow the dictionary. Filters are limited to what people actually use, date comparisons are consistent, and every scorecard says where its number comes from.

Tune freshness and speed

BigQuery sources can refresh every 1 to 50 minutes or every 1 to 12 hours, and Sheets as often as every 15 minutes (Manage data freshness). We pick the slowest setting the audience can live with. For heavy reports, BI Engine caches data in memory to speed up queries (BI Engine).

Lock down access

Every data source runs on owner's, viewer's, or service account credentials. Owner's credentials let anyone you share the report with see the data without their own access, so Google warns you to share them only with people you trust (Data credentials). We choose per source and document why.

Common reporting mistakes John fixes

Blends that multiply rows. A left outer join on a key that isn't unique repeats rows, so totals in the blend come out higher than in either source (Blending tips).
Cross joins on big tables. Every row matched to every row, which triggers "too much data requested" errors.
GA4 quota errors at 9 a.m. Ten charts, a dozen viewers, and a direct GA4 connection drain the hourly quota, and every chart on the property fails until it resets.
Mismatched conversions. GA4 key events next to Google Ads conversions under the same label, with different attribution and counting.
Reports owned by an ex-employee. When the owner leaves, the data sources go with them.
Raw-event queries on every load. Dashboards that scan unpartitioned GA4 export tables and run up BigQuery costs.

Limits and settings that shape the design

These are the constraints we design around, from Google's documentation as checked on 2026-10-11.

Constraint	What the docs say	What we do about it
Data freshness	Google Ads, Search Console, and other Google marketing connectors refresh every 12 hours and can't be changed. Google Analytics can be set to 1, 4, or 12 hours (Data Studio docs).	Say on the report how fresh each section is. If someone needs fresher ad data, it comes through BigQuery.
Blends	Up to five tables per blend, with inner, left outer, right outer, full outer, and cross joins (How blends work). Joins run left to right.	Blend only small, pre-aggregated tables with unique keys. Anything bigger is joined in BigQuery.
GA4 Data API quota	A standard property gets 200,000 core tokens a day, 40,000 an hour, 14,000 per project per property per hour, and 10 concurrent requests. Analytics 360 gets ten times more (Data API quotas). Google says quota increases aren't available and points to 360 or the BigQuery export (Google Analytics blog).	Direct GA4 connections only for light, single-team reports. Shared dashboards read from the export.
BigQuery cost	On-demand queries are billed by bytes processed. Google recommends partitioning, selecting only needed columns, and setting maximum bytes billed (Estimate and control costs).	Partitioned reporting tables, date filters on every page, and a budget alert on the project.
Concurrency	For BigQuery sources, performance depends on slot availability, query complexity, data size, and caching (Improve performance).	Pre-aggregate, cache through freshness settings, and test with real viewer counts before launch.

Governance checklist

Data sources owned by a shared company account or, on Data Studio Pro, managed at the organization level.
Owner's credentials only where every viewer may see every row. Otherwise viewer's or service account credentials.
Client or regional separation enforced in BigQuery with authorized views or row-level security, not by hiding a filter.
Metric definitions linked from the report itself, and a named owner who approves changes.

Pricing and engagement

Reporting builds are quoted as a flat fee after we've seen your sources and agreed on the audiences. The scope depends on how many platforms feed the warehouse and how many report pages you need, so we don't publish a single price. BigQuery, connector, and Data Studio Pro costs are billed by those vendors, and we estimate them up front. Like all our work (see pricing), it isn't priced as a share of your media budget and doesn't lock you into a contract.

Platforms we work in

The reporting stack runs from source platforms to a warehouse to Data Studio. These are the official products we use.

Data Studio (formerly Looker Studio)

BigQuery

Google Analytics

Google Ads

Google Search Console

Google Sheets Supermetrics dbt

Logos via the Simple Icons project. Trademarks belong to their owners; no endorsement implied.

Proof you can check before you call

John's published work on measurement and reporting, and free tools that pull the same data.

Tutorial

AI-powered measurement: from dashboards to intelligence

Tutorial

Cross-channel strategy, attribution, and unified reporting

Guide

Build a Streamlit dashboard for campaign data

Guide

Connect GA4 to AI for automated insights

Q&A

What should you report on for Google Ads?

Free tool

250-point Audit Engine with Search Console, GA4, and GTM connections

Frequently asked questions

Is Looker Studio the same as Data Studio?

Yes. Google renamed Looker Studio back to Data Studio in April 2026, and existing reports moved over without any action needed. Looker, Google's enterprise BI platform, is a separate product.

Do we need BigQuery?

Not for a simple one-source report. Once you're combining ad platforms, GA4, and CRM data, or several people use the dashboard daily, BigQuery is cheaper and more reliable than blending live connectors.

Why don't our dashboard numbers match Google Ads?

Usually a mix of freshness (the Google Ads connector refreshes every 12 hours), attribution or conversion definition differences, and blends that repeat rows. The metric dictionary settles which number is right for which question.

What does BigQuery cost for marketing reporting?

For most mid-size accounts, storage and queries on pre-aggregated reporting tables are modest, but costs depend on data volume and how often reports query raw tables. We estimate it from your data before building and set a budget alert.

Do we need Data Studio Pro?

Not always. Pro adds organization-level management and Google Cloud integration, which matters when many people and clients share reports. Smaller teams often do fine on the free edition with shared ownership.

Can you fix our existing reports instead of rebuilding?

Often, yes. We start by checking data sources, credentials, and blends. If the definitions are sound, we repair; if not, we rebuild the data layer and keep the page layouts people already know.

Talk to John about Data Studio reporting

Tell John which platforms you report on, who reads the reports, and what's going wrong today. You'll get a written scope.

John, Kristy, or Sandeep will reply. One of the three of us will respond personally within 1 business day. No SDR queue.

Top 25 references

The primary sources, standards, research, and tools we rely on for this work. Every link was checked on 2026-10-11. We aren't affiliated with these publishers unless noted.

Official documentation

Looker Studio is Data Studio — Google Cloud Blog
Google's April 2026 announcement of the rename and the Pro edition.
Data Studio release notes — Google Cloud
Dated product changes, including the April 16, 2026 rebrand.
Manage data freshness — Google Cloud
Refresh options by connector, including the fixed 12-hour Google connectors.
How blends work in Data Studio — Google Cloud
The five-table limit and each supported join operator.
Blending tips and advanced concepts — Google Cloud
Join order, row multiplication, and cross-join errors.
Improve Data Studio performance — Google Cloud
Caching, BigQuery concurrency, and the Storage Read API.
Data credentials — Google Cloud
Owner's, viewer's, and service account credentials compared.
Introduction to BI Engine — Google Cloud
In-memory acceleration for dashboards that query BigQuery.
Estimate and control costs — Google Cloud
Partitioning, column pruning, and maximum bytes billed.
Data Studio Community Connectors — Google for Developers
How custom connectors are built when no official one exists.
Data API limits and quotas — Google for Developers
GA4 token, concurrency, and error quotas for standard and 360.
Managing quota for the Google Analytics Data API — Google for Developers
Why quota can't be raised, and the alternatives Google suggests.
BigQuery Export — Google Analytics Help
GA4's raw event export: limits, streaming cost, and schema.

Research & studies

Dashboards: making charts and graphs easier to understand — Nielsen Norman Group
How preattentive attributes make dashboards readable at a glance.
Choosing chart types: consider context — Nielsen Norman Group
Matching chart type to the comparison the reader needs.
Perceptual Edge library — Stephen Few
Articles on dashboard design from the author of the standard text.

Leading tools

Data Studio — Google
The product itself, free to start, with Pro for organizations.
What is dbt? — dbt Labs
Version-controlled SQL modeling for warehouse reporting tables.
Supermetrics — Supermetrics
A widely used connector for non-Google ad platforms.

Expert guides

The Visual Display of Quantitative Information — Edward Tufte
The classic case for removing chart clutter.
storytelling with data books — Cole Nussbaumer Knaflic
Practical guidance on building charts for business audiences.
Introduction to GA4 export data in BigQuery — GA4BigQuery
A well-known primer on the GA4 export schema and SQL.
Looker Studio tutorial for Google Analytics 4 — Analytics Mania
Step-by-step GA4 reporting walkthrough from a recognized GTM educator.
Looker Studio basics — MeasureSchool
An introductory course-style guide to connectors and charts.

Communities & courses

Data Studio is back with a new and expanded mission — Google Developer forums
The product team's rename notice in Google's official community.