Google Data Studio (formerly Looker Studio)

What Data Studio is and its relationship to Looker Studio

Data Studio is Google’s tool for creating and sharing visual reports from connected data sources. It was called Looker Studio during part of its history and returned to the Data Studio name in April 2026. Both names may appear in materials, links and searches without necessarily referring to different tools.

Its publication unit is a report containing pages, charts, tables and controls. Uses include commercial monitoring, campaigns, operations and preventive information. The report communicates an interpretation of data; it does not replace the system that records and corrects events. Google also positions Data Studio as a place to access other assets in its data environment, with availability checked for each feature.

It should be distinguished from Looker, Google Cloud’s enterprise analytics platform. Sharing a brand family for several years did not make their models, configuration or licensing equivalent.

Reference documentation: Google Cloud: Welcome to Data Studio · Google Cloud (2026): Data Studio returns.

History, availability and naming changes

Google announced the free version of Data Studio in May 2016, initially bringing reporting and visualisation to individuals and smaller teams. The product left beta and became generally available in September 2018. These milestones concern a Google product that predates Looker joining the company.

Google completed its acquisition of Looker in February 2020. In October 2022, Data Studio became Looker Studio, and the Pro offering developed additional organisational and administrative capabilities. This naming change explains why tutorials from different periods use different names for similar workflows.

In April 2026, Google restored the Data Studio and Data Studio Pro names, broadening the product’s mission as an access point for Google Data Cloud assets, including reports and other data experiences. The announcement describes product evolution rather than a requirement to rebuild existing reports. When following a guide, check its date, current option names and whether it concerns a standard, Pro or rolling-out feature.

Reference documentation: Google Analytics Blog (2016): Announcing Data Studio · Google Blog (2018): Data Studio generally available · Google Cloud (2020): Welcoming Looker · Google Help: Looker Studio documentation moved to Google Cloud · Google Cloud (2026): Data Studio returns.

From a data source to an interactive report

Google Data Studio organises information into reports combining charts, tables, text and controls. Its documentation distinguishes the connector used to access a service, the data source presenting its fields, and the report using those fields. A dimension describes or groups items, while a metric quantifies something. Confusing those roles can produce misleading aggregations.

This profile retains the reference to Looker Studio to help readers who knew that name identify the product. Consult current Data Studio documentation and confirm the available configuration before using it. The report is not necessarily where a data error should be corrected: a source change can affect several charts and needs checking before results are distributed. Keep the source owner and report owner identifiable even when they are different people.

Reference documentation: Google Cloud Documentation — Data Studio quick start guide.

Connectors, calculated fields and blended sources

A connector communicates with a source system; a data source defines how its fields appear to the report. Data sources can be reused across reports, and connectors may come from Google or third parties. The existence of a connector does not mean it is free, includes every source field or will retain the same provider conditions indefinitely.

Calculated fields transform or combine information through formulas. Scope matters: a calculation defined in a data source is reused differently from a chart-specific calculation. Aggregation matters too: adding percentages from groups rarely answers the same question as calculating a proportion over the whole population.

Blends join tables using conditions. First define what one row represents and check the keys. An activity register and an attendance register can be related, but joining them and counting rows would multiply activities with more attendees. Reconcile each source independently before checking the blend, retaining visibility of unmatched records.

Reference documentation: Google Cloud: About data sources · Google Cloud: About calculated fields · Google Cloud: Create, edit and manage blends.

Choosing charts and interpreting them

Data Studio offers visualisation families for different questions. Selection should start with the data and message rather than the available colours.

• Tables and pivot tables: present detail or summaries by dimension. They suit readers who need to check specific figures and locate records.
• Scorecards: highlight a measure, potentially with a comparison. Gauges show its position against a target or range, which needs a justified meaning.
• Lines, time series and areas: show change. Time series use a date dimension; areas emphasise magnitude or composition, so cumulative figures should not be confused with individual-period values.
• Scatter plots: relate two numeric metrics. A point cloud or trend line helps explore association but does not establish causation.
• Bars and pie charts: bars compare categories, while pies or doughnuts represent parts of a whole. Pie charts convey little when there are too many categories or the total lacks a common meaning.
• Google Maps and geographic charts: place data in a territory. Map area is not equivalent to the exposed population; colour comparisons require denominators and coverage.
• Bullet charts and treemaps: the former compare a metric with targets, while the latter use areas to represent a hierarchy. The scale and meaning of size should be explainable in both.

In OSH, a dashboard might combine a delivery indicator, a series of overdue actions and an exceptions table. Each component should retain its unit and period; placing them on one page does not make them directly comparable.

Reference documentation: Google Cloud: Types of charts · Google Cloud: Gauge chart reference · Google Cloud: Treemap reference · Google Cloud: Scatter chart reference.

Design, controls and the reader’s experience

A report can start from a template or use a custom layout. Text, colours, pages and controls should help readers understand the information. A template solves part of presentation; it does not decide which indicator is appropriate or which population belongs in it.

Date and selection controls let readers change the view. Show the active selection and explain whether a date represents planning, execution or validation. If two charts use different date concepts, state this alongside their titles. Apply the same discipline to table ordering, units and percentage formats.

One proposed usability check is asking a representative reader to locate a total, identify its period and explain an exception. This profile proposes that method; it does not claim that user testing has taken place. The report is better prepared when its interpretation does not depend on its author explaining every filter during a meeting.

Reference documentation: Google Cloud Documentation — Data Studio quick start guide · Google Cloud: Types of charts.

Standard, Pro and content management

Data Studio retains a standard offering and a paid Pro edition. Pro links the subscription to a Google Cloud project and adds team-oriented content organisation. Team workspaces manage assets and responsibilities differently from a collection of reports dependent on one personal account.

Selection should start with the report’s lifecycle: who takes responsibility when its author changes, how another editor joins and how access is revoked. Subscription, report permissions and data-access credentials are separate layers. Having Pro does not automatically make every source accessible or every report private.

Costs may also arise outside the tool: source queries, commercial connectors or services providing the data. A fit assessment should use the actual source and intended reader journey rather than only an example report with prepared data.

Reference documentation: Google Cloud: Data Studio Pro subscription overview · Google Cloud: Team workspaces · Google Cloud Documentation — Data credentials.

Refresh, caching and maintenance

Data freshness determines when Data Studio queries the source again rather than reusing temporarily stored data. Options vary by connector. Opening a report or changing pages does not guarantee a new query or establish that the source system has received every record.

For recurring preventive reporting, retain three references: the analytical period, the source’s last update and the report’s last check. A campaign may be closed in the schedule while responses still await loading. Show this as a data limitation rather than hiding it inside a percentage.

Maintenance includes credentials, field changes, types, blends and recipients. When a shared source changes, check the reports that depend on it. A small set of expected totals and exception cases helps detect deviations without manually inspecting every chart.

Reference documentation: Google Cloud: Manage data freshness · Google Cloud: About data sources.

What it can add to preventive monitoring

• Campaign summaries: show planned and delivered sessions by period and site, with enough detail to locate differences.
• Participation monitoring: present received responses against the invited population, explaining the denominator and missing responses. Participation is not equivalent to preventive effectiveness.
• Indicator communication: provide a common report for a management meeting, placing definitions and refresh dates alongside the charts.

Sabentis proposes these as examples of organising information. Data should come from authorised records and conclusions should stay within what the measures actually describe. An interactive report can prompt useful questions, but it does not turn a statistical association into a demonstrated cause.

Worked example: comparing delivery with the plan

Hypothetical example. A team wants to show which awareness activities were delivered against its quarterly plan and where information still needs confirmation.

1. Define a source containing activity identifier, site, planned date, actual date and verification status. Avoid one row per attendee when the measure counts activities, as this would multiply the total.
2. Connect the source and review field types. Check that dates are treated as dates and identifiers are not summed as quantities.
3. Prepare a detail table and site charts. Add date controls after deciding whether they filter planned or actual delivery dates.
4. Reconcile the report with a reference list. Test a site without activity, a postponed session and an activity delivered outside the quarter.
5. Choose data credentials and report permissions for the intended audience. Check an authorised reader’s view before sharing.

The result must explain why an activity appears in one period rather than another. Display the report date and source refresh date to avoid presenting old information as current. Preserve the exception list so unresolved dates are not silently excluded from reporting.

A test can include 12 planned activities: nine completed within the quarter, one afterwards and two with no actual date yet. In-quarter delivery would be 9/12, or 75%. If the chart shows 10/12, it includes the later activity and should explain that choice. These are hypothetical figures for validating the time rule, not observed outcomes.

Reference documentation: Google Cloud Documentation — Data Studio quick start guide · Google Cloud Documentation — Data credentials.

Sharing a report does not settle data access

Google distinguishes owner, viewer and service-account credentials. With owner credentials, a person may see data through a report without having direct access to the original dataset. Sharing a report and sharing its data source are therefore related but distinct decisions. Check exactly what information each recipient can access.

Connections, transformations and calculated fields require maintenance. A source-structure change can leave charts incomplete without making the reason obvious to readers. Filters and data combinations can also change the analysed population. Maintain a reconciliation table and document exclusions, unmatched records and refresh rules. A visually empty chart should be investigated rather than interpreted automatically as an absence of activity.

Reference documentation: Google Cloud Documentation — Data credentials.

When to choose Data Studio

It may fit a shareable web report based on compatible sources with an accountable maintainer. Before adoption, test the real connection, expected refresh, plan capabilities and access requirements. A mock-up using sample data does not establish that the production process will work.

Google Sheets can provide a working source for a simple register. To assess a different analysis and distribution model, compare Power BI against sources, skills and data governance, not only chart appearance.

Frequently asked questions about Data Studio in OSH

Does a report link expose every original record?

Its scope depends on permissions, credentials and configuration. Test with the actual recipient role rather than inferring access from the link’s appearance.

Why do two charts show different totals?

Review dates, filters, aggregation, dimensions and source matching. They may be answering different questions.

Should a safety dashboard be publicly available?

Only where its content is authorised for public disclosure and its detail does not expose restricted information. Link-based sharing requires an explicit decision.

Reference documentation: Google Cloud Documentation — Data Studio quick start guide · Google Cloud Documentation — Data credentials.