Klaviyo Dashboard Without Another Tool

A good email dashboard is five panels, not twenty. Here is the set that earns its place, what to leave out, and how to keep it current without maintaining a separate reporting stack.

A useful Klaviyo dashboard has about five panels: revenue share by month, top campaigns, flow revenue, list growth and deliverability. Everything else needs to justify itself by naming a decision it supports. This post lists the panels, the numbers that mislead, and how to keep the dashboard current without adding a separate reporting stack.

Start from decisions, not metrics

Dashboards fill up because adding a chart is cheaper than deciding what it is for. The test for each panel is a sentence: "If this goes up or down, I will do X." Open rate fails the test: you will not do anything differently based on a number that includes machine-generated opens. Revenue per recipient passes: if it falls, you look at the offer, the segment or the send frequency.

For email and SMS the real decisions are few. Which campaign do I repeat or retire? Which flow needs rebuilding? Am I sending too much? Is the audience healthy enough to keep growing revenue next quarter? Five panels cover them.

The five panels

1. Attributed revenue share by month. Revenue Klaviyo credits to email and SMS, divided by all order revenue Klaviyo sees, split by channel. It answers how much of the business email touches. Read it as influence rather than cause, because attribution gives credit to any order that followed an interaction.

2. Top campaigns. The last 90 days by revenue, with recipients and revenue per recipient beside them. Revenue alone rewards big sends. Per-recipient revenue shows which sends were efficient.

3. Flow revenue by month. Each flow, with a trend. Flows are the part of email that earns without a send button, so decay in a flow is the most expensive quiet problem in the program.

4. List growth. Subscribes and unsubscribes by month, and net growth as subscribes minus unsubscribes. These are events, not list size, so label the panel that way.

5. Deliverability. Spam complaints and bounces by month. A rise here predicts trouble in everything else, since mailbox providers act on complaints.

What to leave off

• Open rate as a headline. Pre-loaded opens inflate it. Keep it in a diagnostic view for spotting anomalies.
• Averages of rates. The mean of campaign click rates treats a small send like a huge one. Compute click rate as total clicks over total recipients for the period.
• Lifetime totals. They only go up and tell you nothing about this month.
• Revenue without a denominator. Always put recipients or store revenue next to it.

Three ways to build it

You can use Klaviyo's built-in dashboards, which are the right place to start for in-platform work. You can export or connect to a spreadsheet or BI tool, which gives flexibility at the cost of refresh limits, connector upkeep and formulas that drift between charts. Or you can ask for each panel as a question in a tool that already holds your definitions. The third is what this post describes.

Doing it with Quiriz

The Klaviyo connector (read-only, daily refresh, in beta) imports [Klaviyo] Attributed revenue by day, [Klaviyo] Campaigns, [Klaviyo] Flows by month and [Klaviyo] Audience activity by day. Each panel is one question:

• "What share of our revenue comes from email and SMS, by month?"
• "Which email campaigns earned the most revenue in the last 90 days, with revenue per recipient?"
• "Flow revenue by flow and month."
• "Is our list growing? Subscribes versus unsubscribes by month."
• "Spam complaints and bounces by month."

Metrics like Klaviyo attributed share, Klaviyo click rate and Klaviyo revenue per recipient are defined once in Company Context. A saved question that produces a chart or table can be rerun as data refreshes, so the dashboard is a set of saved questions rather than a separately maintained build. Anyone with access can then ask a follow-up, such as why a flow fell in a particular month, from the same dataset instead of waiting for whoever owns the dashboard. If you also connect Shopify, the revenue share panel can be shown beside net sales; see Klaviyo and Shopify: Revenue by Flow vs Campaign.

Give the dashboard an owner

Dashboards decay when nobody owns them. Name one person who reads it on a set day, and make them responsible for the sentence that follows each panel: what changed and what, if anything, to do. Without that sentence a dashboard is wallpaper. A good rhythm is a five-minute weekly look at revenue share and the last week's campaigns, and a thirty-minute monthly look at flows and list health. If a panel has gone three months without prompting a decision, remove it and put the space to something that does.

Honest limits

• It is not a drag-and-drop canvas. You get answers, charts and saved questions, not pixel-level layout control. If you need a heavily designed wall display, a dedicated BI tool may suit better.
• Twelve months of history. That is the span Klaviyo allows for a report.
• Daily refresh, which is enough for email but not an intraday monitor.
• Revenue needs a store connected to Klaviyo. Without it, revenue panels read zero.
• Per-message flow results are not read; flows are shown by flow and month.

The same approach to other platforms is described in HubSpot Dashboard Examples, and a first set of questions is in Klaviyo AI: Ask Your Email Data Questions. Store teams may also want Quiriz for ecommerce.

Frequently asked questions