Understanding GA4 Data in NinjaCat: Why Numbers May Look Different

Understanding GA4 Data in NinjaCat

If the Google Analytics 4 (GA4) numbers in your NinjaCat reports look a little different from what you see in the GA4 interface, you can rest easy: this is expected behavior, not an error. NinjaCat pulls your GA4 data directly from Google's official Analytics Data API — the same v1beta data family that powers the GA4 interface itself. A handful of well-documented characteristics of that API can cause totals or breakdowns to appear slightly differently, and NinjaCat is designed to work correctly within them.

This guide explains how GA4 data flows into NinjaCat so you know exactly what you're looking at — and why it's accurate.

How GA4's API shapes your data

1. GA4 data is available from January 1, 2021 onward

Google's Analytics Data API makes GA4 data available starting January 1, 2021. This is a boundary set by Google's data source, so any date range that reaches earlier than that has no data to return. If an older report looks like it's "missing" GA4 data, a start date before this boundary is almost always the reason — and NinjaCat is faithfully reflecting what the API provides.

What to do: Set your report's date range to start on or after January 1, 2021.

2. Detailed reports are intelligently split and recombined

Google's API allows up to 9 dimensions in a single GA4 query. When a report calls for more breakdown detail than that, NinjaCat automatically and transparently splits the request into multiple queries and recombines the results for you — so you can build richer reports than a single API call would otherwise allow. For high-cardinality breakdowns (dimensions with many unique values, like landing pages or campaign names), this can cause totals to differ slightly from a simpler view in the GA4 interface. That's a normal characteristic of how the data is aggregated, not a miscount.

What to do: If a heavily broken-down report looks unexpected, compare it against a simpler version with fewer dimensions to confirm the totals, then layer breakdowns back in as needed.

3. Google's API quotas can briefly affect timing

Google enforces usage quotas on its Analytics Data API. When those quotas are reached, data retrieval may be briefly paused, which can make a report look momentarily out of sync with the GA4 interface until the data catches up. NinjaCat respects these quotas to keep your data delivery reliable, and any timing differences resolve on their own.

What to do: If numbers look incomplete, give it a short while and refresh the report — quota-related timing differences are temporary.

When to reach out to support

These behaviors cover the vast majority of differences between NinjaCat and the GA4 interface. If you've confirmed your date range starts on or after January 1, 2021, simplified the report to rule out query complexity, and given any quota timing a moment to clear — and the numbers still don't reconcile — our support team is happy to help. Reach out to NinjaCat support and we'll be glad to take a closer look.