When the question isn't on a screen yet.
Drag a measure. Drag a dimension. Pick a chart type. Every model in the semantic layer is queryable right here, so the answer is one drag away even when nobody built the dashboard for it.
- Plp Session %
- Pdp Session %
- Add to Cart Sessions
- Checkout CVR %
- Session to CVR %
- Total Purchase Revenue
- Web Traffic
- Avg Session Duration
- Customer Sessions
- Engagement Time
- User Count
| Region / City | Add to Cart | Checkout CVR | Session → CVR | Revenue ₹ |
|---|---|---|---|---|
| ⊟Punjab | 2.00 | 100.00 | 0.92 | 1,999 |
| Ludhiana | 2.00 | 100.00 | 0.92 | 1,999 |
| ⊟West Bengal | 2.00 | 50.00 | 1.92 | 1,999 |
| Kolkata | 2.00 | 50.00 | 1.92 | 1,999 |
| ⊟Delhi Division | 5.00 | 150.00 | 3.18 | 16,193 |
| New Delhi | 2.00 | 100.00 | 2.63 | 14,394 |
| ⊟Haryana | 3.00 | 66.67 | 8.70 | 3,979 |
| Gurugram | 3.00 | 66.67 | 8.70 | 3,979 |
| ⊟Tamil Nadu | 1.00 | 100.00 | 14.29 | 1,999 |
| Madurai | 1.00 | 100.00 | 14.29 | 1,999 |
| Total | 14.00 | 483.34 | 29.36 | 28,168 |
- Heatmap
- Search
- Sub totals
- Cell bars
The real builder, recoloured. Flip the chart type and the same query redraws.
Four moves. One canvas.
Every model in the semantic layer is one drag from a chart, including the ones we never built a screen for.
Pick a model
Sales, marketing, cohorts, fulfilment, quick commerce, B2B, planning. Everything modelled in the semantic layer is queryable here, not just the screens we pre-built.
Drag measures and dimensions
Compose a pivot, layer filters, add a comparison window. The semantic layer writes and runs the query underneath, so there is no SQL to learn.
Switch how you see it
The same query as a pivot, a line, a bar or an area. One toggle, no re-querying.
Save and share
Group related charts into a dashboard, set a refresh cadence, pin it to the team board. Per-role views open straight in Slack, and everyone reads the same numbers because everyone reads the same model.
Pick how you see it.
One query, every shape. The format is a toggle, never a rebuild.
No SQL to write. None to read.
You compose with measures and dimensions. The semantic layer turns that into a governed query, runs it, and hands back the number. The query stays under the hood.
You speak measures. The layer does the rest.
Drag the fields you care about. The semantic layer resolves them to agreed definitions, writes the query and runs it, so there are no tables to join and no SQL to learn.
- Compose with governed measures and dimensions
- The semantic layer writes and runs the query for you
- One definition per number, shared across every team