Conversion tracking in GA4: why your analytics are quietly lying to you

Google Analytics 4 does not track your conversions out of the box. Here is why most businesses make spend decisions on wrong numbers, and what proper conversion tracking actually looks like.

Open Google Analytics 4 on most small business websites and you will see traffic, sessions, bounce rates and a tidy line going up and to the right. It looks healthy. The problem is that almost none of it tells you what you actually need to know, which is how many people did the thing that makes you money. That is conversion tracking, and GA4 does not do it for you.

This catches out far more businesses than you would think. GA4 counts visits perfectly well. But a visit is not a lead. If your conversion tracking is wrong, broken or simply never set up, every report you read is fiction with good production values. You then spend real money on the strength of it.

GA4 does not track your conversions by default

This is the part nobody tells you. When you paste the GA4 tag onto your site, Google starts collecting page views and a handful of automatic events. It does not know what a conversion means to your business. A form submission, a phone tap, a quote request, a booking: GA4 has no idea any of those matter until you tell it.

You have to define your conversions. In GA4 that means creating the events that represent a lead, then marking them as key events so they show up as conversions. Skip that step and your conversion count is either zero or wrong, and the dashboards built on top of it inherit the same fault.

The common failures we find

When we audit a new client's setup, the same handful of problems come up again and again. Most sites have at least two of these live right now.

No conversion events defined

The site collects traffic but never marks anything as a key event. GA4 reports plenty of numbers and not one of them is a lead.

Form submissions not tracked

The contact form works, the email arrives, but GA4 records nothing. The single most important action on the site is invisible to your analytics.

Phone clicks not tracked

For a lot of UK businesses the phone is the main way leads come in. A tap on a mobile number is a conversion, and almost nobody tracks it. So the channel that drives the most business looks like it does nothing.

Consent banners blocking the data

A cookie banner set to deny analytics until someone clicks accept will quietly drop a large share of your visitors from the numbers. The fix is consent mode done properly, not a banner bolted on that breaks the data underneath it.

Thank-you-page-only tracking

Counting conversions by landings on a thank-you page sounds reasonable. It misses every form that does not redirect, every booking widget in an iframe, and every visitor who closes the tab a second early. It undercounts, and you never know by how much.

Last-click attribution hiding what works

By default many reports give all the credit to the last click before the conversion. So the blog post, the paid ad or the search result that started the journey gets nothing, and you cut the very thing that was feeding your pipeline.

Why this matters more than it sounds

This is not a tidiness problem. It is a money problem. You decide what to spend more on, what to cut and what is working entirely from these numbers. If the numbers are wrong, the decisions are wrong in the same direction.

We see it constantly. A channel gets killed because it "does not convert", when really its conversions were never tracked. Budget pours into a campaign that looks brilliant on last-click and is actually riding on work done elsewhere. The dashboard says one thing and the bank account says another, and nobody can explain the gap. Proper tracking and reporting is what closes it.

What good conversion tracking looks like

Done properly it is not complicated, it is just deliberate. Here is the setup we put in place.

• Defined conversion events: every action that means a lead, set up as a key event in GA4. Form submits, phone taps, booking requests, quote downloads. Real actions, not page views.
• Google Tag Manager: tags managed in one place rather than hard-coded across the site, so tracking can change without a developer touching the build each time.
• Google Search Console connected: so you can see the actual search queries bringing people in, joined up with what they do once they arrive.
• Consent handled correctly: a cookie banner with consent mode configured so you stay compliant and still keep usable data, instead of choosing between the two.
• Server-side tagging where it earns its place: for sites where ad blockers and browser limits are eating a meaningful slice of the data, moving tagging server-side recovers it. Not every site needs this, and we will tell you if yours does not.
• A clean reporting layer: a single Looker Studio dashboard that shows leads by source in plain language, so you are not digging through GA4 to answer a simple question.

That last point matters as much as the tracking itself. Once the data is right, it needs to be readable by the person spending the money. We cover the reporting layer in detail in our guide to building a marketing dashboard in Looker Studio.

How to check your own setup

You do not need an agency to spot the obvious gaps. Open GA4, go to your key events, and ask three questions. Is a form submission listed? Is a phone click listed? Do the conversion numbers roughly match the leads you actually got last month? If the answer to any of those is no, your tracking has a hole in it.

If you would rather have someone who does this all day look at it, that is what we are for. If you are weighing up help, our rundown of the best analytics agencies in the UK is an honest place to start, including where we fit and where we do not.

FAQ