The question analytics should answer
Not "how many visitors did we get". That number is nearly useless to a small business. The question is: which pages, and which sources, produce the enquiries, calls and bookings that become customers? Answer that and you know what to write more of, where to spend on ads, and which pages are decorative.
Most small business analytics setups cannot answer it, because they count visits and nothing else. Here is how to make them count what matters.
Step one: decide what a conversion is
List every action on the site that means a potential customer has raised a hand:
- Submitting the contact form.
- Clicking the phone number (on a phone, this is a call).
- Clicking the email address.
- Clicking Book Now, or completing a booking if the booking tool is embedded.
- Clicking a WhatsApp or chat link.
- Downloading a price list, if you have one.
Each is a conversion event. Give each a name you will recognise in a report: generate_lead, contact_click, booking_click. Google Analytics 4 has recommended names for some; use them where they fit so its reports work.
Step two: send the events
Each action needs to fire an event when it happens. Three common ways:
In the site's code. The cleanest. The form's success handler sends generate_lead; the phone link's click handler sends contact_click with a parameter saying phone. A developer does this in an hour, and it survives theme changes.
Google Tag Manager. A trigger on clicks to links containing tel: fires a tag that sends the event. Good when you cannot change the code, and it is what marketing teams tend to use. It adds a script to the page, so keep it lean.
The form or booking tool's own integration. Many form plugins and booking widgets can send a GA4 event on completion. Check the settings before writing anything.
Whichever you use, test it: open GA4's Realtime report, perform the action on your own site, and watch the event appear. If it does not, nothing downstream will work.
Step three: mark them as key events
In GA4, an event is just a count until you mark it as a key event (previously "conversion"). Admin, Events, toggle the switch beside generate_lead and the others. Now they appear in the conversion columns of every report, and Google Ads can optimise towards them if you import them.
Step four: read the two reports that matter
Pages by conversions. Reports, Engagement, Pages and screens, with the key events column. Sort by conversions. This tells you which pages people were on when they enquired. Usually the contact page is top, which is uninformative; look at the landing pages instead.
Landing pages by conversions. Reports, Engagement, Landing page. This is the page the visitor arrived on, from search or an ad or a link. Sorted by conversions, it tells you which pages bring in the people who go on to enquire. A blog post that lands fifty visitors a month and produces three enquiries is worth more than a page that lands five hundred and produces none. This is the report that changes what you write.
Source by conversions. Reports, Acquisition, Traffic acquisition. Google organic, Google Business Profile, paid, social, direct, referral. Which sources produce enquiries, not just visits. This is the report that changes where you spend.
Step five: close the loop on quality
Analytics knows an enquiry happened. It does not know whether it became a customer. For that, add one field to your enquiry handling: where did this lead come from? The form can include a hidden field capturing the landing page and source (GA4's client ID, or simple UTM parameters passed through). Your CRM or spreadsheet then has, for each closed customer, the page and source that produced them.
Even done roughly, by asking "how did you find us" on the first call and noting the answer, this is the number that matters most, and it is the one no analytics tool gives you on its own.
Phone calls, properly
For a business where most enquiries are calls, the tel: click event undercounts: desktop visitors read the number and dial it. Two upgrades: a call-tracking service that shows a unique number to website visitors and reports the calls back to analytics; or, more simply, a dedicated number on the website that differs from the one on your van and your Google listing, so the receptionist knows a call from the website when it rings.
What to ignore
Bounce rate, average session duration, pages per session, "engagement rate". They describe behaviour, not outcomes, and they are easy to improve in ways that do not produce a single customer. Look at conversions by landing page and by source, monthly, and let the rest be.
Where this sits
Every website we build ships with the conversion events wired in code, marked as key events, and tested before launch, because a site that produces enquiries you cannot attribute is a site you cannot improve. The monthly care plan report includes the landing-page and source tables, so the owner sees where the customers came from without opening analytics at all.