What is Looker Studio? A guide to the tool now called Data Studio

Looker Studio is Google's free reporting and dashboard tool. It connects to sources such as GA4, Google Ads, Search Console, BigQuery and Google Sheets, and turns the data into charts, tables and filterable dashboards in a drag-and-drop editor. This guide covers what it does, how the free and Pro editions differ as of October 2026, how to use it for marketing dashboards, and where it runs out of road.

First, a note on the name: in April 2026 Google changed the Looker Studio name back to its original one, Data Studio. The product now lives at datastudio.google.com; lookerstudio.google.com redirects there, and Google says existing reports need no changes. Since most people still search for "Looker Studio", we use both names here.

What is Looker Studio used for?

Marketing teams usually have to look at five screens to see their numbers: GA4 for traffic and conversions, Google Ads for spend, Search Console for organic visibility, the CRM for leads and revenue. Looker Studio puts those sources side by side in one report. In Google's own words, it turns data into shareable, fully customizable dashboards and reports.

In practice it is used for three things:

• Recurring reporting: a dashboard that refreshes itself, instead of a spreadsheet rebuilt by hand every month.
• Executive summaries: one page that follows a handful of metrics from spend to leads to revenue.
• Per-client or per-team reports: one template reused across accounts. Google's data control lets viewers pick their own account and see the same report with their own data.

Which data can it connect to?

Reports reach data through connectors. As of October 2026 Google's connector catalogue lists Google connectors in these groups:

On top of these there are community connectors built by third parties; Google Cloud's product page mentions more than 1,300 of them. Sources such as Meta Ads, LinkedIn Ads or HubSpot usually arrive this way, or through a data warehouse that collects them first. Most community connectors are paid and route your data through another company's servers, so check the contract and data processing terms before you buy.

To show several sources in one chart you use blended data, for example joining Google Ads spend and GA4 leads on date and campaign name. Blending works for small reports; as sources and volumes grow, doing the join in BigQuery instead of in the report becomes faster and easier to audit.

Looker Studio vs Looker Studio Pro

As of October 2026, Google Cloud's product page shows the two options like this:

The same page notes that Pro's per-user monthly price varies with the length of the subscription. According to the subscription docs, a self-service Pro subscription is sold as user licenses and billed monthly for the number of licenses in the subscription, whether or not they are used. Each subscription is tied to exactly one Google Cloud project and paid through the Cloud Billing account linked to it. Google offers a 30-day free trial of Pro for an organization; billing starts automatically when it ends.

A license is only needed by users who create, edit or manage content in Pro workspaces. Managers and clients who only view reports do not need one.

The main Pro features in Google's docs:

• Company-owned content: in the free edition, reports and data sources belong to whoever created them. Pro content belongs to a Google Cloud project, so a report keeps working when its author leaves.
• Team workspaces: shared spaces with Manager, Content Manager and Contributor roles.
• Richer scheduled delivery: up to 200 delivery schedules per report, delivery to Google Chat, and alerts when a chart meets conditions you set.
• Personal report links: each person explores their own copy of a report.
• Security and compliance: CMEK, customer-managed storage for uploads and extracts, and data residency.
• Gemini in Data Studio: asking questions of your data, building calculated fields from natural-language prompts, and adding report content to Slides.
• Google Cloud support: technical support for Pro issues, which per Google also requires a separate Google Cloud support plan.

In short, Pro earns its price once "who owns this report" and "who can see what" become real questions. For a small team where one specialist runs a few dashboards, the free edition is usually enough.

How to build a marketing dashboard

A good marketing dashboard starts with questions, not with the tool. The order we use:

1. Write down the questions. Five to ten that change decisions, such as "which channel brought how many qualified leads this month, at what cost?"
2. Fix the metric definitions. Which GA4 key event is a "lead", and which CRM stage? Without written definitions, the same dashboard shows two numbers in two meetings.
3. Connect the sources. GA4 for traffic and key events, Google Ads for spend, clicks and conversions, Search Console for organic queries and pages. For multi-source or CRM dashboards, join the data in BigQuery first.
4. Layer the pages. Page one is the executive summary; the next pages go into channels, campaigns and landing pages.
5. Set up sharing and delivery. Decide who views, who edits, and who gets the weekly PDF.

The sturdiest way to show GA4 and CRM data together is to export GA4's raw data to BigQuery. Our GA4 BigQuery export guide walks through it step by step. If your tags need a clean-up first, start with what Google Tag Manager is.

Sharing and permissions

Sharing has two layers: the report and the data source.

Sharing the report. Google's sharing docs say you can invite specific people or Google Groups to view or edit, turn on link sharing for everyone in your organization or on the web, schedule PDF delivery by email, or embed the report in a web page. Sharing a report shares all of its pages, and editing always needs a Google account.

Data source credentials. This is the setting that matters most. There are three options:

• Owner's credentials: the report runs on the data source owner's access, so viewers do not need their own GA4 or BigQuery access. Handy for showing reports to clients or leadership, but everyone who sees the report sees the data it shows.
• Viewer's credentials: every viewer needs their own access to the dataset.
• Service account credentials: access tied to a service account rather than a person, often used with BigQuery so a report does not depend on one employee.

Google itself advises making sure you trust the people you share an owner's-credentials report with. Keep personal data (emails, phone numbers, names) out of reports altogether; a marketing dashboard does not need it.

Limits to plan for

GA4 API quotas. Reports that use the GA4 connector are subject to Google Analytics Data API quotas. Per Google's quota page, a standard GA4 property gets 200,000 core tokens per day, 40,000 per hour, 14,000 per project per property per hour, and at most 10 concurrent requests. Analytics 360 limits are ten times higher. Reports with many pages, dozens of charts per page and many simultaneous viewers can hit these limits and show errors.

Functional limits of the GA4 connector. Google's connector docs say GA4 segments and comparisons are not available through it, and tables filtered by a calculated field cannot show a totals row. The docs also warn that certain date dimensions combined with complex filters can inflate session counts in stacked bar charts, and recommend rebuilding the query as a view in BigQuery.

Reports and explorations can disagree. Google notes that the connector matches GA4 reports but not explorations.

Ownership risk. In the free edition a report belongs to a person. If the agency employee or specialist who built it leaves, ownership has to be transferred; building it under a company account from the start, or moving to Pro, removes that risk.

Performance. Every chart queries its source live. Long date ranges, many calculated fields and blended data are the usual reasons for slow reports.

When to move to BigQuery

If two of these apply, it is time to point reports at BigQuery rather than straight at GA4: quota errors are frequent; CRM, Meta or LinkedIn data must sit in the same dashboard; you need more history than GA4 keeps (on standard properties, at most 14 months for explorations); or the same metric shows different numbers in different reports. We build this as our marketing data warehouse service. If you are weighing GA4 against a product analytics tool, see our GA4 vs Mixpanel comparison.

How Roicool works on this

In Looker Studio reporting projects we write down the questions and metric definitions first, prepare the data in BigQuery where needed, and hand over dashboards your team can edit. For the measurement stack as a whole, see our analytics consulting page.

Sources

• Google Cloud, Data Studio (product and pricing page): cloud.google.com/looker-studio (accessed October 2026)
• Google Cloud, Welcome to Data Studio ("Looker Studio is now called Data Studio"): cloud.google.com/looker/docs/studio/welcome (accessed October 2026)
• Google Cloud, About Data Studio Pro: cloud.google.com/looker/docs/studio/about-pro (accessed October 2026)
• Google Cloud, Data Studio Pro subscription overview: cloud.google.com/looker/docs/studio/pro-subscription-overview (accessed October 2026)
• Google Cloud, Available connectors: cloud.google.com/looker/docs/studio/available-connectors (accessed October 2026)
• Google Cloud, Connect to Google Analytics: cloud.google.com/looker/docs/studio/connect-to-google-analytics (accessed October 2026)
• Google Cloud, Ways to share your reports: cloud.google.com/looker/docs/studio/ways-to-share-your-reports (accessed October 2026)
• Google Cloud, Data credentials: cloud.google.com/looker/docs/studio/data-credentials (accessed October 2026)
• Google for Developers, Google Analytics Data API quotas: developers.google.com/analytics/devguides/reporting/data/v1/quotas (accessed October 2026)
• Google Analytics Help, Data retention: support.google.com/analytics/answer/7667196 (accessed October 2026)