Cybrial
Independent design. Ongoing growth.Manchester · Working everywhere

Guide · Measurement

Setting Up GA4 and Conversion Tracking Properly

By Measured 4 September 2026

Almost every business I start with is making decisions on numbers that are wrong. Not slightly wrong — wrong in a direction and by an amount nobody has quantified. Here is where it goes wrong and how it is fixed.

The short answer

Conversion tracking is set up by deciding what counts as a conversion, firing an event for every route a customer can take — form, phone tap, chat, purchase — feeding those same events to Google Ads and Meta so the channels agree, and keeping a cookieless page-view count alongside GA4 as an honest denominator. GA4 undercounts traffic wherever a consent banner is used: on one e-commerce site I run, Google Merchant Centre recorded 337 Shopping clicks in a 28-day window while GA4 recorded 54 organic Shopping sessions for the same period.

The numbers on this page

Where each of these came from.

Nothing here is an industry average or a vendor's marketing figure. Each one names the tool it was read from and the date it was read.

337 vs 54

Shopping clicks vs GA4 sessions

same 28-day window, same site — Merchant Centre counts before consent, GA4 after

Source: Merchant Centre and GA4, one e-commerce site, 28-day window

288

GA4 sessions, all channels

consented only — the floor, not the total

Source: GA4, same 28-day window

24,054

Search Console queries, Beds.ie

unaffected by consent, which is why it is the reliable source

Source: Google Search Console, August 2026

Your analytics numbers are lower than reality

Start here, because everything downstream depends on it and almost nobody has been told.

UK sites use a consent banner. Configured correctly, analytics storage is denied by default, and a visitor only becomes a session once they accept. Everyone who declines, ignores the banner, or leaves before deciding is invisible to GA4. They still visited. They still bought or did not buy. They are simply not in the denominator.

Here is that gap measured. On an e-commerce site I run, over one 28-day window: Google Merchant Centre reported 337 Shopping clicks, while GA4 reported 54 Organic Shopping sessions and 288 sessions across all channels combined. Merchant Centre counts clicks at Google's end, before any banner exists. GA4 counts sessions after consent. Both are correct measurements of different things, and the difference is enormous.

The fix is not to remove the banner. It is to keep a second, cookieless count of page views server-side — no personal data, no cookie, no consent required — and use that as the denominator for anything you are going to make a decision on. GA4 then does what it is good at: behaviour and journeys among the people who did consent.

Deciding what counts as a conversion

Before any code, one conversation: what does a good outcome look like for this business? The wrong answers here cost more than any technical error.

  • For a service business: an enquiry, by any route. Form, phone tap, WhatsApp, chat, email link. All of them, or the number is fiction.
  • For e-commerce: a purchase, with its value. Add-to-basket and checkout steps are useful diagnostics but are not the outcome.
  • For a business selling something considered and expensive: often a partial step — a brochure download, a quote request, a booked call.

The most common error is counting a page view as a conversion. A thank-you page view is a proxy for a submission, not the submission — it is triggered by refreshes, by bookmarks, and by anyone who lands on it directly. It is also the easiest thing to set up, which is exactly why it is everywhere.

The second most common error, in trade and service businesses specifically, is counting only form fills. If most of your customers ring, an account optimised on form submissions is optimising toward a minority of your business — and Google Ads will faithfully spend your budget chasing the wrong people.

How it is actually set up on a new site

Six steps, in this order, and the order matters because each one depends on the last being right.

  1. Consent first. The banner, configured so that analytics and advertising storage default to denied and are granted only on acceptance. Doing this after the tags are live means every number from the first month is a different measurement from every number after it.
  2. GA4 with real events, not just page views. One event per enquiry route: form submitted, phone number tapped, chat opened, email link clicked. Named consistently, so that six months later a report can be built without archaeology.
  3. A cookieless page-view count alongside it. Server-side, no personal data, no cookie. This is the honest denominator and the reason any conversion rate quoted afterwards means something.
  4. Search Console connected. Free, unaffected by consent, and the only source of truth for what people searched before they arrived. Anything that matters gets stored in a database the client can query rather than left to expire at sixteen months.
  5. Google Ads and Meta conversions fed from the same events. Not separately defined in each platform — the same events, so that the channels are at least measuring the same thing when they disagree about who deserves the credit.
  6. Reconcile against reality. Count last month's enquiries in the inbox and the phone log. Compare with what the tracking says. If they differ, the tracking is wrong, and it is wrong now rather than in three months when a decision is made on it.

That last step is the one that separates working tracking from tracking that merely exists. Almost every setup I inherit has never been reconciled with an actual count of enquiries, and a surprising number of them are out by more than half.

Is server-side tracking worth it?

Sometimes, and it is oversold. Server-side tracking sends events from your own server rather than from the visitor's browser, which makes them more reliable — browser extensions, ad blockers and tracking prevention all remove browser-side events.

When it is genuinely worth the complexity:

  • You spend enough on ads that a 10–20% improvement in signal quality is worth real money.
  • You sell to a technical audience, where ad-blocker use is high enough to distort the picture materially.
  • You need a durable server-side record of conversions independent of any platform, for reconciliation.

When it is not: a local business spending £500 a month on ads. The setup and ongoing maintenance will cost more than the improvement is worth, and the same effort spent on counting phone calls properly would return several times as much. A simple cookieless page-view endpoint gets you most of the honest-denominator benefit for a fraction of the work.

Reading the numbers without fooling yourself

  1. Always name the source and the window. "288 sessions" is meaningless; "288 GA4 sessions, all channels, 28 days to 4 September, consented only" is a fact.
  2. Never blend a consented number with an unconsented one in the same ratio. Merchant Centre clicks over GA4 sessions is not a conversion rate, it is a category error.
  3. Compare full calendar months against full calendar months. Partial periods and rolling windows produce changes that are entirely artefacts of the dates.
  4. Exclude yourself. Your own visits, your developer's, and your office. It sounds trivial until you notice a small site where internal traffic is a fifth of everything.
  5. Expect the channels to disagree. Google Ads, Meta and GA4 each attribute by different rules and will each claim the same sale. The reconciliation is a judgement, and anyone presenting a single blended number without saying so is hiding the judgement rather than making it.

Every case study on this website carries the tool it was read from and the date, for exactly these reasons. It is not decoration; it is what makes the figures checkable — and a figure nobody can check is a claim, not a measurement.

Sources

Everything this page relies on.

  1. One e-commerce site run by the founder, 28-day window: Google Merchant Centre 337 Shopping clicks; GA4 54 Organic Shopping sessions; GA4 288 sessions across all channels. The site is deliberately not named; the measurement is first-hand.

  2. Beds.ie Google Search Console, August 2026: 24,054 distinct queries. Search Console data is unaffected by consent banners, which is why it is the reliable source for search performance.

  3. Search demand and click-price data: DataForSEO (Google Ads data, United Kingdom), read 4–5 September 2026. The specific phrases and figures are Cybrial’s own research and are not published.

Common questions

Questions people actually search for.

Why are my GA4 numbers lower than my ad platform's?

Because they count at different points. Ad platforms count clicks at their end, before any consent banner exists. GA4 counts sessions after the visitor accepts cookies. On one site I run, Merchant Centre reported 337 Shopping clicks in a 28-day window against 54 GA4 organic Shopping sessions for the same period. Both figures are correct measurements of different things.

Does a cookie banner affect Google Analytics?

Substantially. With consent mode configured properly, analytics storage defaults to denied, so a visitor only becomes a session once they accept. Everyone who declines or ignores the banner is missing from your traffic figures — which means your conversion rate is overstated, often by several multiples.

What should I use as my traffic denominator?

A cookieless server-side page-view count, kept alongside GA4. It requires no consent because it stores no personal data and sets no cookie, so it counts everybody. Use it for anything you will make a decision on, and use GA4 for behaviour among the people who did consent.

Do I need Google Tag Manager?

Not necessarily. It is useful when several people need to add and change tags without touching the site, and on a small site built properly it often adds a layer of complexity for no gain. What matters is that events fire reliably and are named consistently, not which tool fires them.

Is server-side tracking worth it?

Only above a certain ad spend, or with a technical audience where ad blocking distorts the picture. For a local business spending a few hundred a month, the setup and maintenance cost more than the improvement is worth, and counting phone calls properly would return more.

How do I track phone calls from my website?

At minimum, fire an event when someone taps the number on a mobile device — that is a few lines and it is the enquiry route most often missed entirely. Call tracking numbers give you more detail and cost more; whether they are worth it depends on how much of your business arrives by phone.

Why does every channel claim the same sale?

Because each platform attributes by its own rules and none of them can see the others. Feeding all channels from the same event definitions at least makes them measure the same action. The reconciliation is a judgement, and a report that presents one blended number without saying so is hiding that judgement rather than making it.

Do your numbers survive being checked?

Send me your site and I will tell you what is actually being counted, what is being missed, and what your real conversion rate looks like against an honest denominator. It is usually the most uncomfortable and most useful hour of the engagement.