Which three numbers deserve a place on your weekly store dashboard

It is Monday morning. You have opened your sales page, checkout, email platform and social accounts, and each one is offering a different number to worry about. Before you change your product, write three figures on one page: qualified visits, purchase rate and revenue per buyer. That is enough to decide what to improve this week without turning your dashboard into a second job.

Start with a dashboard that can make decisions

A useful dashboard is not a complete account of your business. It is a short list of measurements that can change what you do next. For a digital product creator, the three numbers below cover the path from attention to purchase: how many suitable people arrived, how many bought, and how much value each order contained.

Number one: qualified visits

Begin with visits to the page you are actually trying to improve. If you are launching a template, count visits to that template's page. If you are filling coaching calls, count visits to the coaching page rather than every visit to your storefront. The word qualified matters: a thousand accidental visitors are not the same as a smaller group who came looking for the problem your product solves.

This number helps you separate a reach problem from an offer problem. If visits fell after you stopped mentioning the product, the first action may be a clearer post, newsletter or link. If visits stayed similar but purchases fell, sending more people to the same page may not address the issue. Record the source when you can, but do not let a source list replace the decision. The useful question is whether a source brought people who could reasonably buy.

Number two: purchase rate

Purchase rate is the proportion of relevant visitors who became buyers. If 240 people reached a product page and 6 purchased, the calculation is 6 ÷ 240 × 100, which gives a 2.5% purchase rate. Keep the denominator consistent. Comparing purchases from one page with all storefront visits produces a number that looks precise but does not describe one buying journey.

1. 1If qualified visits are low and purchase rate is steady, work on distribution: make the offer easier to find in the places your audience already uses.
2. 2If qualified visits are steady and purchase rate is low, inspect the page and checkout: the promise, format, price, proof, delivery details and next step should agree with one another.
3. 3If both move, avoid assigning a cause too quickly. A different audience, a seasonal launch, a broken link or a change in the offer may have affected both numbers.

Number three: revenue per buyer

Revenue per buyer shows the average value of an order. If 10 buyers produced £450 in sales, the figure is £450 ÷ 10, or £45 per buyer. Use the same definition of revenue each week: for example, sales before or after refunds, but not one this week and the other next week.

This number is useful when several products, bundles or price points are involved. A lower purchase rate can still produce more revenue if buyers choose a higher-value offer. Conversely, a week with more orders may produce less revenue if most people bought a cheaper product. That does not make the cheaper product a mistake. It tells you to ask what role it has: first purchase, standalone offer, route into a course, or complete solution.

Turn the three numbers into a weekly routine

1. 1Choose a fixed review day and write the three figures for the past seven days. Add the previous seven days beside them, using the same pages and revenue definition.
2. 2Write one sentence explaining the largest change. Use cautious language: “Visits rose after the newsletter” is safer than “the newsletter caused all sales” unless you have isolated the effect.
3. 3Choose one action for the coming week. Examples include rewriting the first section of a sales page, making one clearer invitation to buy, testing a bundle, or following up with people who requested a free resource.
4. 4Set a review date before you make the change. Otherwise, you may check too early, forget what changed, or react to ordinary variation.

Keep the collection process simple. Your store.fan analytics can give you a central place to review store activity, while sales are paid directly to your own Stripe account. If you sell through a storefront at store.fan/username, you can use the same weekly note for downloads, courses, memberships or coaching rather than stitching together a separate report for each format. The free plan is link-in-bio only; paid plans begin with a 14-day trial, and store.fan takes 0% of sales, with Stripe's own processing fee still applying.

The numbers become more useful when they sit beside the actions that can change them. A product page built with the store designer gives you a practical place to clarify the offer. If your issue is follow-up rather than page traffic, Pro adds email marketing, and you can use discount codes or flash campaigns for a defined test instead of reducing the price without a plan. The iOS app can also send instant sale alerts, which helps you notice when a campaign is working without refreshing the dashboard all day.