Skip to content
VERQEN — home

Problem

Your reports may not represent reality.

Most measurement problems are invisible: they do not throw errors, they just quietly report a number that is wrong by 30%. The only way to find them is to perform real actions and follow them through every system.

What you would say

“Our GA4 and CRM numbers do not match and I do not know which to believe.”

Urgency
Usually urgent — it is costing money now
First useful answer
The real-action test usually finds at least one significant problem in the first two days.
Investigation steps
7 steps, in a fixed order

Business impact

What this usually costs

Before the technical detail: this is why it is worth someone's attention.
  • Budget moved between channels on the basis of wrong attribution
  • Paid campaigns optimising towards conversion signals that are duplicated or fake
  • Good pages cut and bad pages kept
  • Agencies and teams judged on numbers nobody validated
  • Board reporting that will not survive scrutiny

Our approach

What we would investigate

In this order, because each step eliminates a category of cause. Skipping to step five is how teams spend a quarter fixing the wrong thing.
  1. Inventory everything that collects data

    Every GA4 property and stream, every GTM tag, trigger and variable, every ads pixel, and every CRM field that is supposed to capture source.

  2. Classify every event and conversion

    Correct, wrong, duplicated or legacy. Most containers we open have tags nobody currently owns.

  3. Check what conversions actually measure

    A conversion defined on a thank-you page view is not the same as a confirmed submission — and behaves completely differently when routing changes.

  4. Perform real actions

    Submit a real form, complete a real purchase or signup, click a phone link, and trace each one through GTM, GA4, the ads platforms and the CRM.

  5. Test both consent paths

    Granted and denied. A consent implementation that drops data instead of modelling it can move reported traffic overnight for a compliance reason nobody connected to the chart.

  6. Check cross-domain and subdomain behaviour

    One journey becoming two sessions inflates traffic, destroys attribution and creates enormous “direct”.

  7. Reconcile against the CRM

    Match front-end conversions against CRM records, quantify the gap, and explain each contributor to it rather than averaging over it.

Differential diagnosis

Likely causes, and what proves each one

Ordered roughly by how often we find them. Every one has a specific piece of evidence that confirms or eliminates it — that is what makes it a diagnosis rather than a guess.
Likely causes of analytics cannot be trusted and the evidence used to confirm each
#Possible causeEvidence that confirms or eliminates it
01Duplicate or double-firing eventsReal action traced through GTM preview and GA4 debug, event count comparison
02Conversions defined on page views instead of confirmed actionsConversion definition review against the real business action
03Consent mode configured to drop rather than model dataGranted versus denied path testing, reported traffic against the banner go-live date
04Cross-domain tracking not configuredSession fragmentation analysis, self-referral and direct traffic share
05Lead source captured on the form but lost before the CRM recordForm payload versus CRM field completeness
06UTM taxonomy applied inconsistentlyChannel grouping accuracy audit, unassigned and (not set) share

The no-guessing rule

If the data does not support a conclusion, we write “we do not have enough evidence to confirm this” and tell you what we would need. A guess never becomes a recommendation.

Outcome

What you end up with

Whether or not you continue with us afterwards.
  • A quantified, explained gap between GA4, ads platforms and the CRM
  • A measurement plan built on the real business definitions of lead and customer
  • Corrected event and conversion set, with dataLayer contracts for developers
  • A GTM cleanup plan in a safe order
  • Working consent, cross-domain and UTM configuration
  • Documentation so the setup survives staff changes

No surprises

What happens if you get in touch

You can stop at any of these five steps.
  1. You send us your website and what is happening

    One form, six fields. No call required to get started.

  2. We review the situation

    We look at your site and the public data before we reply, so the first conversation is useful.

  3. We confirm whether we can help

    If we are not the right fit, we say so — and where we can, we point you somewhere better.

  4. We explain what we would investigate

    Specifically: where we would look first and why, based on what we already saw.

  5. You decide whether to move forward

    No pressure and no follow-up sequence. You have the information; the decision is yours.

Questions

Questions about tracking problems