A daily KPI report is a short summary of the few numbers that tell you whether yesterday went normally: signups, orders, payments, failures. It arrives at the same time every morning, shows each number next to the previous day's, and takes a minute to read.
Daily, weekly or monthly?
Each cadence answers a different question, so the same number can belong in one report and not another.
| Daily | Weekly | Monthly | |
|---|---|---|---|
| Question | Did anything break or spike? | Are we growing? | Is the business on track? |
| Typical metrics | Orders, payments, failed payments, signups, errors in customer flows | Signups, activation, active use, revenue, cancellations | Revenue, churn, growth rate, costs |
| Compare with | The previous day, or the same weekday | The previous week | The previous month, the same month last year |
| What you do with it | Fix something today | Adjust this week's priorities | Plan |
A daily report that tries to show growth trends gets noisy, because single days jump around. A monthly report that tries to catch outages is too late. Most products need a daily report for operations and money, and a weekly one for growth.
What to include in a daily KPI report
Five to eight numbers is enough. For a SaaS product or an online shop, start with:
- Revenue events: orders paid or subscriptions started, and renewals.
- Failures that cost money: failed payments, failed checkouts, refunds.
- New users: signups or trial starts, split by source if you market on more than one channel.
- Activation: how many new users did the first important thing, such as creating a project.
- The core feature: one count that shows the product is being used, such as exports or reports sent.
- Background work customers depend on: imports finished, emails sent, jobs completed.
For each number, the report needs three things: the count, the change against the previous period, and whether that change is unusual. A count on its own says little; "orders 184, up 12%" says something.
Leave out numbers nobody acts on daily. Monthly recurring revenue, lifetime value and churn rate move too slowly to read every morning; they belong in the weekly or monthly report.
Rules that make it worth reading
- Same time, every day, in your own timezone. A report at 08:00 covering the previous day is read; one that arrives at random times is not.
- Summary first. One or two sentences at the top: was the day good, bad or normal, and what moved. On most days that line is all you need to read.
- Compare like with like. Sundays are quieter than Mondays, and public holidays quieter still. Judge a day against the days before it and the calendar, or every weekend looks like a crisis.
- Show zeros. An event that stopped completely is the most important line in the report. Make sure it shows up as 0, not as a missing row.
- One screen. If the report needs scrolling, it has too many numbers. Move the rest to the weekly report.
- Put it where you read. Email works; a team chat is often better, because the first line appears in the notification.
A daily KPI report template
Copy this into an email, a document or a chat message and fill it in each morning:
Daily KPI report - Tue 6 Oct, 08:00 (Europe/Berlin)
Summary: Orders up 12% on Monday, two thirds on the Pro plan.
Signups flat. Failed payments halved, down to 9.
Metric Yesterday Change Note
Orders paid 184 +12% Pro 121, Starter 63
Signups 212 +1% Google 140, email 72
Activation 58 -3%
Failed payments 9 -53%
Refunds 2 0%
Imports completed 1,204 +2%
Anything unusual: none.
Keep the order of the rows the same every day, so the eye knows where to look.
Example: an automated daily report
Here is the same report as Eventkiwi sends it by email, with sample data: the written summary at the top, then every event with its count, its change since the previous report, a trend line and the tags under it.
Daily report ยท My shop
Orders up 12% on Monday, two thirds of them on the Pro plan. Signups are flat. Failed payments halved, down to 9.
| Event | Count | Change |
|---|---|---|
order_paid
| 184 | +20 (+12%) |
user_signup
| 212 | +3 (+1%) |
| payment_failed | 9 | โ10 (โ53%) |
| refund_requested | 8 | +1 (+14%) |
Total: 413 events
How to automate a daily KPI report
There are three common ways, from most manual to least:
- A spreadsheet you fill in. Fine for a week; it rarely lasts longer, because the person who fills it in gets busy.
- A BI tool with scheduled emails. Works well if your data is already in a warehouse with dashboards built on it. For a small product that is a lot of setup for six numbers.
- Events sent from your code, counted and reported on a schedule. Each time something happens, your app sends one HTTP request with the event's name. A reporting service counts them and sends the report.
The third option is what Eventkiwi does. The setup:
- Create an aggregator in the app and give it a daily schedule at the time and timezone you want.
- Connect a channel: your email, a Telegram chat or a Telegram group.
- Send an event wherever the thing happens in your code:
curl -X POST "https://app.eventkiwi.com/api/event?_id=YOUR_AGGREGATOR_ID" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"name": "order_paid", "plan-pro": true}'
Any field besides name becomes a tag, so plan-pro shows up under order_paid in the report. The docs have the same call in JavaScript, Python, PHP, Ruby, Go and Rust.
From then on the report arrives every day at that time. It compares each event with the previous report, marks new events, lists stopped ones at 0, and its written summary looks at the last few reports and the calendar, so a quiet Sunday or a public holiday is called that rather than reported as a drop. If a delivery fails, the counts are kept for the next report.
The weekly KPI report
A weekly report uses the same events with a weekly schedule, for example Mondays at 09:00. With seven days in each period, the changes are steadier and show the direction: are signups growing, is activation slipping, did the new pricing change the plan mix? Tag breakdowns are more useful here too, because each tag has enough events to compare.
Many teams run both: a daily report to a chat for the people who fix things, and a weekly email for everyone else. In Eventkiwi that is two aggregators, each with its own schedule and channels; your code sends each event to both, and each send counts toward your plan's events.
Questions
How many KPIs should a daily report have? Five to eight. More than that, and the report gets skimmed instead of read.
What time should it arrive? Before the working day starts, covering the full previous day. 08:00 in the team's timezone is a common choice.
Should a daily report include revenue? Include the events behind revenue, such as orders paid and failed payments. A daily revenue total is useful for shops; for subscriptions, the weekly and monthly totals say more.
What does Eventkiwi cost? The free trial covers 100 events. Paid plans start at $19 a month for 10,000 events; see pricing.