Skip to content
KONIGI

Domains

Embedded analytics

Somebody else's charts inside your product, themed hard enough to look like they were always there.

3 products 5 captures

Products 3

Retool

A builder aimed at people making internal tools, so it shows what a dashboard looks like when the person assembling it is the person who will use it.

Admin and devtools · Embedded analytics
Stripe

The reference for a financial admin surface: dense tables with in-cell state, and a home page that is a small strip of numbers above a very long list.

Consumer fintech · Ecommerce · Embedded analytics
Tableau Public

Thousands of dashboards made by people who are not designers, published without a review step. The best available sample of what the pattern language looks like in the wild.

Embedded analytics · Product analytics

Patterns seen in this domain 18

Captures

Newest first within each product.

Tableau Public

Tableau Public — Cohort Retention Analysis
Cohort grid. One row per cohort, one column per period since joining. The triangle is the shape, not a rendering accident. Ratio and rate. Cohort dates, and no cohort size. A 100% first cell could be ten people or ten thousand. Sequential and diverging scales. Column one is 100% for everyone and takes the darkest step, so a constant sets the top of the ramp. Cohort grid. 50% then 9%. The last cell in every row is a partial period drawn as a finished one.
Cohort Retention Analysis September 11, 2026 Tableau Public embed view; workbook published by Tyran Christian medium · light · desktop-web
The triangle, exactly as the entry describes it: thirteen monthly cohorts down the side, thirteen periods since joining across the top, and each row one cell shorter than the last because younger cohorts have had less time. Reading down column two gives the comparison the grid exists for—37%, 22%, 19%, 15%, then a slow climb back to 24%—which no single averaged retention number could show. Two things undercut it. The first column is 100% for every cohort by definition, and it takes the darkest step on the ramp, so the one column carrying no information anchors the scale and compresses every real value between 2% and 50% into what is left. And look along the staircase edge: 9%, 4%, 3%, 2%, 4%, 2%, 4%, 2%, 3%, 4%. Every row's final cell falls off a cliff relative to its neighbour, because that period is still in progress and is being drawn as though it were complete.
  • Cohort grid One row per cohort, one column per period since joining. The triangle is the shape, not a rendering accident.
  • Cohort grid 50% then 9%. The last cell in every row is a partial period drawn as a finished one.
  • Sequential and diverging scales Column one is 100% for everyone and takes the darkest step, so a constant sets the top of the ramp.
  • Ratio and rate Cohort dates, and no cohort size. A 100% first cell could be ten people or ten thousand.
Tableau Public — Emergency Department / Clinical Dashboard
Sequential and diverging scales. A diverging blue-orange ramp on wait time, which has no meaningful centre, so the midpoint is wherever the mean fell. Small multiples. Twelve month panels on one shared y-axis, so the seasonal fall from 265 in May to 52 in December is comparable across all of them. Calendar heatmap. The punch-card variant: hour of day against weekday. The busy band reads in a second, from the layout alone. Target and progress. Each unit against a median reference line, green below and red above. A target marker doing the work of a threshold. Filter bar. One dropdown, full width, showing its selected value rather than a count. Everything below is scoped to it.
Emergency Department / Clinical Dashboard September 11, 2026 Tableau Public embed view; emergency department patient flow workbook dense · light · desktop-web
Worth recording partly for what it is not. I went looking for a bed map, and what the public web has instead is this: analysis about an emergency department rather than the board the department actually runs on. There is no row per bed, no occupancy, no waiting-for column. Track boards live inside the patient record and never leave it, which is why that pattern has no example here and probably never will. What this does have is the punch card the calendar-heatmap entry names as the better answer for anything with a daily rather than weekly shape: weekday down the side, hour of day across the top, and the busy band from roughly ten to twenty-one is legible instantly without anyone labelling it. Its ramp is the problem—a blue-to-orange diverging scale on a patient count, which has no meaningful centre, so the midpoint sits wherever the data happened to average. The treemap beneath it degenerates into a mosaic of unlabelled slivers about a third of the way across.
  • Calendar heatmap The punch-card variant: hour of day against weekday. The busy band reads in a second, from the layout alone.
  • Small multiples Twelve month panels on one shared y-axis, so the seasonal fall from 265 in May to 52 in December is comparable across all of them.
  • Sequential and diverging scales A diverging blue-orange ramp on wait time, which has no meaningful centre, so the midpoint is wherever the mean fell.
  • Target and progress Each unit against a median reference line, green below and red above. A target marker doing the work of a threshold.
  • Filter bar One dropdown, full width, showing its selected value rather than a count. Everything below is scoped to it.
Tableau Public — Energy flows in the Regional scenario
Sankey and path. Three columns of nodes, link width as volume, and crossings kept to the few places where a carrier genuinely switches rank. Categorical series palette. Five carriers, five hues, held constant across every column so a band can be followed end to end. Ratio and rate. 546 TWh in, 476 TWh out, both stated. The diagram's own arithmetic is checkable from the page. Dashboard builder. Curve type, whitespace and squish ratio exposed as reader-facing controls. The last one reads 0.484057971. Sankey and path. Conversion losses as an explicit destination. This is the node product analytics leaves out, and the reason its widths stop adding up.
Energy flows in the Regional scenario September 11, 2026 Tableau Public embed view; workbook published by Chia Yu Lin medium · light · desktop-web
A Sankey doing the job it was invented for, published by an analyst rather than designed by Tableau. The entry argues that the form comes from engineering, where what enters a node leaves it, and that conservation is what makes band width readable as quantity—and that product analytics breaks it because people leave and nothing accounts for them. Here conservation holds and is stated: primary supply 546 TWh at the bottom left, final demand 476 TWh at the bottom right, and the missing 70 TWh has its own destination node called Conversion losses. Nothing disappears off the edge of the diagram. Colour is doing identity rather than status—blue for electricity, green for hydrogen, teal for biomass, orange for heat—and it stays consistent across all three columns, so a carrier can be traced from supply to end use without a legend. The one oddity is that the author has exposed the layout parameters as live controls, including a squish ratio printed to nine decimal places.
  • Sankey and path Three columns of nodes, link width as volume, and crossings kept to the few places where a carrier genuinely switches rank.
  • Sankey and path Conversion losses as an explicit destination. This is the node product analytics leaves out, and the reason its widths stop adding up.
  • Ratio and rate 546 TWh in, 476 TWh out, both stated. The diagram's own arithmetic is checkable from the page.
  • Categorical series palette Five carriers, five hues, held constant across every column so a band can be followed end to end.
  • Dashboard builder Curve type, whitespace and squish ratio exposed as reader-facing controls. The last one reads 0.484057971.
Tableau Public — User Funnel & Conversion Rates
Funnel. Drawn as a taper, so the count is the width of a trapezoid. Length would have read more accurately for nothing. Header KPI strip. Three counts, boxed and centred, with no delta and no base. The first and last are the funnel's own endpoints. Funnel. Overall conversion only. The trial-to-payment step converts at 30% and no number on the chart says so. Ratio and rate. A 20% rate over 10 registrations drawn the same size as a 26% rate over 3,673. Tabs as genres. Seven worksheet tabs across the top, named after the data rather than the question—Users : Registration, CVR to Start of Trial.
User Funnel & Conversion Rates September 11, 2026 Tableau Public embed view; workbook published by Tetiana Berezhna medium · light · desktop-web
Another published workbook rather than anything Tableau designed, and it makes both of the mistakes the funnel entry names. It shows one number per step, not two. The labels down the right read CVR 100%, 74%, 55%, 37%, 23%, 7%, and every one of those is overall conversion—the share of the original 8,460 still present. Step conversion is missing, which matters because the worst step in this funnel is invisible: 1,948 people start a trial and 577 pay, so that step converts at 30%, and nothing on the chart says 30. You have to divide two numbers printed four inches apart. The second is the rendering. It is drawn as a taper, so quantity is encoded as the width of a trapezoid, and the eye compares areas rather than lengths. Plain horizontal bars would have been easier to read and easier to label. The panel on the left has a third problem: a 20% conversion rate sits above a bar of 10 registrations, next to a 26% rate over 3,673, at the same size and in the same grey.
  • Funnel Drawn as a taper, so the count is the width of a trapezoid. Length would have read more accurately for nothing.
  • Funnel Overall conversion only. The trial-to-payment step converts at 30% and no number on the chart says so.
  • Ratio and rate A 20% rate over 10 registrations drawn the same size as a 26% rate over 3,673.
  • Header KPI strip Three counts, boxed and centred, with no delta and no base. The first and last are the funnel's own endpoints.
  • Tabs as genres Seven worksheet tabs across the top, named after the data rather than the question—Users : Registration, CVR to Start of Trial.
Tableau Public — Shopify Customer Journey
Ranked list. 490 against 30 for second place, so every bar below the first is a sliver and the ordering is all you get. Time series. Titled per month, plotting seven days, on an axis starting at 500K. A 25% spread rendered as a cliff. Geo map with markers. A choropleth of raw sales, unnormalised, so California and Texas lead partly by being large and populous. Header KPI strip. Nine values in a grid rather than four to six in a row, so there is no privileged place for the eye to start. Cross-filter. The tiles are the filter. It needed a line of instruction above it, because nothing about a number says it is clickable. Hover detail. The breakdown by city exists only on hover, so it is unavailable on touch and invisible in this screenshot.
Shopify Customer Journey September 10, 2026 Tableau Public embed view; workbook published by Lovelytics medium · light · desktop-web
Tableau Public is the product; the design decisions here are the author's. This workbook was published by Lovelytics, so read it as what a competent analyst builds in Tableau rather than as how Tableau thinks dashboards should look. What is instructive is that it carries three separate lines of small-caps instruction—"click on metric to filter dashboard", "hover on a province to view breakdown by top 10 cities", "click on bar to view the second product purchased". Every interaction on the page needed a label, because none of them announces itself. That is the honest cost of cross-filtering: it is powerful and it is invisible until someone tells you it is there. Two other things. The tile block is nine values in a three-by-three grid, which is past the point where a strip has a reading order—the eye has to be told where to start and isn't. And the chart titled "Total sales per month" is plotting seven days, on a y-axis that begins at 500K, so a roughly twenty-five percent spread draws as a mountain range.
  • Cross-filter The tiles are the filter. It needed a line of instruction above it, because nothing about a number says it is clickable.
  • Header KPI strip Nine values in a grid rather than four to six in a row, so there is no privileged place for the eye to start.
  • Time series Titled per month, plotting seven days, on an axis starting at 500K. A 25% spread rendered as a cliff.
  • Hover detail The breakdown by city exists only on hover, so it is unavailable on touch and invisible in this screenshot.
  • Geo map with markers A choropleth of raw sales, unnormalised, so California and Texas lead partly by being large and populous.
  • Ranked list 490 against 30 for second place, so every bar below the first is a sliver and the ordering is all you get.