CompanyWebsite measurement does not require dozens of reports. A small business needs to see whether the right people find the site, what they read and whether important pages lead to contact or another intended action.
This guide helps build a light measurement practice. It is not privacy or legal advice. Check requirements separately if the site handles personal data or uses third-party tracking services.
A small weekly view where every metric connects to a decision or next action.
Start with the decision
Begin with the question you want answered. Do people find the service page, read the price or complete the contact path? Once the question is clear, unused metrics are easier to remove.
“We want more data” does not say what happens next. A better goal is to find out whether product-page visitors reach the trial or contact action.
Do this
- Write one business question.
- Name the decision the answer will support.
- Remove any metric that changes no decision.
Keep the main view small
A useful weekly view fits on one screen. It might show visits, popular pages, key traffic sources and one goal event. Add a metric only after naming its user and purpose.
Compare trends over time rather than reacting to one day. Use the same period and note launches or campaigns that may explain changes.
Check at least these
- Visits or visitors in the chosen period.
- Entry and exit pages.
- Important traffic sources.
- One important action, such as contact.
Check what the site actually sends
An analytics tool is not the only possible data collector. Forms, video, maps, chat and external fonts may contact other services. List the components in use and their purpose.
Collect only data you use. Remove old services whose owner or purpose no one can name.
Do this
- List third-party services.
- Record each service's purpose and owner.
- Remove unnecessary or forgotten measurement.
- Review the whole whenever a new tool is added.
Interpret weekly instead of stacking reports
Set aside a short weekly moment. Review the same view in the same order and write down one observation. An observation is not yet an explanation; it identifies what to inspect next.
Choose one small change, give it enough time and continue following the same metric.
Do this
- Review the same period each week.
- Record one change or exception.
- Choose one possible explanation to check.
- Make one change and follow the same metric.
Keep measurement understandable
Every term in a report should be explainable in plain language. If no one knows what a session, event or engagement means in your setup, the number cannot yet support a decision.
Record the definition, data source and latest review date next to each metric.
Check at least these
- What does this metric mean on this site?
- Where does it come from?
- Who uses it?
- When was it last checked?
Checklist before continuing
- One decision is the starting point.
- The weekly view contains only used metrics.
- Third-party services and purposes are documented.
- Every metric has a clear definition.
- An observation leads to one tracked change.