Topic hub

Measuring Performance

Website performance should be measured by whether the site helps people complete useful tasks and produces outcomes the business can act on. Sessions, page views and average engagement can provide context, but they are…

2 published guides0 subtopicsUpdated 21 July 2026

Start here

The main guide for this topic

Comparison

Privacy-Friendly Analytics Alternatives

Privacy-friendly analytics is not a product label but a design decision about purpose, data, storage, access and legal controls. A simpler tool can reduce data collection, yet the organisation must st…

Open the complete guide →

Published guides

Articles in this section

Comparison7 August 2026

Privacy-Friendly Analytics Alternatives

Privacy-friendly analytics is not a product label but a design decision about purpose, data, storage, access and legal controls. A…

Read guide →

Step-by-step21 July 2026

How to Measure Website Enquiries

Measuring website enquiries means connecting a visitor action with an actual business outcome. A form event alone does not show wh…

Read guide →

About this section

Information checked: 21 July 2026.

In brief: Measure business actions first, then use traffic and behaviour metrics to explain them.

Start with a measurement map

From business outcome to evidence
Business outcome	Website action	Supporting evidence
Qualified enquiry	Form success, call or email action	Source, landing page and CRM outcome
Appointment	Confirmed booking	Service, time, cancellation and attendance
Sale	Server-confirmed order	Revenue, margin, refund and repeat purchase
Self-service success	Completed support task	Reduced support demand and user feedback
Local visit	Direction, call or booking action	Profile and website evidence plus offline outcome

Use more than one system

Search Console for Google Search visibility and indexing.
Web analytics for on-site journeys and events.
Form, booking, payment or CRM records as the operational source of truth.
Call tracking or documented call handling where proportionate and lawful.
Server logs and uptime monitoring for technical diagnosis.

Quality controls before trusting data

Write an event specification with names, triggers and required parameters.
Test success, failure, duplicate submission and consent states.
Exclude internal or test traffic where appropriate.
Compare recorded actions with actual orders or enquiries.
Document known gaps caused by consent, blockers or cross-domain journeys.
Review changes after releases rather than assuming tracking survives.

Do not optimise for noisy metrics

A rise in traffic can be harmful if it comes from irrelevant queries. A lower conversion rate can coexist with more qualified leads. Review volume, quality, cost and business outcome together.

Before you publish

Measurement is ready when the business can reconcile important website actions with operational records and explain the main sources of missing or duplicated data.

Typical failure to avoid

Dashboards often count the easiest events rather than the most important outcomes. A button click may look like a conversion even though the form failed or the enquiry was irrelevant. Reconciliation with operational systems is therefore part of measurement, not an optional audit.

Measurement records

Event specification and trigger conditions.
Test cases for success, failure and duplicate actions.
Consent and tag-behaviour documentation.
Monthly reconciliation with CRM, bookings, payments or call records.

A practical next move

List the three website actions that matter most and trace each into the operational system. Remove or downgrade events that cannot be reconciled with an enquiry, booking, order or other real outcome.

Sources and date checked

Search, product and regulatory information was checked against the following primary sources. Interfaces and policies can change, so recheck operational details before acting. Date checked: 21 July 2026.