Why GA4 users, sessions and conversions never add up
People open GA4, see users, sessions and conversions that refuse to reconcile, and conclude it is broken. Usually it is not. GA4 counts these things with different rules, and modelling fills gaps. Here is how to tell a by-design difference from a genuine fault.
Different counters, different rules
- Users are deduplicated across sessions and devices where possible, and are often modelled when consent is missing.
- Sessions reset on a new day, after 30 minutes idle, or on a new campaign source, so one person can rack up several.
- Conversions (key events) can count more than once per session unless you set them to count once.
So users < sessions, and conversions can exceed converting users. That is expected, not a bug.
Where modelling widens the gap
With Consent Mode, GA4 models users and conversions it cannot directly observe. Reported totals then include estimates, which will never tie out to a raw order count. The modelled data is useful, but it is not a ledger.
When the gap is a real problem
It is worth investigating when sessions balloon far beyond users (often self-referrals splitting journeys), when conversions are wildly over actual orders (duplicate firing), or when numbers swing day to day with no cause. Those are tracking faults hiding behind "GA4 is just weird".
Want us to check your tracking in 10 seconds?
Pop in your domain and we will show you what is firing, what is not, and where data is leaking. Free, no signup.
Check my tracking freeGet a plain-English audit
We check your live GA4, Google Tag Manager and consent setup by hand and tell you exactly what is wrong. The audit comes off any build.
See how it works & pricingDatahound are analytics and ad-tracking specialists. We fix broken GA4, Google Tag Manager and server-side tracking so every sale, form and call gets counted. Back to datahound.agency · All tracking guides · Key events vs conversions in GA4