Data discrepancies

Data discrepancies are differences in numbers that happen when the same metrics or events are measured in multiple analytics tools but the numbers don’t match exactly. For example, page views, conversions, or audience sizes might appear higher in one tool and lower in another, even though both are tracking the same website or campaign.

Data discrepancies are common when comparing personalization and analytics tools. They usually result from differences in definitions, identity models, session logic, consent handling, or event timing, not from missing or incorrect data.

The key is to compare equivalent metrics, over the same time range, using finalized reports.

NOTE: Small variations between numbers across tools can be expected. But if you are seeing unexpectedly large differences, please follow the troubleshooting checklist under the Quick checks section before contacting support.

It’s common to see different numbers when comparing our tool with other analytics tools, such as Google Analytics (GA4). Below are the most frequent scenarios that can occur between our tool and, for the purpose of this article, GA4. 

Visitor or user counts don’t match

You may notice that visitor or user numbers differ across tools, especially over longer time ranges.

• We report Total Visitors as the sum of unique visitors per day. A visitor returning on multiple days is counted once per day.

• GA4 reports Total Users as unique users across the entire selected date range.

Why this happens:
Each tool defines and aggregates users differently. Over 7, 30, or 90 days, Contentful numbers often appear higher. This is expected and does not indicate missing data.

Session counts are significantly different

Session counts are one of the most common sources of discrepancies.

• Contentful Personalization sessions always end after 30 minutes of inactivity.

• GA4 sessions default to 30 minutes but can be extended up to 7 hours and 55 minutes.

Why this happens:
If GA4’s session timeout has been increased, it will report fewer sessions than our tool for the same user behavior.

Events appear in one tool but not another

Some events, such as clicks or page views, may appear in one tool but be missing in another.

Common reasons include:

• Events firing at slightly different times.

• One tool loading earlier or later than the other.

• Users navigate away before both tools capture the event.

Why this happens:
Client-side tracking depends on timing and page lifecycle. Fast navigation or early exits can cause one system to miss events.

User identity and profile counts differ

Different tools identify and group users in different ways.

• Contentful Personalization assigns each visitor a persistent stable_id to build a profile across sessions.

• GA4 relies on device-based identifiers and consent-dependent signals.

Why this happens:
Identity resolution works differently in each system, which directly affects user and profile counts.

One tool consistently reports higher numbers

In some cases, one tool may always show more traffic or events.

This can happen when:

• A Consent Management Platform (CMP) allows one tool but restricts another.

• Ad blockers or browser privacy settings block client-side tracking.

• One tool runs server-side or at the edge, while another runs client-side.

Why this happens:
Tools that are blocked less often or run server-side typically capture more data.

Use the following troubleshooting checklist to narrow down the most common causes of data discrepancies, before reaching out to support:

1. Confirm you’re comparing the same time range.

   1. Make sure both tools use the same date range, and check whether time zones match.

   2. Avoid comparing real-time data with historical or processed reports.

2. Verify you’re comparing equivalent metrics.

   1. Confirm the metrics mean the same thing in each tool (for example, visitors vs users).

   2. Check how sessions are defined and whether session timeouts differ.

   3. Ensure event names and definitions match across tools.

3. Review consent and ad-blocking behavior.

   1. Check whether a Consent Management Platform (CMP) is in place.

   2. Confirm both tools are treated the same under consent rules.

4. Look for implementation issues.

   1. Verify that tracking requests are visible in the browser’s Network tab.

   2. Check whether requests consistently include required identifiers.

   3. Watch for missing events, incomplete payloads, or errors.

When to reach out to support

If discrepancies are large, sudden, or growing over time, and the checks above don’t explain them, please reach out to support.