measuremy.site

Vanity Metrics vs Useful Metrics: What to Track

Screen displaying real-time COVID-19 case data with global map and statistics.
Photo by Anton Uniqueton on Pexels

The problem with vanity metrics

A vanity metric is any number that changes without telling you what to do next. It may go up and make you feel good, or down and make you worry, but it does not lead to a decision. For a small site, total pageviews is often the classic example. If pageviews go from 4,000 to 6,000 but signups stay flat, the extra traffic may be irrelevant or low quality. The pageview number alone cannot tell you whether your site is doing its job.

The opposite is a useful metric: a number that is tied to a specific goal and suggests an action. Useful metrics are usually rates, segments, or completion counts rather than raw totals.

A quick test for any metric

Before you add a number to a report or dashboard, ask four questions.

If you cannot answer the first question, the metric is probably vanity. That does not mean you should never look at it. It means it should not be the headline.

Common vanity metrics on small sites

Some metrics are not always useless, but they become vanity when they are not connected to a decision.

Bounce rate can also become a vanity metric when it is reported on its own. A high bounce rate on a contact page may be fine if people find the phone number and leave. A low bounce rate on a blog post may just mean someone scrolled around without acting. Context matters.

Useful metrics to track instead

Replace raw totals with metrics that describe whether visitors do something valuable.

These metrics are useful because they compare output to input. A spike in traffic is only good if the rate of valuable actions holds or improves.

Turn one vanity metric into a useful metric

Take a metric you already have and add a condition or denominator.

This forces you to see whether the audience is doing something, not just arriving.

Define what each useful metric should change

A metric is only useful if you know what you will do when it moves. Write down a simple rule for each one. For example:

You do not need complex automation. A simple threshold and a checklist item is enough for a small site.

Track the events that represent value

Pageviews are easy to collect, but they do not tell you who signed up, downloaded, or clicked a button. Set up events for the actions that matter. For example, a signup button can be tracked with a data attribute:

<button data-measuremysite-event="signup_click">Sign up</button>

Then your dashboard can show how many people clicked the signup button and how many completed the form. That is more useful than knowing how many people loaded the page. If you use measuremy.site, you can also build funnels from page paths and events, and ask your coding agent to read the numbers through MCP.

What to put on a weekly report

A useful weekly report for a small site is short and decision-oriented. Skip the raw visitor total as the headline. Instead show:

Then write one sentence about what you will do next. That turns the report into a working document rather than a number collection.

When a vanity metric becomes useful

Some numbers only become useful when you segment them. Total pageviews is not useful on its own, but pageviews per landing page can show which page is wasting traffic. Social follower count is not useful, but followers who click a link and sign up is useful. The raw number is not the problem; the lack of connection to a goal is.

If a metric makes you feel busy but never changes a decision, move it to the bottom of the report or remove it. The goal is not to track everything. It is to track the few numbers that tell you what to do next.

Start with one goal, such as signups or purchases, and build your dashboard around that. Then add only the metrics that would change how you spend the next hour. That discipline keeps a small site focused on useful metrics instead of flattering ones.

See it on your own site

measuremy.site is cookieless analytics your coding agent can read. 30-day free trial, no card. Plans from $9/month.

Start free trial See the live demo

Add measuremy.site analytics to this project: connect the measuremy.site MCP server at https://a.measuremy.site/mcp for all my projects (claude mcp add --scope user; it signs in with OAuth, no key, and one sign-in covers every site), then tell me how to sign in. Details: measuremy.site/llms.txt

Free tools

All free tools

More from the blog