Why HubSpot and GA4 numbers don't match is not a mystery once you stop treating them like two copies of the same report. GA4 explains website behavior. HubSpot explains people, lifecycle stages, deals, and revenue. Reconciliation hell starts when a monthly report build pretends those are the same thing.
Why HubSpot and GA4 numbers don't match
GA4 is built around web events. HubSpot is built around CRM records. A form submit can be a GA4 event, a HubSpot contact, a lifecycle-stage change, and later a deal. Those records may have different timestamps, filters, ownership rules, and attribution windows. Nobody is lying, but the report still needs one number a team can defend.
| Mismatch | GA4 view | HubSpot view | Report rule |
|---|---|---|---|
| Lead count | Events or conversions | Contacts or submissions | Report qualified contacts from HubSpot |
| Traffic source | Session or user source | Original or latest source | Name which source field is used |
| Revenue | Imported or modeled events | Deals and closed-won amount | Use HubSpot for pipeline and revenue |
| Timing | Event timestamp | Contact/deal timestamp | Convert to one report time zone |
Start with the reporting question
The first question is not, "Which platform is right?" It is, "What decision is this report supposed to support?" If the question is traffic quality, GA4 leads. If the question is pipeline quality, HubSpot leads. If the question is what changed and why, the report needs both systems joined by a definition everyone can see.
Reconcile before the meeting
- Name the metric as traffic, conversion, contact, opportunity, pipeline, or revenue.
- Write the exact GA4 event name and the exact HubSpot object or property used.
- Lock date range, time zone, attribution window, and filters before exporting anything.
- Document duplicates, test records, spam, and internal traffic exclusions.
- Explain every expected gap in the report, not in a follow-up Slack thread.
Where HubSpot should win
HubSpot should be the source of truth for owned contact and revenue lifecycle: contacts, companies, deals, stages, owners, pipeline, and closed-won revenue. GA4 can help explain the web journey that created or influenced those records, but it should not replace the CRM for pipeline reporting.
Where GA4 should win
GA4 should be the source of truth for website behavior: landing pages, sessions, engagement, events, and traffic movement. It is also useful for diagnosing whether a campaign changed volume or quality before that change appears in HubSpot. The problem comes when a team uses GA4 to defend sales pipeline or HubSpot to explain every website session.
FAQ
Why don't HubSpot and GA4 ever show the same lead total?
HubSpot and GA4 count different things. GA4 starts with website events and attribution rules, while HubSpot starts with contacts, lifecycle stages, forms, deals, and CRM ownership.
Should HubSpot or GA4 be the source of truth?
Use GA4 for traffic and website behavior. Use HubSpot for contact, pipeline, lifecycle, and revenue reporting. Use a reconciliation layer when a single executive number needs both.
How much mismatch is normal between HubSpot and GA4?
Small mismatches are normal because attribution windows, sessions, contact deduplication, filters, and time zones differ. A large or sudden mismatch means the workflow needs review.
Can Maven reconcile HubSpot and GA4?
Yes. Maven maps the source fields, attribution windows, exclusions, and CRM stages so the team can explain what changed and why without rebuilding the report by hand.
If the team is stuck defending the numbers, start with the Report Trust Checklist, then map the source-of-truth rules into CRM reporting, governed dashboards, and the Maven agent. Compare the broader platform mismatch pillar, a monthly marketing report workflow, and HubSpot cleanup, then review pricing. Bring the disputed report, run the checklist, map the first trusted workflow.
Sources and references
Jamie Isabel
Founder at Maven
