Chart · reads metric
Metrics dashboard
Charts of trends.
One measure over time or across a category.
What it does
Behaviours, not fields. Choosing between two modules is choosing between these.
Several measures over the same period, so a good number can be read against the thing that explains it.
Shows shape rather than value — whether a figure is a trend or a Tuesday.
Seasonality becomes visible, which is what makes planning around it possible.
How it works
- 1
Two or three measures are plotted over the same periods so they can be compared.
- 2
Ratios like conversion are derived rather than entered, so they cannot disagree with their inputs.
- 3
The shape is the content — whether a good figure is a trend or a single good Tuesday.
- 4
Periods must be uniform, and mixing them produces a chart with a meaningless axis.
Best for
Trends and comparisons.
Not the right choice for
Exact values — pair it with a table.
What a row holds
Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.
| Field | Type | Filled from |
|---|---|---|
| Weekrequired | text | The period label. A grouping key rather than a date, so weeks or months both work. |
| Visitorsrequired | number | The first measure, summed per period from its source. |
| Ordersrequired | number | The second measure, so the two can be read against each other. |
| Conversion | text | Derived from the pair. The column that explains the other two. |
What it does not do
A module chosen for something it cannot do costs more than one that was never offered.
- Plots up to about eight periods legibly. A year of weeks is a table, not a chart.
- No statistical smoothing or seasonality adjustment. What you see is the raw series.
- One chart, one comparison. Three measures on one axis stops being readable.
- No annotations, so the week a campaign ran is not marked unless it is in the label.
Before it works
What you have to provide, if anything.
- Needs the underlying measures to exist as modules or as an uploaded dataset.
- Decide the period length first. Changing it later invalidates every stored figure.
In practice
A shop that had run a promotion and could not tell whether it worked.
“Did the campaign week actually do anything?”
What the agent built
Four weeks of visitors, orders and conversion on one chart.
What changed
The campaign week had the most visitors and the worst conversion. The traffic was wrong, not the site, and the next campaign was targeted differently.
Better with
These do a different job on the same data. An agent can have all of them.
Questions
What data does the Metrics dashboard page use?
It reads metric records the agent has collected. Charts of trends. Nothing has to be imported first — the page appears once there is something to show.
Do I have to build or configure it?
No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.
When is a chart the wrong choice?
Exact values — pair it with a table. It is best for: trends and comparisons.
Does it stay up to date?
Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.
More in Analytics & data
Orders today
23
20
Unanswered messages
4
0
Stock alerts
2
0
Overdue invoices
1
0
KPI page
Headline numbers.
Monthly performance
August · Sent 2 Sep · Maison Lauret
Quarterly review
Q2 · Sent 8 Jul · Board
Monthly performance
September · Draft · —
Stock and wastage
August · Sent 4 Sep · Internal
Reports
Generated summaries.
Data table
Uploaded rows (elastic data).
Charts
Visualize any dataset.
Ask for it in a sentence
You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.
Build your agent free