The KPIs worth putting in a Magento reporting dashboard, and why the default tools rarely line them up in one place.
Why the default Magento reporting falls short
Magento 2 ships a working reporting suite: sales, products, customers, abandoned carts, search terms. For checking yesterday's orders, it does the job. The strain shows when a team wants a single weekly view spanning traffic, search, and revenue.
The reports are siloed. They know orders and products, but not where the traffic came from, which pages are gaining or losing search visibility, or whether a revenue dip lines up with a CTR drop on an important landing page. That context lives in GA4 and Search Console, off in their own tabs.
They are also passive. Every chart still needs a person to read it and decide what to do next, because nothing on the screen compares the data or calls out what changed.
And they don't scale across clients. An agency running three Magento stores ends up with three reporting stacks, three spreadsheet routines, and three separate weekly reviews.
The five KPIs every Magento reporting dashboard should surface
1. Traffic and conversion: sessions, engagement rate, purchase revenue
The dashboard should open on the top-line GA4 numbers that say whether the store is healthy: sessions, engaged sessions, conversion rate, and purchase revenue, each shown against the prior period. That is the first thing anyone wants to know in a weekly review, whether the trend is up, down, or holding. Skip it and the review starts on guesswork.
2. Search visibility: impressions, CTR, average position
Search Console belongs next to revenue, not in a tab of its own. When a product page loses revenue, you want to see in the same place whether impressions dropped, average position moved, or CTR fell while impressions held. Each pattern points somewhere different, a ranking issue, a weak snippet, or a seasonal swing, and pairing the data is what keeps the diagnosis quick.
3. Order-line revenue and product movement
Magento order data is worth pulling at the line-item level rather than as one rolled-up figure, because a single total hides the product that dropped 40% while another doubled. Category revenue movement, average order value over time, top products by revenue, and product drop-off detection should all sit in the same view.
4. Priority review targets
A dashboard should do more than draw charts; it should point at what to look at. Pages pulling impressions but no clicks. Products sliding against the prior period. Categories running hot or cold against expectation. With the evidence attached, the weekly review becomes a decision session rather than a reading exercise.
5. An AI brief that reads across sources
An executive brief should read GA4, Search Console, and Magento order data together and write the week up in plain English, with specifics: "Sessions are up 12% week over week, led by the Accessories category. The product page for SKU-4821 lost 34% of its organic impressions, worth checking whether a competitor launched a replacement." That comes from the connected data, not a fill-in-the-blank template.
What about custom reports?
When people search for custom Magento reports or a report builder, they usually mean one of two things. Either a developer writes a query or a module for a report the admin does not have, or someone exports CSVs and rebuilds the numbers in a spreadsheet every week. Both work. Both cost time every single time you need the answer.
This is most of what the chat in Vysible exists for. You type the report you want, like "revenue by category last quarter" or "orders over $500 this month", and it answers from your live order database. No SQL, no export, no ticket to a developer. One-off questions stop needing a build.
Inventory and stock reporting
Magento's admin will tell you the stock level of a product if you go look it up. What it is thin on is movement: which products are selling down toward zero, and which have not moved in months. Those are the two inventory questions that actually cost money when nobody asks them.
Because Vysible reads stock levels alongside order lines, the chat handles both. "Which products are low on stock" and "what has not sold in 90 days" are one-line questions instead of a spreadsheet exercise.
Profit reporting
Honest answer first: real profit reporting needs cost data, and that is where most Magento profit reports quietly fall apart. Magento has a cost field on products, but plenty of stores never fill it in, and no tool can report margin on costs that are not there.
If your cost data exists, revenue minus cost by product or category is a question the chat can answer. If it does not, the useful proxies are the revenue-side numbers the dashboard already tracks: average order value, discount rates, and refund rates. Fixing the cost data is worth it, but that is a catalog job, not a dashboard feature.
How Vysible packages these KPIs into one dashboard
Vysible connects GA4, Google Search Console, and Magento order data into one hosted dashboard built for the weekly Magento review. The executive overview gathers traffic, search visibility, revenue, and merchandising movement; the AI brief summarizes the evidence; the priority targets name the pages, products, and categories that need attention this week.
Setup runs about a business day for a standard deployment. You grant Google Viewer access for GA4 and Search Console, run one SQL command to create a read-only Magento user, and Vysible handles the rest. The dashboard queries your sources directly and caches each one briefly, with no warehouse, ETL, or maintenance to own.
For agencies, it runs under your brand, your logo, and your domain. The Agency tier at $499/month includes up to three client deployments with dedicated support, the full gpt-5.4 model, and custom domains.