Vanity Metrics vs Useful Metrics: What to Track
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.
- What decision would change if this number moved?
- Can I act on it this week?
- Does it measure progress toward a real goal?
- Would I still care about it if nobody else saw the dashboard?
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.
- Total pageviews across the whole site with no segment or goal
- Social media follower counts when followers do not visit or convert
- Raw visitor counts by country when you only sell locally
- Email open rates when the goal is replies, purchases, or signups
- Time on page when the page is a short landing page designed to send people elsewhere
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.
- Signups or purchases per 1,000 visitors
- Conversion rate by source, campaign, or landing page
- Funnel completion rate from first visit to goal
- Revenue or pipeline value per visitor
- Key event completion rate, such as trial starts, file downloads, or click-to-call
- Cost per signup or cost per purchase for paid traffic
- Returning visitor conversion rate when repeat visits matter
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.
- Pageviews becomes pageviews per signup
- Visitors becomes visitors who clicked the pricing page
- Downloads becomes downloads per campaign click
- Newsletter signups becomes signups per blog post pageview
- Social traffic becomes social traffic that reached the pricing page or started a trial
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:
- If signup conversion from organic search drops for two weeks, review the landing page headline and form.
- If cost per signup from a paid campaign rises above your target, pause the campaign or change the ad.
- If the pricing page gets more visits but trial starts stay flat, test the pricing page layout or offer.
- If a blog post brings traffic but no email signups, add a clearer call to action or write a follow-up post.
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:
- Signups or purchases this week
- Conversion rate by top three sources
- Funnel drop-off at the biggest step
- Cost per result for any active paid campaign
- Any unusual change from the previous week
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 demoAdd 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
- Analytics tag checker: Which analytics and pixels a site runs, plus duplicate and broken tags.
- Free UTM link builder: Add utm_source, medium and campaign to any link.
- Website traffic checker: A site's popularity rank and estimated monthly visits.
More from the blog
- How to calculate your website conversion rate, and what to compare it to
- Is my A/B test result significant? A plain-English guide with a worked example
- What is bounce rate, how is it calculated, and is yours a problem?
- How to add a visitor counter to your website or GitHub README
- How much traffic does a website get? How to estimate any site's visits
- How to track QR code scans: count them, and see which poster worked
- How to see how many people clicked your link (without a paid shortener)
- How to check if your Google Analytics 4 tag is installed (and only counting once)
- Why GA4 shows your campaign traffic as Unassigned (and how to fix the links)
- Does your redirect keep your UTM tags? How to check before a campaign goes out
- How I built a self-hosted analytics MCP server on Cloudflare Workers and D1
- UTM tracking explained: what the parameters mean and how to use them
- Conversion funnel analysis for small sites: a practical guide
- Sudden drop in website traffic? A checklist for finding the cause
- What is an MCP server? A plain-English guide for people who run websites
- How to Compare Cookieless Website Tracking Tools
- Why Your Analytics Numbers Differ Between Tools
- When GA4 Is Too Much for a Small Website
- How to keep historical data when switching analytics tools
- How to give an AI agent read-only access to your analytics
- Why developers are connecting agents to production data
- How to recover from a sudden traffic drop
- Website analytics for indie hackers: what to watch and what to ignore
- Direct Traffic Explained: Why So Much Is Unknown
- Why a high bounce rate is not always bad
- High bounce rate: 8 causes and practical fixes
- How to Set Up Traffic Alerts for Sudden Drops
- How to Track Traffic From a Podcast
- How to measure the return on a paid ad campaign
- How to use analytics to decide what to write next
- How the Model Context Protocol Works
- Track File Downloads Without Guesswork
- Adding analytics to a Next.js app without slowing it down
- Core Web Vitals and Traffic: Is There a Link?
- Analytics After Cookies: What Actually Changes
- GDPR and website analytics: a practical guide for small sites
- How to Compare Website Analytics Tools by Privacy
- GA4 Events Explained for Beginners
- How to measure a newsletter send with UTM links
- How to track Hacker News traffic
- Adding Analytics to a Framer Site
- How to ask your coding agent about your analytics
- What Is Bounce Rate and How Is It Calculated?
- A practical website analytics retention policy
- Map your site's funnel from first visit to signup
- What Is a Good Bounce Rate?
- How to automate a weekly traffic report
- A Practical Privacy-Friendly Analytics Checklist
- Adding an MCP server to Claude Code
- How long should you keep analytics data?
- How to Build a Small MCP Server That Actually Helps
- How to Find the Biggest Drop Off in a Funnel
- What Is the Urchin Tracking Module?
- What Microsoft MCP servers actually do
- UTM parameters for email newsletters
- Track Button Clicks Without Google Tag Manager
- How to track the results of a social media post without cookies
- How to track traffic from a GitHub README
- How to measure a product launch without guessing