Dashboards
Reports built on Google Data Studio (formerly Looker Studio), fed straight from your modeled BigQuery marts — for teams that want reporting people actually open.
The platform choice is deliberate: no new BI tool to roll out, no per-seat licenses to justify, and sharing that works like every other Google doc your company already uses.
Another BI tool, another login, another license
Every new BI platform arrives with training sessions, seat pricing and a second source of truth. Adoption dies at the login screen: the report exists, but the audience never moves in. The fastest dashboard is the one your team already knows how to open.
How it works: built on Google Data Studio, fed by your marts
Nothing between the chart and the warehouse but Data Studio's own BigQuery connector.
- 01
Marts in BigQuery
Dashboards read modeled, documented tables — never raw event exports.
- 02
Native connection
Data Studio's built-in BigQuery connector, running in your own Google Cloud project.
- 03
Templates applied
Report templates per domain — acquisition, SEO, revenue — adapted to your marts, not the other way round.
- 04
Shared like a doc
Google-account sharing, viewer or editor, company-wide or per person — with no per-seat cost.
Why Data Studio is the advantage
There is no new UI to learn — your team has almost certainly opened a Data Studio report before. There is no license line item on top of the engagement. And the report lives in your Google account next to Sheets and Drive, so sharing, permissions and access reviews work the way your company already works.
Templates, not blank canvases
Each domain starts from a proven report template — acquisition, SEO, revenue — and gets adapted to your marts. Nobody stares at an empty canvas, and every chart traces back to a documented table in your warehouse, so a number on screen always has a definition behind it.
What the reports look like
Three of the standard templates — each listing the marts that feed it.
Sessions
372,480
Users
268,940
Conversions
9,412
Revenue
€563,200
Clicks
48,220
Impressions
2.14M
Avg. position
6.8
Brand — 34% of clicks
Non-brand — 66% of clicks
One dot per day · orders (x) vs revenue (y)
Representative example. Layouts are schematic and the numbers illustrative — the real reports are built from your marts, with your numbers.
What it does not do
-
It runs on Data Studio — and inherits its limits.
We build on Google's product; we don't extend it. If Data Studio can't render it, neither can we.
-
It is not an enterprise BI platform.
No Tableau- or Power BI-class governed semantic modeling, no permission matrices beyond what Google sharing provides.
-
It is not a custom application.
If you need a bespoke product interface for your own customers, this isn't the tool.
-
It does not paper over data quality.
A broken pipeline gets fixed in the warehouse layer — never hidden behind a chart.
-
It does not move your data out of your project.
Data Studio reads your marts in place through its read-only connector. Report and warehouse both live in your own Google accounts — if the engagement ends, everything stays.
Related marts & sources
Every template reads modeled tables. These are the marts behind the reports above — and the sources behind the marts.
Marts
- mart_sessions_daily sessions by channel and market
- mart_gsc_queries Search Console clicks and impressions
- mart_gsc_pages Search Console performance by page
- mart_revenue_orders orders, revenue and order value
Representative selection — the final list depends on your stack. Source pages are linked above; detailed model pages are on the way.
Reporting your team already knows how to open.
Free discovery call · Leave with a template shortlist for your marts