Analytics you can trust again.

We audit Google Analytics, Tag Manager and consent on your site, fix what is miscounting, and show you why your numbers disagree with each other.

Rising bars of light with a trend line arcing over them, for Analytics

What it is

One lead, four different counts.

Your CRM says 40 leads. Google Analytics says 47, or 27. Google Ads says 31. Each number is produced by a different system with its own rules, and most businesses end up trusting none of them.

As your Google Analytics consultant we do the unglamorous part: read the tag setup, the site’s code and the live data side by side, find where they drifted apart, and fix it. You keep every account. We work in yours.

Why numbers disagree

One month, four numbers.

The same leads, counted four ways. Select a count to see why it is off. None of this is unusual: it is what a normal setup looks like before anyone checks it.

Leads in one month (sample data)

7 too many

GA4, as we found it

Why it differs

More leads than exist. Double counting is hiding the visitors who refused consent, so the total looks plausible while both errors are still in it.

Usual causes

  • No lead id, so a refresh or a double click counts twice.
  • A tag that fires again when consent is given.
  • A thank-you page view and a form event both counted as a lead.

Sample figures to show the pattern, not a client’s data. The causes are the ones we found in our own audits and the ones Google documents.

Sources: Google, consent mode (opens in a new tab), Google, behavioural modelling (opens in a new tab), Google, attribution (opens in a new tab), Google, key events and conversions (opens in a new tab)

What we find

Patterns from five websites we manage.

We audited the tracking on five websites we manage. The page-level foundation was right on all five. The event layer was not right on any of them. These are the patterns, without names.

One action, many names

The same lead had four different names across the sites, and on one site no name at all. Every setup becomes a one-off and nothing can be compared.

Tags that fire twice

The main Google tag fired again when a visitor gave consent, sending a second page view for the same page.

A form that reports nothing

The site sent one event name and the tag setup listened for another. The form worked. Analytics recorded zero.

Leads counted twice

No site passed a lead id, so a refresh, a double submit or a retry could count the same lead again.

Clicks nobody tracked

Phone and WhatsApp buttons in a sticky mobile footer sent nothing at all.

Leftovers from a copied setup

A setup cloned from another site still carried the old site’s tags, sending clicks to the wrong property.

What we look at

Consent, a second count and conversion.

Conversion optimisation

Measure first. Then change. Test where the traffic allows.

A test on a conversion event that counts twice measures nothing, so conversion work starts with the measurement. Then we review the pages for what stops people: a form that fails, a button nobody sees on a phone, a path that ends nowhere. Those get fixed without a test.

For sites with enough traffic we run A/B tests, built into the site’s own code. Enough is more than most people expect. By a common rule of thumb, detecting a 10% relative lift on a 5% conversion rate takes about 30,000 visitors per variant. We set the sample size before the test starts and do not stop early: checking a running test again and again can turn a 5% false-positive rate into 26%.

  • No uplift promised in advance
  • Sample size fixed before the test
  • Smaller sites: fix what is broken, compare honestly

Sources: Google, consent mode (opens in a new tab), Google, EU user consent policy (opens in a new tab), Autoriteit Persoonsgegevens, cookies (opens in a new tab), ICO, exceptions to consent (opens in a new tab), CNIL, audience measurement (opens in a new tab), Evan Miller, How Not To Run an A/B Test (opens in a new tab), Optimizely, how long to run an experiment (opens in a new tab)

Consent mode

Basic or advanced: what each one costs.

Question
When do Google’s tags load?
Basic mode
Only after the visitor chooses.
Advanced mode
When the page opens.
Question
What is sent after a refusal?
Basic mode
Nothing, not even the consent status.
Advanced mode
Measurements without cookies.
Question
Can Google model the missing visitors?
Basic mode
No: behavioural modelling in GA4 needs the advanced setup.
Advanced mode
Yes, above the traffic thresholds.
Question
Who should decide?
Basic mode
You, with your privacy adviser.
Advanced mode
You, with your privacy adviser.

As described in Google’s documentation on 15 November 2026. This is general information, not legal advice.

Sources: Google, consent mode (opens in a new tab), Google, behavioural modelling (opens in a new tab)

What we set up

Four things, in your accounts.

GA4 and Tag Manager
One event vocabulary for the whole site, built on GA4’s own recommended event names, with a lead only counted after the server confirms it.
Consent Mode v2
The default set before any tag loads, one update on a real choice, and both paths tested on every page type.
Server-side tagging
Tags that run on a server you control instead of in the visitor’s browser. Google lists privacy controls, performance and data quality as the reasons to do it. Not every site needs it.
Dashboards and reports
A dashboard where leads are counted on the server, and a monthly report that reads the same data.

Sources: Google, server-side tagging (opens in a new tab), Google, why server-side tagging (opens in a new tab)

How we work

Audit, plan, fix, verify.

  1. 01 · Audit

    Read, change nothing

    Three sources side by side: the tag setup, the site’s code and the live data. The audit is read-only.

  2. 02 · Plan

    Rank the findings

    What loses data today comes first. You get each finding with its evidence and the fix.

  3. 03 · Fix

    Repair the event layer

    One vocabulary, one lead id, tags that fire once. In your own accounts, never in ours.

  4. 04 · Verify

    Check against the server

    We compare what analytics now reports with the server count, with consent given and refused.

Tracking audit

From €500

Fixed and agreed before we start. The fixes are quoted from the findings, because their size depends on what the audit turns up. For UK clients we quote in pounds on request. See all pricing

FAQ

Questions about Analytics

Reviewed by Chris de Gruijter,

Find out which number is right.

Start with the free AI Scan, or ask for a tracking audit straight away.