Why website counts and Google Analytics differ

Know which source you are reading

First-party website reporting counts consented public pageviews grouped by page and UTC day. It does not measure unique people or sessions. Google Analytics reports have their own metrics, property time zone and processing behavior.

1. Identify first-party pageviews or Google Analytics as the source.
2. Compare the same hostname and a compatible date range.
3. Check consent, collection settings and the displayed reporting status.

• Private CRM, admin and sign-in routes are excluded from first-party public-page reporting.
• A GA4 measurement ID configures browser collection; it does not prove that reporting access or data delivery works.

Check reporting access separately

The Google reporting adapter requires a configured property and a server-managed reporting identity with access to that property. If it is not connected or Google denies access, the dashboard should say so. No estimated visitor or session figures should replace a missing report.

• Browser privacy signals and consent can affect collection.
• Google reports may be delayed or subject to reporting thresholds.
• First-party and Google counts should not be added together as distinct visitors.

When asking about a discrepancy

Send the measure, period and source. Deployment administrators manage reporting credentials; do not send a service-account key in a support request.

• The hostname and selected dates.
• The metric names and displayed source status.
• Whether collection settings or consent choices recently changed.