If you have been comparing GA4 key events（Conversions） with your own database or CRM, you have probably noticed a gap. You are not alone—this is one of the most common questions I hear. In most cases, the gap comes down to a handful of predictable causes.
In this guide, I will walk through the six most common reasons and what to do about each.
Reason 1: Data Delay
GA4 Standard reports lag by 24–48 hours. If you compare today’s key events from GA4 against your internal system, you will almost always see a shortfall.
Fix: Compare using the same date range and exclude the current day and the previous day.
Reason 2: Consent Management (CMP)
A CMP blocks GA4 scripts until the user consents. If the user rejects tracking, GA4 never fires, and that key event is lost.
Fix: Enable Google Consent Mode. It sends cookieless pings that still register key events. I have seen it close a 40% gap to under 10%.
Reason 3: GA4 Tag Not on the Key Event Page
If a key event happens on a thank-you page or an external checkout page that does not have the GA4 tag, the event is never sent. The key event exists in your internal data but never reaches GA4.
Fix: Verify that the GA4 tag fires on every page where key events happen. For external checkout pages, use the referral URL parameter or the GA4 measurement protocol to send the key event server-side.
Reason 4: Ad Blockers
Ad blockers prevent GA4’s JavaScript from loading. When the script does not load, the key event is never sent.
Fix: No reliable client-side workaround exists. Server-side GTM can help—ad blockers cannot intercept server-to-server requests.
Heads up! Even server-side tagging is not a silver bullet. If the GTM web container itself is blocked, the data never reaches your server container.
Reason 5: Timezone and Attribution Differences
GA4 properties have a configured timezone. If your internal system uses a different timezone, the same key event can land on different dates in each system. Over a 30-day comparison, this causes small discrepancies that add up.
Similarly, GA4’s default attribution window may differ from how your internal system credits key events.
Fix: Check the GA4 property timezone under Admin → Property Settings. Align your reporting to the same timezone. For attribution, compare GA4’s model with your system’s model and document the difference rather than trying to make them match exactly.
Putting It All Together
Here is what I recommend when reconciling GA4 key events with internal data:
- Rule out data delay first. Exclude the current and previous day. If the gap disappears, that was it.
- Check the key event page. Does GA4 fire there?
- Review CMP configuration. Enable Consent Mode if you haven’t.
- Account for ad blockers. Estimate the rate and set expectations.
- Align timezones. One property, one timezone for all comparisons.
In my experience, a 10–20% gap is normal. If the gap is larger, one of the six causes above is usually responsible. Have you found a cause that is not listed here?