The product names
Google renamed Looker Studio to Data Studio in April 2026. That change does not make it a different edition of Looker. A job asking for LookML development is asking for a modeling skill; a job asking for a Looker Studio report may mean the report editor now called Data Studio. Read the tasks beside the tool name before choosing a course.
Models and report fields
| Work | Looker’s modeled workflow | Data Studio report workflow |
|---|---|---|
| Reusable definitions | Views, dimensions and measures in LookML | Data-source fields and calculated fields |
| Querying | Select fields and filters in an Explore | Select dimensions and metrics for a chart |
| Combining data | Model joins and derived tables | Connect sources and create report blends |
| Data access | Model permissions, user attributes and access filters where configured | Data-source credentials and source permissions |
| Useful practice | Trace a metric to its model and test joins | Check chart aggregation, dates and sharing |
Both products make charts and reports. The distinction is where you define and maintain the meaning of the data. In a LookML model, several dashboards can refer to one revenue measure. In a Data Studio report, you need to understand whether a calculation lives in the source or only in a chart. A connector to governed data can bring existing definitions into a report, but it does not remove the need to check aggregation.
A practical example
A retailer has orders and order lines. Its LookML developer defines the order key and join relationship, then exposes an order-revenue measure to analysts in an Explore. The analyst selects channel and revenue, applies a period filter and saves a dashboard tile.
A Data Studio report author connects a prepared order table and charts revenue by channel. If they blend another source, they must check that the join key does not duplicate amounts. These are related tasks, but knowing how to arrange a report does not demonstrate that you can maintain its warehouse semantic model.
Access and sharing
In Looker, folder visibility and access to the underlying model are separate concerns; row restrictions can depend on user attributes and access filters. In Data Studio, report sharing and data credentials are also separate. Owner’s credentials and viewer’s credentials can produce different data-access outcomes for the same shared report link.
Neither a hidden field nor a chart filter should be assumed to establish a security boundary. Test with the intended viewer and consult the relevant product’s access documentation.
A learning choice
Take the Looker and LookML course when your role involves Explores, metric definitions, model joins or LookML changes. Use the Looker Studio tutorial for the report-builder basics of the product now called Data Studio. Those Studio lessons are a focused part of the broader course, not a separate full Data Studio training program.
The Work Gym provides independent browser practice. It does not supply a hosted Looker instance, deploy warehouse models or publish real Google reports. For credentials, read the Looker certification status guide; the former standalone exams are retired.