Join our product leaders to architect your agentic future To answer a complex business question, an AI agent must understand two things: what happened, and why . The what is a governed metric, like revenue at risk; the why is the network of relationships that produced it. Because metric definitions, a. measures, traditionally live in business intelligence (BI) platforms while relationships live in knowledge graphs, an AI agent only ever sees half the picture. It guesses the rest, leading to confident but sometimes wrong answers.

To solve this hallucination problem, we introduced measures in BigQuery , which are now generally available. Historically, organizations needing both BI and knowledge graphs had to run two siloed technology stacks: one to calculate reliable metrics, the other to map out entity relationships. Bridging them entailed brittle data pipelines and runtime reconciliation by analysts and AI agents, who held the connections in their heads or in sprawling prompts.

This patchwork approach wasn't just slow and expensive — it’s where data governance broke down, as every analyst and prompt may define joins and metrics differently. Figure 1: A unified model for defining BI metrics and knowledge graphs in one place, for powering AI agents, SQL, GQL and dashboards. To replace manual reconciliation, you need a single model that understands both the structure of your business and the math that measures it. BigQuery measures builds directly on BigQuery Graph to deliver that unified foundation.

By defining measures directly on the graph entities they describe, your BI dashboards and AI agents don't just get a number they can trust — they get the relational context behind it. Finally, they can reliably answer both the what and the why . "With BigQuery measures, we can now deliver self-documenting data products. Defining measures natively in BigQuery ensures Looker Dashboards, Conversational Agents and our Data team queries operate on identical logic, guaranteeing metric alignment across leadership and significantly reducing data team maintenance overhead.