Analytics tracking that records your enquiries

Google Analytics, Search Console and conversion tracking set up properly for businesses across Halifax and West Yorkshire. Calls, forms and WhatsApp taps recorded as events, so the numbers describe enquiries rather than traffic.

What tracking is supposed to record

Most sites have analytics installed and nobody looking at it, usually because it was never set up to record the thing that matters.

Enquiries counted as events

A visit count tells you nothing you can act on. Calls, form submissions and WhatsApp taps are what a business needs counted, so each one is set up as its own conversion event and the traffic figures become context around them rather than the headline.

Configured as well as installed

GA4 dropped onto a site without configuration collects traffic and very little else. Events, filters and internal traffic exclusions get set up properly, so the numbers describe customers rather than you refreshing your own homepage twice a day.

Joined up with Search Console

Analytics tells you what people did once they arrived. Search Console tells you what they typed to get there. Connecting the two is what turns a list of visits into a list of the searches that produce work.

Tested on a real device

An event that was never fired is indistinguishable from a quiet month, and that mistake can run for a year before anybody questions it. Every conversion is triggered on a real phone and confirmed as arriving before the job is called done.

How it gets set up

The first stage decides what is being measured. Get that wrong and the rest is a very tidy record of the wrong number.

  1. Agree what counts as a lead

    Every business measures something different. A phone call is the goal for most trades, a form for most professional services, a basket for a shop. That gets decided first, because everything built afterwards exists to record that one thing.

  2. Install and configure

    GA4 and Search Console set up and verified, consent handling wired in so nothing fires before a visitor has agreed, and internal and spam traffic filtered out so the figures are not mostly your own visits and a bot in another country.

  3. Build the conversion events

    Each action worth counting gets its own event: phone taps, form submissions, WhatsApp clicks, quote requests. Where useful they are given a value, so the reporting can separate a boiler replacement enquiry from someone asking about a washer.

  4. Verify and document

    Every event is fired on a real device and checked as arriving. You get a short written note of what is tracked and where it lives, so the setup is not something only one person understands.

What is included

Set up once and yours to keep, with no monthly fee attached to it.

  • GA4 property setup and configuration
  • Search Console setup and verification
  • Conversion events for calls, forms and WhatsApp
  • Consent handling wired to tracking
  • Internal and spam traffic filtering
  • Event testing on real devices
  • Written note of what is tracked and where
  • Handover walkthrough

Questions we get asked

Mostly from people who already have analytics and have never opened it.

Is this not included when you build a site?
The basics are. Every build ships with analytics installed and Search Console connected, and for plenty of businesses that is genuinely enough. This is for sites that already exist and were never set up properly, or where the enquiry side needs tracking rather than just the traffic. What comes as standard is listed on pricing.
I already have Google Analytics. Is it worth redoing?
Worth auditing, at least. The usual state is GA4 installed some years ago, recording pageviews, with no conversion events, no filtering, and internal visits inflating every figure on the screen. That data is not so much wrong as unable to answer the only question worth asking, which is where the enquiries actually come from.
What is the difference between this and Data Insights?
This page is collection: making sure the right things are recorded, correctly. Data Insights is interpretation: reading what has been recorded and deciding what to change. This one has to come first, because analysis of data that was never set up properly is just a confident version of guessing.
Do I need a cookie banner?
If you are tracking visitors in the UK or EU, consent has to come before the tracking rather than alongside it, and the setup wires the banner to the analytics so nothing fires until someone agrees. What the banner needs to say is a legal question rather than a technical one, and worth putting to someone qualified if you are at all unsure.
How much does it cost?
Quoted per site, because it depends entirely on what is already there. A site with nothing installed is a different job from one carrying a misconfigured GA4 and three conflicting tags left behind by previous providers. Send the address over and you will have a fixed price before anything starts.