Why GA4 and Your CRM Report Different Lead Numbers

The short answer: they are not measuring the same thing

A CRM is a list of people and companies. GA4 is a record of things that happened in web browsers. When both are asked “how many leads did we get?”, each answers a slightly different question, and neither is lying.

The useful question is not “which one is right?” but “is the gap explained, and is it stable?” A gap you understand, that stays roughly the same size month to month, is a fact of life. A gap that nobody can explain, or that suddenly widens, is a symptom: something broke, something changed, or the two systems were never counting the same thing to begin with.

This article is about diagnosing that discrepancy. If the CRM itself does not yet record where leads came from, start with how to connect marketing reporting to sales outcomes. If GA4 is not yet configured properly, the GA4 setup and audit checklist comes first. Reconciliation only makes sense once both systems are, in principle, set up to count leads.

Cause one: different definitions of a lead

The most common cause is also the least technical. The two systems were never told to count the same thing.

• GA4 counts events; the CRM counts records. If one person submits the quote form twice, GA4 records two events. The CRM, matching on email address, may update one contact and show one lead.
• GA4 may count actions the CRM never sees. A key event set on phone number clicks, brochure downloads or newsletter signups inflates the GA4 “leads” figure with things nobody in sales would call a lead. This is one reason to be strict about what counts as a conversion.
• The CRM counts leads GA4 cannot see. Phone calls, direct emails, walk-ins, referrals, trade show contacts and sales prospecting all create CRM records with no website event behind them.
• Spam and tests. Bot submissions and staff test entries may fire a GA4 event and be deleted or filtered in the CRM, or the reverse.
• Existing customers. Clients who use the contact form to ask about an invoice are “leads” to GA4 and support tickets to the CRM, if anyone bothers to reclassify them.
• Counting method. GA4 can count a key event once per event or once per session. A setting nobody remembers choosing can change the figure.

Before investigating anything technical, write down in one sentence what each system is counting. Frequently the gap explains itself at that point.

Cause two: consent and blocking

GA4 only sees what the browser is allowed to send it. A visitor who declines analytics cookies, uses an ad blocker or a privacy-focused browser, or closes the tab before the confirmation loads may submit a perfectly good inquiry that reaches your inbox and your CRM without GA4 ever recording it.

Depending on how Google consent mode is configured, GA4 may fill some of that gap with modelled estimates, or may not. Either way, GA4’s figure for website leads will generally sit below the number of website-originated records in the CRM, and the size of the gap depends on your audience. A B2B audience on managed work laptops may behave very differently from tourism visitors on their phones.

This part of the gap is not an error, and it should not be “fixed” by working around visitors’ choices. Our article on client-side vs server-side conversion tracking covers what can legitimately be recovered from blocking, and what cannot.

Cause three: identity

A CRM identifies people, usually by email address, and often groups them under companies. GA4 identifies browsers and devices, unless you send it your own user identifiers, which most business websites do not and many should not.

That creates a few predictable mismatches:

• The same person inquiring from a work laptop and later from a phone is two users in GA4 and one contact in the CRM.
• Two colleagues from the same company inquiring separately are two contacts, possibly one account, and one “lead” or two depending on how sales counts.
• A returning contact who inquires again may be merged into an existing record and not counted as new at all, while GA4 cheerfully counts another key event.

Decide whether your business counts new contacts, new inquiries or new opportunities, and make sure the CRM report you compare against counts the same thing. Most organizations want inquiries for marketing reporting and opportunities for revenue reporting. Those are different reports.

Cause four: attribution and timing

Even when the totals agree, the breakdown by channel almost never does.

• Different attribution rules. GA4 assigns credit for a key event according to its attribution settings and the session in which it happened. The CRM usually stores whatever source was captured in hidden form fields, which might be the first visit, the last visit, or whatever a sales rep selected from a drop-down.
• Missing source data. If UTM parameters are lost on a redirect, or hidden fields are not populated on one form, the CRM records “website” or nothing, while GA4 still has a channel.
• Different dates. GA4 records when the event happened. The CRM report may filter on when the record was created, when it was qualified or when it was last modified. A lead imported on the second of the month for an inquiry on the thirtieth lands in different months.
• Time zones. A GA4 property set to Eastern time and a CRM set to Atlantic time disagree about which day late-evening inquiries belong to.
• Processing delay. GA4 data for recent days can still be updating. Comparing yesterday’s numbers is asking for confusion.

A reconciliation process that settles it

Arguments about which number is right end when someone does the reconciliation once, carefully. It is tedious and it is worth it.

1. Pick one complete month that ended at least a week ago, and one primary conversion, usually the main inquiry form.
2. Export three lists: GA4 key events for that form with timestamps, submissions from the form tool itself, and CRM records created from that form.
3. Match them by date and time, within a few minutes. The form tool is usually the referee, because it records every submission regardless of consent.
4. Sort every unmatched item into a cause: declined consent or blocked, duplicate submission, spam, test, existing customer, merged contact, date boundary, broken source capture, or unknown.
5. Fix the errors (duplicates counted, tests not excluded, hidden fields empty, wrong time zone) and accept the rest as known gaps.
6. Write down the expected gap and its main causes, in the measurement plan, so the next person does not start from zero.

An illustrative example. Say a property management company with offices in Moncton and Halifax finds GA4 well above the CRM one month. The reconciliation shows that phone clicks had been marked as a key event, that a spam wave hit the contact form in the third week, and that the leasing team deletes rather than disqualifies junk records. GA4 was counting three different things as leads and the CRM was quietly hiding the evidence. The fixes are a configuration change, a spam filter and a rule that junk is marked as junk, not deleted. Nothing about the marketing changed; the conversation about it did.

Repeat the reconciliation after any significant change: a new form tool, a new consent banner, a CRM migration or a website rebuild. Between those, a quick monthly comparison of totals is enough to catch drift. If the gap jumps suddenly, treat it as you would any sudden change and work through how to diagnose a drop in website conversions, starting with measurement.

Which number leadership should see

Give each system the job it is good at.

• The CRM is the source of truth for lead volume, quality and outcomes. It sees every channel, it deduplicates people and it knows what happened next. This is the number on the executive dashboard.
• GA4 is the source of truth for website behaviour. Which pages and channels drive inquiries relative to each other, where visitors drop out of a form, how mobile compares to desktop. Its absolute totals matter less than its comparisons.
• Ad platforms are the source of truth for spend, and an optimistic one for conversions. Their numbers will disagree with both of the others, by design.

Put the known gap on the report in plain language: “GA4 typically records fewer website inquiries than the CRM, mainly because of consent choices and blocked tracking.” Leadership trusts numbers more, not less, when the caveats are stated up front.

Reconciliation is one of the first things we do in an analytics and measurement engagement, because until marketing, sales and leadership agree on why the numbers differ, every other report gets argued about instead of used.