CLOUDAD / PERSPECTIVES

From Data Studio to Looker Studio and back to Data Studio: the name changed, data is still the lead

From Data Studio to Looker Studio and back | COO Perspectives cover

OVERVIEW

Data Studio became Looker Studio in 2022 and returned to its original name in April 2026. Following Google's explanations of both renames, this piece covers what to check for existing reports, URLs and Pro features, and what the name changes made me think about data quality and judgement.

KEY POINTS

Key points

  • When Google launched the free Data Studio in 2016, it wanted more people in an organisation to be able to access, understand and share data.
  • The 2022 rename to Looker Studio was Google Cloud bringing its business intelligence products under the Looker brand.
  • The April 2026 return to Data Studio redraws the line between it and Looker, and brings more data assets into one entry point.
  • Existing reports do not need rebuilding because of the rename, and old URLs redirect automatically; companies that restrict external sites should still confirm the new domain is allowed.

One tool, two renames

From Data Studio to Looker Studio and back to Data Studio, each stage came with a different product arrangement.

When Google changed the name back to Data Studio in April 2026, I dug out the earlier official announcements and read them again.

For people who use reports every day, a rename may mean little more than updating training material, bookmarks and habits. Seen over a longer stretch, though, the history is a good prompt to ask: when we build reports, is our attention on the data, the visuals, or the people looking at them?

When Name Official positioning and change
May 2016 Data Studio Earlier that year the enterprise Data Studio 360 launched with the Google Analytics 360 Suite; the free version followed in May, lowering the barrier to accessing and sharing data.
October 2022 Looker Studio Google Cloud’s business intelligence (BI) products were unified under the Looker brand. The free version continued, and Looker Studio Pro was introduced.
April 2026 Data Studio Complementary to Looker, with each developing on its own. Data Studio leans towards personal data exploration and quick visualisation; Looker focuses on enterprise BI with a central semantic model.

These are the product directions set out in the official announcements. What I read into the names is a separate, personal layer.

2016: letting more people see the data

Data Studio’s original aim was to make data easier to access, understand and share.

The 2016 announcement focused on connecting marketing data, building easy-to-read reports, and editing them together in real time, like Google Docs. At the time, the free version allowed five reports per account and was available only to users in the United States.

I like the name Data Studio because it puts the data first. The tool brings scattered information into view so more people can join the discussion.

But getting from “everything in view” to “nothing in doubt” still takes a lot of work. Where the data comes from, how a metric is calculated, and what decision a chart can support all need to be spelled out. Only when the picture is clear can we go on to check whether the conclusion holds up too.

2022: Looker, and the people looking

Google’s reason for the rename was a unified product brand; my own association was the people in front of the report, looking at the numbers.

Google completed its acquisition of Looker in 2020. In October 2022, Kate Wright explained in a Google Cloud announcement that the BI product family would be unified under the Looker brand, and Data Studio became Looker Studio.

That was Google’s product decision. Still, the word Looker made me think naturally of the people looking: the audience.

Looking back on those years, many teams, ours included, put a lot of effort into who each report was for: managers needed summaries, clients cared about results, and each department had its own analysis needs. All of these differences deserve attention.

But as reports multiplied, one thing needed checking again and again: do these different-looking views rest on the same definitions? When every team says “new customer”, are they counting the same people? However clear the charts, if each report understands the same metric differently, the meeting ends up back at the start.

2026: back to Data, with more data assets inside

This rename comes with a new product positioning, and Data Studio’s entry point now reaches beyond reports.

The 10 April 2026 announcement says Data Studio will complement the Looker platform, with each developing on its own. Besides reports and data sources, the new home page offers BigQuery conversational agents and an entry point to data apps built in Colab notebooks.

Clay illustration: a robot and colleagues looking at a report together

Each of these has its own conditions for creating, sharing and using it; an entry point on the home page does not mean every account automatically gets the same features.

For me, the change is a reminder: as more data work is assisted by AI, the explanations people used to fill in from experience need to be written more clearly into data definitions and usage.

“This field changed its calculation last month.” “That number can’t be compared directly with last quarter.” People who know the business may know this; AI may not have the same background. When data is wrong or lacks the necessary context, AI can still produce confident, complete-looking answers.

Starting from Data, going full circle and coming back to Data, what I care about more is whether the data can be understood by whoever takes it over, and whether it can support new ways of analysing it.

What should teams already using it do?

Ordinary reports do not need rebuilding; what is worth checking together is URL access, document naming, asset handover and feature needs.

  1. Existing reports and data sources do not need moving. Google says existing reports, data sources, assets and users move to the new experience. According to current documentation, the old lookerstudio.google.com redirects automatically to datastudio.google.com. If the company restricts external sites through a proxy or allowlist, IT still needs to allow the new domain.
  2. Use one name in internal documents and training. SOPs, onboarding material and client guides can switch to Data Studio, adding “formerly Looker Studio” on first mention so people working from older material can still find their way.
  3. Tell Data Studio and Looker apart when buying and planning. The former suits quick reporting and data exploration, with Pro team management features; the latter manages metric definitions in a central semantic model for enterprise BI. The choice should come back to data governance and how the data is used.
  4. When considering Pro, check the activation conditions too. Whether assets can be managed by the organisation over time, and whether there are requirements on encryption and where data is stored, are both factors. In June 2026 Pro added customer-managed encryption keys, customer-managed storage and data residency; customer-managed encryption keys and data residency must be set when a new Pro subscription is created and cannot be added to an existing one.

Colleagues new to the tool can start with What is Data Studio? Five business benefits (in Chinese); for features, see Six practical new Data Studio features (in Chinese).

Frequently asked questions

The rename, report migration and paid features are three things to understand separately.

Do old Looker Studio report links still work?

Yes. Google says the old domain redirects automatically, so there is no need to rebuild reports. If the company restricts access to external sites, ask IT to confirm the new domain is on the allowlist.

Will it start charging after the rename?

The free version still offers personal analysis and visualisation. Teams that need more governance and enterprise features can consider Data Studio Pro; connected cloud services or third-party connectors may still carry their own costs.

Are Data Studio and Looker the same product?

No. In Google’s positioning they complement each other and develop separately. Data Studio focuses on data exploration and report visualisation; Looker focuses on enterprise data analysis and governance through a central semantic model.

After years of building reports with clients, what I care about more and more is whether, once a report is handed over, the next person knows what it can answer and where judgement still needs to be held back.

Names can change and visuals can be refreshed, but data definitions and usage cannot live only in a few people’s heads. When these things are spelled out, reports have a better chance of staying in use and discussions can keep moving forward.

For ready-made templates, see Data Studio templates and tutorials (in Chinese); to check data definitions and quality first, get in touch.

Further reading

References

  1. Google Analytics Blog, Announcing Data Studio: our free, new, Data Visualization Product, 25 May 2016.
  2. Google Cloud Blog, Introducing the next evolution of Looker, your unified business intelligence platform, 11 October 2022.
  3. Google Cloud Blog, Data Studio returns as new home for Data Cloud assets, 10 April 2026.
  4. Google Cloud, Data Studio release notes.
  5. Google Cloud, Welcome to Data Studio.
  6. Google Cloud, Customer-managed encryption keys (CMEK).
  7. Google Cloud, Set up data residency.
  8. Google Cloud Blog, Google completes Looker acquisition, 13 February 2020.

KEEP READING

Keep building your understanding

Leave a Reply

Your email address will not be published. Required fields are marked *