Diagnostic & Repair

GA4 says one number. CRM says another.

→ DIRECT ANSWER

GA4 and CRM conversion mismatches are almost always architectural — not a "tracking bug." Common causes: client-side tracking lossy under iOS/ad-block, GA4 events not tied to CRM contact IDs, lead-to-opportunity gaps, and timezone/window misalignment between platforms. The fix is server-side tracking + identity stitching + reconciled definitions, not more tags.

Book a Strategy Call Start with a Systems Audit

06CAPABILITY LAYER

Why this symptom is a Intelligence & Analytics problem.

Every revenue team eventually hits the "marketing says X, sales says Y" stand-off. The cause is rarely one platform being wrong; it's that the platforms are measuring different things at different times against different identities. We diagnose the architecture and ship a reconciled measurement layer.

See: Intelligence & Analytics

Symptoms

If most of these are true, you have it.

01GA4 reports 30% more (or fewer) conversions than CRM

02Sales challenges marketing's lead numbers in every QBR

03Two dashboards, two truths, and no source of truth

04Attribution drops between form fill and opportunity

05iOS / ad-block users underrepresented in GA4

06Reports show different numbers in different timezones

Likely causes

Three patterns that produce most cases.

CAUSE · 01

Lossy client-side tracking

iOS 14.5+, ad-blockers, and ITP suppress 20–40% of client-side GA4 events. CRM captures form fill regardless. Result: GA4 < CRM by structural margin.

CAUSE · 02

Identity stitching gaps

GA4 client_id never resolves to CRM contact_id. Same person counted as 3 visitors → 1 lead. Attribution dies at the form fill.

CAUSE · 03

Definition + window misalignment

GA4 "conversion" includes form fills + button clicks; CRM "conversion" requires SQL. Apples to oranges, every report.

Recovery process

A 21-day reconciliation sprint.

01 · DAYS 1–7

Audit + map

Inventory every conversion definition + event in both systems. Map the journey from anonymous → identified → opportunity. Find the gaps.

02 · DAYS 8–16

Server-side + stitch

Deploy server-side GA4 tracking. Wire identity resolution (form fill → contact_id). Standardize windows + timezones.

03 · DAYS 17–21

Reconcile + dashboard

Single reconciled dashboard. Definitions in writing. Hand off to RevOps. Monthly review cadence.

FAQ

Questions we get asked.

01Why does GA4 always undercount vs CRM?+

Client-side tracking is lossy by design — iOS, ad-block, ITP, browser-level privacy. Server-side tracking + identity stitching closes the gap to within 5%.

02Should we trust GA4 or CRM more?+

Neither — alone. CRM has identity but no upstream behavior. GA4 has behavior but no identity. The architecture that joins them is the source of truth.

03How fast can we close the gap?+

21–30 days for the structural fix. Reconciled reporting starts within the first week as we deploy server-side tracking.

04Do we need to replace GA4?+

Almost never. GA4 is fine when properly architected with server-side + identity stitching. Replacement (Mixpanel, Amplitude, etc.) is a larger decision orthogonal to the reconciliation problem.

05What about Google Ads / Meta attribution?+

Same architecture solves it. Server-side conversion APIs (CAPI, Google Enhanced Conversions) ride on the same identity stitching infrastructure.

06Will this break our current reports?+

Reports will look different — more accurate. We provide a reconciliation report explaining the prior gap so leadership trusts the new numbers.

07Is this related to lifecycle / lead scoring?+

Yes — reconciled measurement is the foundation lifecycle scoring rides on. Without it, scoring fires on the wrong signals.

08How is this different from "fix our tracking"?+

"Fix our tracking" usually means add tags. The actual problem is architectural: where data lives, how identities resolve, how definitions align. That's what we ship.

Get it fixed

One number. One source of truth.

A strategy call gets you a clear diagnosis and a 21-day reconciliation plan within 48 hours.