Conversions do not reconcile with the CRM or store
A shared definition, reference system or explanation of the difference is missing.
GA4 audit · GTM · e-commerce
I review the complete measurement chain—from the dataLayer and GTM to GA4, e-commerce, Consent Mode and advertising integrations. I show where the data distorts decisions and what should be fixed first.
I do not promise a one-to-one match between GA4 and a CRM or store. I separate implementation errors from differences caused by definitions, consent, delays and the limitations of the platform.
When an audit is useful
An audit is the right first step when measurement is already running, but the results are disputed or nobody can explain the source of a mismatch.
A shared definition, reference system or explanation of the difference is missing.
purchase, transaction_id, item data and refunds do not form a consistent view of sales.
Legacy tags, DOM dependencies and unknown triggers make every change risky.
Self-referrals, payment gateways, subdomains or incorrect UTMs change session and conversion sources.
It is unclear which tags run for each consent state and when they are triggered.
Marketing, sales and finance use different definitions of the same conversion.
Audit outcome
Every material issue is described with evidence, impact, a recommendation and an acceptance check. The audit can enter a backlog instead of becoming a presentation that is filed away.
Issue, environment, reproduction steps, evidence and area of ownership.
Comparison of critical events and values with an agreed reference system.
Critical, important and optimisation items, with the consequence for decisions.
Sequence, dependencies, required roles and indicative effort.
Property, streams, domains, filters, referral exclusions and systems of record.
Names, parameters, trigger conditions, duplicates and conversion definitions.
Funnel, item data, transaction_id, currencies, values and edge cases.
Tags, triggers, CMP, Consent Mode, Google Ads and technical dependencies.
Completeness, consistency, delays and comparison with the store, CRM or backend.
An audit does not automatically include rebuilding measurement. When recommendations require changes, the implementation scope is agreed only after the causes and dependencies are known.
Explore GA4 implementationProcess
We establish the decisions that depend on the data, symptoms, sites, integrations and reference systems.
I review the configuration, container, dataLayer and data flow, then reproduce the critical scenarios.
I test duplicates, omissions, consent and domains, and compare critical results with the reference system.
I order recommendations by impact, dependency and effort, then review them with the people who will implement the changes.
A tangible result
This is an illustrative structure, not data from a specific client. The report separates fact, interpretation and recommendation.
Choosing the first step
When data exists, but it is unclear what works, why numbers differ and what should be fixed first.
Review the scopeWhen KPIs, events, parameters, the dataLayer and ownership must be agreed before configuration.
Explore the planWhen specifications and issues are known, and configuration, changes, QA and documentation are required.
Explore implementationWhen critical data requires ongoing controls, alerts and a response process after releases.
Explore monitoringConditions for a useful audit
Honest limitations
I document confidence levels and the limits of each conclusion instead of hiding them behind a promise of “100% accurate data”.
One accountable consultant
I lead the audit personally—from questions about decisions and systems of record, through GA4 and GTM testing, to the discussion with the people who will implement the fixes. Priority therefore reflects more than the number of errors.
The figures cover the wider analytics and data practice, not GA4 audits alone.
Before we talk
It depends on the number of sites, containers, integrations, consent variants and the availability of reference data. After a short qualification, I propose a scope and schedule instead of applying one duration to every environment.
Usually, agreed access to GA4 and GTM, the ability to test the site and comparative data from a CRM or order system are enough. Google Ads, the CMP, BigQuery and other systems are included only when they belong to the scope.
I do not guarantee a one-to-one match. The goal is to understand the differences, remove implementation errors and agree tolerances for critical metrics.
The core deliverable is diagnosis, priorities and a repair plan. I can estimate implementation after the audit, when the causes, development dependencies and acceptance criteria are known.
A findings register with evidence, a data quality and reconciliation summary, priorities, recommendations, a roadmap and a review meeting. The format is designed to move directly into a backlog.
Pricing depends on the number of sites, containers, e-commerce scenarios, integrations, reference systems and the required testing depth. After qualification, I identify the core scope and optional elements.
First step
I will respond with questions about the site, reference system, GTM, consent and the people needed for the audit. If an audit is not the right first step, I will say so before preparing an estimate.
Before ordering an audit