Understanding and unifying Looker and Looker Studio

Key Concepts

• Looker Studio: A web tool for building visual data stories and reports.
• Looker: A business intelligence tool focused on data governance and consistent business definitions through a semantic layer.
• Studio in Looker: Integration of Looker Studio within the Looker interface, allowing connection to Looker Explores.
• Data Governance: Ensuring data is secure, private, accurate, available, and usable.
• LookML: Looker's modeling language used to define the semantic layer.
• Connectors: Bridges between Looker Studio and data sources.
• Dimensions: Categorical data fields used for analysis.
• Metrics: Data aggregations like count, sum, and average.
• Semantic Layer: A unified data model that provides consistent definitions across an organization.
• Explores: The interface in Looker used to save and run queries.

Looker Studio: Visual Data Storytelling

• Purpose: Enables users to build visual data stories and reports easily.
• Data Connections: Connects to various data sources, including Google Cloud products (BigQuery, Google Sheets), services (Google Ads, YouTube Analytics), and CSV files.
• Connectors: Uses connectors to bridge Looker Studio with data sources; includes Google-built and community connectors (over 1,000 available).
• Data Modeling: Allows data modeling within Looker Studio without altering the original data.
  • Defining data types for fields.
  • Creating new fields for binning, grouping, or calculated fields.
• Calculated Fields: Uses functions like CONCAT, DATE_DIFF, or CASE statements to create new metrics or dimensions.
  • Example: CONCAT(FIRST_NAME, " ", LAST_NAME) to combine first and last names.
• Interface: Features a drag-and-drop interface for building visualizations and charts.

Looker: Data Governance and Semantic Modeling

• Challenge Addressed: Solves the challenge of data governance, ensuring data is secure, private, accurate, available, and usable.
• Semantic Layer: Employs a semantic layer to unify data definitions across the organization.
• LookML: Uses LookML to model data before it's used in dashboards.
  • Model Files: Define the overall data model.
  • View Files: Represent database tables.
• Components:
  • Dimensions: Attributes like customer name or order date.
  • Measures: Aggregations and calculations.
  • Parameters: User-defined inputs.
  • Drill Downs: Functionality to explore data at a more granular level.
• Looks, Explores, and Dashboards:
  • Look: A saved visualization that explains a specific piece of data.
  • Dashboard: A collection of visualizations that tells a story.
  • Explore: The interface used to save and run queries.
• Interaction with Database: Interacts with the underlying database to execute queries based on the LookML model.
• Programmability: Can be interacted with programmatically via its RESTful API or by embedding visualizations, automating tasks, or building custom applications.
• Example: Customer Acquisition Cost (CAC):
  • Sales Team Definition: Includes sales team time, travel, entertainment, lead generation costs, commissions, and bonuses.
  • Marketing Team Definition: Focuses on event costs, advertising campaign costs, or influencer marketing.
  • Issue: Conflicting reports due to lack of a centralized definition.

Studio in Looker: Bridging the Gap

• Integration: Integrates Looker Studio directly within the Looker interface.
• Data Source Connection: Connects to modeled and ad hoc data sources in Looker.
• Looker Connector: Connects to Looker Explores via a Looker connector.
• Benefits:
  • Build reports using the same measures and dimensions defined in the LookML model.
  • Ensures everyone is on the same page with consistent data definitions.
  • Combines governed data with ad hoc data (e.g., from Sheets or Excel).
• Example: Marketing Team and Customer Acquisition Cost:
  • Uses LookML to find metrics like customer acquisition cost in Looker reports.
  • Combines governed data with recent ad campaign data from Google Ads that hasn't yet been modeled in their database.

Conclusion

Studio in Looker unifies the strengths of both tools, empowering Looker users by combining the powerful data governance of Looker with the ad hoc analysis and visualization capabilities of Looker Studio. This integration allows for consistent, governed data to be combined with more flexible, real-time data sources, providing a comprehensive view of business performance. The key takeaway is that organizations can leverage the semantic layer in Looker to ensure data consistency while still allowing for the agility and flexibility of Looker Studio for ad hoc reporting and analysis.