📌 Part of the fasilytics.fr analytics series
This article is a companion to the Looker Studio Complete Guide and the LookML Metric Governance Guide. It focuses on the naming confusion and explains how the three pieces fit together.
Why This Is Confusing: A Brief History
Before 2022, there was no confusion. Google had Google Data Studio (free dashboarding tool, launched 2016). Separately, a company called Looker built an enterprise BI platform powered by a semantic modelling language they called LookML.
In 2020, Google acquired Looker for $2.6 billion. In October 2022, Google rebranded Google Data Studio as Looker Studio. The result: two completely different products now share the “Looker” name, and LookML — the modelling language — exists as a third concept underneath one of them.
The practical consequence: searching “Looker” on Google returns results for all three things interchangeably, and most articles conflate them. This one does not.
The Three Things, Clearly Defined
Looker Studio
What it is: a free, browser-based dashboarding and data visualisation tool. It connects to data sources, lets you build interactive reports with drag-and-drop, and share them via a link. No installation, no code required.
Formerly known as: Google Data Studio.
Where it lives: lookerstudio.google.com — in your browser. Nothing to install.
Who uses it: digital marketers, analytics consultants, small data teams, agencies. Anyone who needs to turn GA4, Google Ads, or Sheets data into a shareable dashboard without writing code.
What it costs: free. A paid tier called Looker Studio Pro (~$9/user/month) adds team workspaces and SLA support, but the core product is entirely free.
Looker Enterprise
What it is: a full BI platform built for data teams. It sits on top of your data warehouse (BigQuery, Snowflake, Redshift, etc.), provides a governed semantic layer, and lets analysts query data through an Explore interface without writing SQL. Business logic is defined once, versioned in Git, and consumed by every report.
Formerly known as: Looker (the product from the acquired company).
Where it lives: cloud.google.com/looker — deployed as a Google Cloud service, managed or self-hosted.
Who uses it: data engineering teams, analytics engineers, BI teams at mid-to-large organisations. Requires SQL fluency and ideally Git knowledge to use properly.
What it costs: enterprise pricing, typically starting at tens of thousands of dollars per year. Not suitable for individual practitioners or small teams.
LookML
What it is: a YAML-like modelling language that runs inside Looker Enterprise. It is how you define your data model — which tables exist, how they join, what metrics mean, how they are computed. LookML is not a product you buy. It is the language you write to configure Looker Enterprise.
Analogy: if Looker Enterprise is a car, LookML is how you write the engine specs and configure the dashboard. You cannot drive LookML without the car.
Who writes it: analytics engineers and data engineers. Not a tool for non-technical users.
What it costs: nothing separately — it is part of the Looker Enterprise license.
Side-by-Side Comparison
The Relationship Between the Three
Understanding how the three fit together is as important as understanding each one individually.
LookML runs inside Looker Enterprise. You cannot use LookML without Looker Enterprise. LookML defines the data model — which tables, which joins, which metrics, which dimensions. Looker Enterprise reads that model and exposes it as an Explore interface for analysts to query without writing SQL.
Looker Studio can consume data that Looker Enterprise governs. Via the Looker (Google Cloud) connector in Looker Studio, you can connect a Looker Studio dashboard directly to a Looker Enterprise data source. When you do this, Looker Studio uses the metrics as defined in LookML — the governed, canonical definitions — rather than recomputing them independently. This is the most sophisticated setup and eliminates the “multiple definitions of the same metric” problem entirely.
The Decision Framework: Which Do You Need?
Use Looker Studio if…
- Your primary data sources are Google products (GA4, Ads, Search Console, Sheets, BigQuery)
- You are an analyst, marketer, or consultant building client-facing reports
- Your team has no dedicated data engineering resources
- You need to be operational today, not in three months
- Your budget is zero or close to zero
The ceiling: Looker Studio works well until you have 5+ analysts independently redefining the same metrics, or until your stakeholders start getting different revenue numbers from different reports. That is when the governance problem appears.
Use Looker Enterprise + LookML if…
- You have a data warehouse (BigQuery, Snowflake, Redshift) with significant data volume
- Multiple teams are building dashboards on the same underlying data
- You have experienced the “which revenue is correct?” problem in a Monday morning meeting
- You have at least one analytics engineer who can own the LookML model
- You can justify an enterprise BI budget — typically $50,000–$200,000+/year
The floor: Looker Enterprise is not a tool you set up in a weekend. It requires data modelling expertise, a data warehouse, and ongoing LookML maintenance. For a team of five, it is almost certainly overkill.
Use both together if…
- You have Looker Enterprise as your governed semantic layer
- Some stakeholders need highly customised, embeddable reports that Looker’s native dashboards cannot deliver
- You want to give non-technical users the ability to explore governed data in a familiar, simple interface
In this setup, Looker Studio connects to Looker Enterprise via the Looker connector, consuming the metrics as defined in LookML. The business logic is defined once. Looker Studio is purely a presentation layer.
Common Misconceptions
“Looker Studio is the free version of Looker Enterprise”
No. They are not tiers of the same product. They are two completely separate products that happen to share a name after a rebrand. Looker Studio is a dashboarding tool. Looker Enterprise is a BI platform with a semantic layer. The difference is not about features — it is about architecture.
“I can write LookML in Looker Studio”
No. LookML is a language that runs exclusively inside Looker Enterprise. Looker Studio has its own formula syntax for calculated fields, which is completely different from LookML. The two do not interact.
“LookML is just SQL with a different syntax”
LookML is closer to a configuration layer above SQL than a replacement for it. A LookML measure generates SQL under the hood, but the LookML definition adds governance: a label, a description, a format, version-controlled documentation, and a type system that prevents double aggregation. SQL alone does none of that.
“I need Looker Enterprise to use BigQuery with Looker Studio”
No. Looker Studio has a native BigQuery connector. You can query BigQuery directly from Looker Studio without Looker Enterprise. Looker Enterprise is only needed if you want the semantic layer — the governed metric definitions on top of BigQuery.
Quick Reference
| Looker Studio | Looker Enterprise | LookML | |
|---|---|---|---|
| What is it? | Dashboarding tool | BI platform | Modelling language |
| Free? | Yes | No (enterprise) | Bundled with Looker |
| Can I use it alone? | Yes | Yes | No — needs Looker Enterprise |
| Requires coding? | No | Recommended | Yes |
| Metric governance? | No | Yes | Yes (this is how it works) |
| Git version control? | No | Yes | Yes |
| Right for small teams? | Yes | No | N/A |
| Right for enterprise? | Limited | Yes | Yes |
Further Reading
- Looker Studio: The Complete Guide — From Zero to Advanced — deep dive on Looker Studio: interface, connectors, calculated fields, data blending, pro tips
- LookML Metric Governance: The Complete Guide — deep dive on LookML: dimensions, measures, cross-source metrics, governance workflow
- Official Looker Studio documentation: cloud.google.com/looker/docs/studio
- Official Looker Enterprise documentation: cloud.google.com/looker/docs
- LookML reference: cloud.google.com/looker/docs/reference/lookml-quick-reference