Normalized claim
Dashboards eliminated: 20,000 count decrease
Instead of maintaining a sprawling footprint of 20,000+ dashboards
Yahoo! centralized fragmented analytics pipelines into BigQuery and standardized enterprise metrics in Looker with LookML to reduce dashboard sprawl across its distributed GM business units. The company added Looker Conversational Agents powered by Gemini so non-technical users could ask cross-functional questions in natural language while staying within governed Looker security and access controls. Yahoo! also embedded deep links into operational dashboards and is planning a Model Context Protocol-based Looker integration to support future agentic analytics workflows.
Reported outcomes
Dashboards eliminated: 20,000 count
Sustainability & resources
Normalized claim
Dashboards eliminated: 20,000 count decrease
Instead of maintaining a sprawling footprint of 20,000+ dashboards
Normalized claim
Looks eliminated: 30,000 count decrease
30,000+ Looks
Normalized claim
Explores eliminated: 1,300 count decrease
1,300+ Explores
Normalized claim
Insight delivery time: 99.9% decrease
compress insight delivery timelines from days to mere seconds
Normalized claim
Operational time recaptured: 10 seconds per interaction decrease
Saving just ten seconds per interaction across thousands of high-velocity corporate users
Yahoo! also embedded deep links into operational dashboards and is planning a Model Context Protocol-based Looker integration to support future agentic analytics workflows
Primary read
Showing 2 of 2
Yahoo! organized its analytics on BigQuery and Looker, using LookML to codify governed semantic definitions. It then layered Looker Conversational Agents powered by Gemini on top of the semantic model, with user attributes and access filters enforcing security. The team also embedded operational deep links into dashboards and described a roadmap to connect external LLM tools to Looker through an MCP server using OAuth PKCE.
AI-generated summary. Verify important details with the linked sources before relying on this case.
Was this useful?
Community
No published comments yet.