Guide

Measure what you do and learn from it

You cannot fix what you cannot see, and most sites see very little.

By Surfil Updated

8 min readBack to guides

Key takeaways

If you read nothing else

  • Start with three numbers and the decision each informs.
  • Fire events on real conversions.
  • One naming rule for campaign links makes sources add up.
  • One decision per weekly review.

Plenty of teams work hard and cannot say what worked. The site changed, sales moved, and nobody can say whether the two are related. Self-awareness is the ability to measure your own performance and learn from it. It is the quiet multiplier behind every other index: a team that can see its results improves faster than one that guesses. This guide builds the habit in four moves: choose the numbers, collect them honestly, label your traffic, and review on a schedule.

3
Numbers to start with, not thirty
4
Data sources worth connecting
1
Weekly review, ending in one decision
1
Naming rule for every campaign link

What self-awareness means

It is simple to state and uncommon in practice: when you change something, can you tell whether it helped?

That needs three things. You have to be recording the right events. You have to be able to tell where visitors came from. And you have to compare before and after on a schedule, not just when you remember.

Self-awareness in Growth Score reflects how much of your own performance you can measure. It reads which of your data sources are connected, such as the pixel, Google and Stripe. It is the one index you improve directly, by connecting what you already have, and once it is in place the other eight become much easier to read.

Pick a few numbers

More metrics do not mean more insight. A dashboard with forty tiles gets glanced at and never acted on.

Start with three, one for each stage of a customer's path:

  • Reach: how many people who could become customers visited. Organic visits from search, and visits from AI answers, are a good start.
  • Action: how many took the step that matters: sign-ups, purchases or booked calls.
  • Value: what it was worth. Revenue, or an honest estimate of lead value.

Then decide your north star, the one number that best reflects customers getting value, and treat everything else as an input. Beware vanity metrics: page views, followers and total sign-ups that never log in look good and tell you nothing about what to do next.

For each number, write one sentence: what decision would change if it moved. If the answer is "nothing", drop it.

Collect data honestly

Four sources cover most small sites:

  • Your own site, through a lightweight tracker or pixel that records visits, referrers, speed and conversions.
  • Google Search Console, for what people searched to find you and where you appeared.
  • Google Analytics or a similar tool, if you use one, for behaviour inside the site.
  • Your payment system, read only, for what actually sold.

Connect them, and check them against each other. If your tracker shows more sales than your payment system, find out why before you trust either.

Choose tools that fit your privacy promises. Cookieless, first-party measurement avoids consent banners for analytics and keeps visitors' data out of other companies' hands.

The Surfil pixel records page paths, referrers, AI referrals, real speed and conversions with no cookies and no personal data. Whatever you choose, tell visitors plainly what you collect.

Mark every conversion

A tool cannot count what you have not told it about. For each action that matters, define a key event: a completed sign-up, a finished purchase, a submitted contact form.

Fire it once, at the moment the thing really succeeds, not at the moment a button is clicked. Success is the thing you want to count.

A few rules save pain later:

  • Name events the same way everywhere, in one shared list.
  • Fire on success, not on the attempt. A failed payment is not a sale.
  • Pass the value where there is one, such as the order total.
  • Test each event yourself, on a phone, and confirm it appears once and not twice.
  • Write down where each one lives so the next person can find it.

A small written tracking plan, a table of event name, trigger, where it fires and who owns it, is one of the most useful documents a small team can own.

Label your traffic

Without labels, much of your traffic arrives as "direct", which really means "we do not know". Some of it is dark traffic from private messages, apps and emails. Some is campaigns you ran and cannot now trace.

UTM parameters fix the part you control. They are tags on a link: source, medium and campaign. A link in your newsletter might carry source=newsletter, medium=email and campaign=october-launch.

The discipline is consistency. If one person writes Facebook and another facebook, your report shows two sources. Use a simple convention:

  • Lowercase everything.
  • A fixed list of sources and mediums, kept in a shared sheet.
  • Campaign names: what and when.
  • Never put UTM tags on links inside your own site, because they overwrite the true source.

The campaign link builder keeps these consistent and reads back the links you already use, so you can find the ones that disagree.

Run a weekly review that ends in a decision

Data nobody reviews is a cost. Put thirty minutes in the calendar, the same time each week, with the same questions:

  1. What moved? Look at your three numbers against last week and against the same week a month ago.
  2. Why do we think it moved? Name the change, the campaign or the outside event.
  3. What did we expect from last week's action, and what happened?
  4. What is the one thing we will do next?

Write the answers in a running log, one short entry per week. After two months, the log is a record of what you believed, and what turned out to be true. That is how teams learn their own habits and blind spots.

If you notice you never run the review, make it smaller, not skipped. Ten minutes and one question beats a perfect meeting that never happens.

Learn from people too

Numbers say what happened. People say why. Pair them.

  • Read every support ticket and review for a month, and count the themes. The same complaint ten times is a finding.
  • Add a one-question survey at a key moment, such as after cancellation: "What was the main reason?" Keep it short and read every answer.
  • Talk to five customers a quarter, and ask them to describe the last time they used the product.
  • Run a session recording or two on the page that leaks most, to see where real people struggle.

Combine these with the funnel from your tracker, and you can say which step is leaking and the reason behind it.

Make it a small routine

Your first week:

  1. Write down your three numbers and the decision each informs.
  2. Connect the sources you already have: your tracker, Google and your payment system, read only.
  3. List the key events, and fix any that fire wrongly.
  4. Share one UTM naming rule.
  5. Book the weekly review.

Then leave it alone for a month and let the data collect. Growth Score shows which sources you have connected and what each unlocks, so you can see the gaps. The free Growth Diagnosis shows where you stand today.

Before you move on

The checklist

Tick these off on your own site. Each one comes from the guide.

  • Write down your three numbers
  • Connect your tracker and payments
  • List your key events and test each
  • Agree one UTM naming rule
  • Book a weekly thirty-minute review
  • Read support tickets monthly
  • Keep a short running log

In Growth Score

Which pillar it moves

Fixing what this guide describes shows up in this part of your score.

FAQ

Questions after reading

Do I need Google Analytics?

No. Any measurement you trust works, as long as you check it against what actually sold.

Can tracking respect privacy?

Yes. Cookieless, first-party measurement records visits and conversions without personal data.

Measure a few things honestly, write down what you expect, and check. That loop is the whole discipline.

Test what you can measure

Have a question?

We're here to help. Get in touch and let's talk.