How do I track KPIs and metrics with iDBQuery?

KPI tracking usually means maintaining brittle dashboards and chasing down why a metric looks wrong. iDBQuery simplifies both.

• Define metrics by asking — "Monthly active users," "gross margin by product," "days sales outstanding." iDBQuery writes the query and renders the result; pin it to a dashboard to watch over time.
• One source of truth — define a metric once in the semantic layer (what counts as "active," how revenue is calculated) and everyone's number matches.
• Cross-source KPIs — a metric blending data from a database, a spreadsheet target, and an API all resolves in one query, because iDBQuery treats them as one model.
• Cited and drillable — click any KPI to see the exact rows behind it, then ask "why did it move?" and follow the trail.

When a KPI drifts, you don't file a ticket — you ask iDBQuery, or hand it to the Analyst agent, which investigates the change and returns a cited explanation. The dashboards are shareable, so leadership watches the same live metrics you do. Because everything runs on live queries against your real sources, there's no refresh job to babysit and no exported snapshot going stale between updates.