Last Updated: November 21, 2025
Looker
Business intelligence and data analytics
Core Concepts
| Item | Description |
|---|---|
LookML
|
Modeling language for data |
View
|
Table representation |
Explore
|
Queryable data set |
Dashboard
|
Collection of visualizations |
Look
|
Saved query and visualization |
Model
|
Collection of explores |
LookML Components
| Item | Description |
|---|---|
dimension
|
Column or calculated field |
measure
|
Aggregation (sum, count, avg) |
filter
|
Restrict data |
join
|
Connect views |
derived_table
|
SQL-based table |
LookML Example
view: orders {
sql_table_name: public.orders ;;
dimension: id {
primary_key: yes
type: number
sql: ${TABLE}.id ;;
}
dimension: status {
type: string
sql: ${TABLE}.status ;;
}
measure: total_revenue {
type: sum
sql: ${TABLE}.amount ;;
value_format_name: usd
}
}Best Practices
- Use meaningful naming conventions in LookML
- Create reusable dimensions and measures
- Use persistent derived tables for performance
- Implement row-level security with access filters
💡 Pro Tips
Quick Reference
Use liquid templating for dynamic SQL in LookML