Skip to main content

Why are my numbers different than Google Analytics? (or other tools)?

It’s normal to see some differences between GoodMetrics and other analytics tools — especially Google Analytics (GA4).

Some differences reflect how each platform measures and attributes data. Other times, these differences come from GoodMetrics providing more complete and privacy-friendly data.

Below are the main reasons your numbers may not match exactly. Even with these differences, overall trends between platforms should still be directionally consistent.

1. Consent, cookies & ad blockers​

GA4 depends on cookies to identify users and maintain sessions. When cookie consent is required (for example, under GDPR), analytics cookies aren’t set until the visitor grants permission.

If users ignore or reject the banner, especially in Europe, those visits typically aren’t recorded at all. Sites using Google Consent Mode can fill in part of the gap with modeled estimates rather than observed visits — but modeled data is an approximation, not a real measurement.

Even without a consent banner, GA4 still misses a meaningful share of traffic. Ad blockers and browser privacy features (uBlock Origin, AdGuard, Brave Shields, Firefox Enhanced Tracking Protection, Safari Intelligent Tracking Prevention) block or degrade GA4 for a significant portion of visitors, often 10–30% of traffic depending on audience. Note also that running GA4 in the EU or UK without analytics consent is generally considered non-compliant under GDPR and ePrivacy rules.

GoodMetrics doesn’t rely on tracking cookies, so no consent banner is required, and visits are recorded even if cookies are disabled. Our first-party tracking script is also much less commonly blocked than GA4.

As a result, GoodMetrics often shows higher and more complete visitor counts, particularly in regions with strict privacy regulations or widespread cookie consent banners.

2. Data freshness & reporting latency​

GoodMetrics processes data continuously:

  • The Realtime report updates instantly as visitors browse your site.
  • The main dashboard reports are updated constantly as new events are received.
    Sessions are finalized and rolled into the reports once 30 minutes of visitor inactivity has passed, ensuring accurate session totals without delay.

GA4 updates much more slowly:

  • Its “Realtime” dashboard shows activity from the past 30 minutes (with a per-minute graph of the last 5 minutes), not true live data.
  • Standard reports can take several hours to update, and in some cases 24–48 hours before all events appear.

Because of this, GA4 may appear to lag or undercount recent activity compared to GoodMetrics.

3. Attribution & lookback windows​

GA4 often reattributes returning direct sessions to a previous non-direct source, within a configurable lookback window (commonly 30 days for acquisition conversions, up to 90 days for others). Its default conversion attribution model is now Data-Driven Attribution, with Last Non-Direct Click available as an alternative.

This means if a user first visits your site from a source (e.g., chatgpt.com) and then returns directly within the lookback window, GA4 may still credit that return session to the original source.

GoodMetrics on the other hand attributes each session to the referrer actually present at the time of the visit. If a returning visitor has no referrer (for example, they typed your URL or used a bookmark), we classify that as Direct, not another chatgpt.com session.

However, GoodMetrics also tracks the Initial Referrer—the first site or campaign that brought the visitor to your website. This gives you visibility into both the true source of each session and the original touchpoint that introduced the visitor, without persisting attribution across every visit.

4. UTM handling & normalization​

GoodMetrics only records UTM parameters when they appear in the URL. If no UTM parameters are present, we rely on the browser’s referrer header to determine where the visit came from. These are shown separately in the Referrers report.

GA4, by contrast, merges UTM data and inferred traffic sources into combined Source/Medium and Default Channel Group categories. It can classify traffic even when UTMs are missing—sometimes using Google’s internal mapping or attribution memory.

The result is that GA4 organizes traffic into predefined channels, while GoodMetrics keeps a clear separation between explicit UTMs and actual referrers. This approach makes it easy to see exactly what data was passed, without assumptions or reclassification.

5. Metric definitions​

Different analytics tools define key metrics in different ways.

For example:

  • Sessions: GA4 uses cookie-based session stitching, while GoodMetrics defines sessions based on real visit activity without cookies.
  • Visitors / Users: GA4 relies on persistent identifiers stored in cookies; GoodMetrics uses cookieless tracking with no persistent identifiers.
  • Bounce and engagement: GA4 emphasizes Engagement rate and defines its Bounce rate as the inverse of engagement, which differs from the traditional single-pageview Bounce rate; GoodMetrics uses more conventional engagement logic.

These definitional differences mean absolute numbers (like total visitors or session counts) may vary, but relative patterns—such as which pages or campaigns perform best—should remain consistent.

Summary​

While GoodMetrics and GA4 may report different totals, both are directionally accurate. The differences mostly reflect GA4’s cookie-based persistence and modeled data versus GoodMetrics’ real-time, privacy-first measurement.

GoodMetrics aims to give you a clear, immediate, and transparent view of your website traffic—based only on what’s actually observed, not inferred or modeled.

This isn’t an exhaustive list, but it covers the most common reasons you may see differences between GoodMetrics and other analytics tools.