- Published
- Nov 4, 2026
- Reading time
- 11 min read
Play, Firebase and RevenueCat DAU Differ? Audit the Observers
Reconcile app DAU across Play Console, Firebase and RevenueCat. Check activity signals, identities, chart versions and day boundaries before changing tracking.

In this guide (12 sections)
Different daily user totals do not establish which dashboard is wrong. First identify the activity each system observes, the identity it deduplicates, the selected app population and the exact day boundary. Play Console app usage, GA4 engagement and RevenueCat SDK activity are different measurement contracts. Choose the measure that answers your question, then investigate discrepancies within a comparable scope.
An actual question comparing Play Console, Firebase and RevenueCat asks which daily active-user count to trust when the RevenueCat figure is substantially higher. The opened page exposes an older relative age and no rendered answer establishing the cause. Its screenshots and reported figures do not identify every selected metric, filter, identity rule or chart version.
The right deliverable is a metric contract and a small observation trace, not a vote for the largest or smallest number. For an app publisher, this also prevents using an unrelated user count as the denominator for ad load or monetization.
Freeze the three screens before interpreting their totals#
Save each report or chart separately. Record its exact title, metric, date range, daily or period resolution, filters, timezone, app/package, platform and extraction time. Include chart version where the product has several versions. Preserve today's configuration separately from the configuration that existed on the disputed date.
Verify the application scope. A store app, a GA4 property containing several streams and a RevenueCat project containing several apps can cover different populations. Do not combine Android-only Play evidence with an unfiltered cross-platform total. Check which versions and release channels actually initialize each SDK.
Use this recommended comparison worksheet:
| Checkpoint | Record to retain | Unresolved question |
|---|---|---|
| Activity signal | App open, qualifying engagement or recorded SDK activity | Did all observers receive the same kind of activity? |
| Identity | User, device, app instance or customer grouping | What is counted once? |
| Population | App, platform, version and filters | Does each total cover the intended scope? |
| Time | Actual start/end instants and reporting day | Are the intervals comparable? |
| Reporting surface | Exact card, chart version and metric variant | Is this a daily count, period unique or another summary? |
Mark unavailable evidence explicitly. If the original screenshot lacks a metric name, retain that limitation rather than silently replacing it with today's most convenient chart.
Compare what each app report observes
Play Console, GA4 and RevenueCat use different activity and identity rules. Discuss which user measure answers your question.
Discuss measurement scopeA short inquiry to scope relevant measurement options; financial adjustments are not promised.
Check what Play Console calls daily activity#
The current Play Statistics reference defines DAU as users who opened the app on a given day. It separately defines installed-audience measures involving an installed app and recent device activity. An installed base is not evidence that everyone opened this app that day.
The same reference says some metrics use aggregate shared data and are adjusted to account for users who opted out. A Play total should therefore not automatically be treated as an exportable, exact census of identified app users.
Also preserve the user-versus-device selection. Google's Grow overview documentation distinguishes unique users across devices from unique devices. It explains that a monthly-active card can have a daily-activity time series. Read the card and selected point separately; do not assume a prominent summary number is that day's DAU.
For example, one permitted signed-in account observed on two devices can support two device observations without establishing two distinct account users. Conversely, a shared device does not prove that only one person used it. Keep the units documented rather than converting either measure into a claim about physical people.
Identify the exact Firebase or GA4 user metric#
Google's user-metric reference defines Total users through any recorded event and Active users through the documented engagement-related criteria. For Android, active-user qualification includes an engaged session or collection of first_open or engagement_time_msec. A field labeled Users needs its underlying metric established before comparison.
That does not mean every returning app open must be absent from Active users, or that a short visit is always excluded. Inspect the events actually collected and the report's definition. Do not substitute an assumed ten-second rule for the complete active-user contract.
Preserve the configured reporting identity as well. The reporting-identity guide distinguishes device-based, observed and blended grouping; app device identity uses the app-instance ID. Account IDs, app-instance IDs and the store's grouping are not interchangeable identifiers.
If the demonstrated fault is incorrect login, logout or account switching, continue with the GA4 User-ID implementation audit. This cross-product comparison does not justify replacing anonymous identifiers or changing reporting identity simply to reach another dashboard's total.
Verify which RevenueCat chart you actually have#
The current Active Customers chart is available in Charts v3. It approximately counts unique customers for whom RevenueCat recorded SDK activity during the selected period, whether or not they purchased. Repeated activity within that period does not create another customer in the chart.
That current definition must not be retroactively assigned to the forum author's unspecified historical screen. First establish its actual chart or Overview metric, version, period and app filters. Active subscriptions, new customers and active customers describe different populations even when a team informally calls all of them DAU.
The chart documentation also limits accuracy to the most recent 28 days; older data can be inaccurate or zero. Conditional SDK initialization can affect observation coverage. Aliased IDs are treated together when seen again, but previously observed separate IDs may remain separately counted until they leave the chart's window. These are bounded current behaviors, not a diagnosis of the original account.
If the disputed day is outside that supported history, preserve the original export and ask the provider what evidence remains available. Do not treat today's reconstructed old chart as a trustworthy reference solely because it can be displayed.
Review identity transitions without inventing a cross-product join#
RevenueCat's identity documentation distinguishes generated anonymous App User IDs from custom IDs. Reinstallation can generate a new anonymous ID. Custom IDs are project-scoped, and the same configured ID can associate a customer across platforms. The login and alias rules determine the applicable transition.
An App User ID does not automatically equal a Firebase authentication identifier or a GA4 app-instance ID. Inspect the implementation owner's actual mapping and its effective version. A matching-looking string in two logs is insufficient without a documented assignment contract.
Use synthetic accounts for an authorized QA sequence: fresh anonymous use, later sign-in, return visit, another device, sign-out and another account. Record the supported identity state at each observation point. Keep customer identities and the private mapping out of public tickets or drafts.
Do not merge production profiles, reset users, recreate accounts or change subscription identity behavior merely to make totals converge. Those actions can affect access and reporting. First establish a reproduced transition error and let the responsible owner review any correction separately.
Compare actual day boundaries, not matching date labels#
The RevenueCat Charts overview specifies UTC for charts. GA4's property setup reference explains that the selected reporting timezone determines the date assigned to activity. The Play Statistics reference identifies Pacific Time for the applicable installation-related statistics; retain the actual selected surface's documented basis.
Write the interval as start and end instants with timezone, including daylight-saving handling where relevant. A calendar date can represent different hours across the reports. A request near midnight may land on different daily rows without disappearing from either system.
Do not change production timezone settings as a diagnostic shortcut. Preserve the originals and compare a suitable overlapping interval or supported timestamped evidence. If only daily aggregates remain, document that exact rebucketing may be impossible.
Daily distinct counts are not additive across differing boundaries: the same identity can occur in several buckets. Moving a daily total into a new date column does not reassign its underlying events. Preserve the original grain and avoid claiming the time correction explains a difference before calculating it from available evidence.
Trace the first observer that did not receive the intended activity#
Compare the released app's actual initialization and collection sequence, not only the source configuration. A purchase SDK initialized after a paywall action can observe a narrower journey than an analytics SDK initialized earlier. A correct configuration in a newer build does not establish what an older installed version sent.
For one authorized diagnostic journey, record:
- The app/build, platform and synthetic test state.
- The actual opening and relevant foreground activity.
- When each observer becomes available under the applicable collection rules.
- The supported activity or identity observation produced by each integration.
- Receiving evidence available through the provider's supported diagnostic path.
- The corresponding report definition and later extraction, kept separate from debug traffic.
Do not synthesize production activity, force a purchase or bypass consent to fill a user-count gap. A local method call, a transmitted observation and a processed unique-user result are separate boundaries. The tracking QA checklist helps retain that versioned evidence without assuming that a debug success must appear in every ordinary report.
A hypothetical comparison with bounded conclusions#
Suppose two completed, explicitly named reports show 120 Analytics active users and 180 RevenueCat active customers. These invented totals are not app measurements or a reconstruction of the question.
The numerical difference is 60. Relative to 120 it is 50%; relative to 180 it is approximately 33.33%. Neither calculation demonstrates 60 missing Analytics users. The reports can differ in activity, identity, scope and timing, and the available aggregates do not expose which observations overlap.
Now conduct a separate hypothetical selected QA sample of six permitted test journeys:
| Journey outcome recorded by the test harness | Journeys |
|---|---|
| Relevant receiving evidence observed for both integrations | 3 |
| Analytics receiving evidence only | 1 |
| Neither receiving surface established | 2 |
| Total selected journeys | 6 |
Analytics receiving evidence was established in 4 / 6, or 66.67%, of these selected journeys; RevenueCat evidence in 3 / 6, or 50%. These are test-observation fractions. They are not DAU, population coverage estimates or proof the other observations were never processed.
Investigate each unsupported journey's first missing boundary. If the test proves a conditional initialization issue on one path, state that finding for that path. Do not project the selected sample's percentage onto all production activity or allocate the full 60-count difference to it.
Keep publisher ad-user denominators on their own contract#
AdMob's current Ads Activity user-metric reference describes its supported AU and DAU variants and their Analytics-integrated population. A Play usage count or RevenueCat customer total does not automatically reconstruct that denominator.
For exposure time, impressions per user or Ads ARPU, retain the selected report’s matching components and included population. For a revenue-collection problem, the AdMob–Firebase collection audit separates automatic integration, manual callbacks and reported revenue.
The useful business distinction remains activity versus observed ad delivery. More measured customers does not by itself establish more ad viewers, valid impressions, subscriptions or earnings. Keep each outcome on its own supported population.
Close with a metric contract and a precise remaining question#
Before accepting the comparison, retain:
- Exact reports, chart versions, app scope and daily resolution.
- Activity definitions and the identity units each observer groups.
- Actual day boundaries and the remaining rebucketing limits.
- Historical coverage limits and preserved original exports.
- The first demonstrated collection or assignment failure, if any.
- Authorized retest evidence and unresolved production scope.
Choose a stable primary metric for the stated product question and preserve the others as complementary observations. A primary metric is a documented decision, not a claim that every other system should match it. Escalate an unexplained difference with those contracts and one reproducible journey.
For campaigns already measured through AdProof, keep a supported event or aggregate export with matching dates, timezone and filters alongside independently obtained app evidence. The anonymized FMCG in-app count-once case concerns delivery reconciliation, not a DAU census. Discuss the available campaign evidence to establish supported scope. AdProof campaign records do not reconstruct private Play, Analytics or RevenueCat user identities.
Frequently asked questions#
Which dashboard contains the real number of people using my app?
First define the activity and identity you need to measure. App users, app instances, devices and customer profiles are different units. A cross-product total alone does not establish a complete census of people.
Does RevenueCat Active Customers count paying subscribers only?
The current Charts v3 definition includes customers with recorded SDK activity whether or not they purchased. Verify the actual chart and version instead of substituting Active subscriptions or New customers.
Can I use today's RevenueCat chart to prove an old daily count?
The cited Active Customers documentation limits accuracy to the most recent 28 days. Preserve historical exports and the original chart definition; do not treat older displayed data as reliable reconstruction without further evidence.
Should I change identity or consent settings until the totals agree?
No. Establish the report contracts and reproduce a specific collection or assignment issue. Any change needs the responsible owner's review and a bounded test while preserving user choices and subscription access.
Research and scope#
Reviewed 4 November 2026. The linked original displays an older relative age; its exact creation time and selected historical chart versions were not exposed. Current product references establish today's documented distinctions, not the cause of that author's figures or a new platform announcement. The workflow and examples are recommendations and hypothetical arithmetic; no account, SDK configuration, identity mapping or report setting was changed.
Compare what each app report observes
Play Console, GA4 and RevenueCat use different activity and identity rules. Discuss which user measure answers your question.
Discuss measurement scopeA short inquiry to scope relevant measurement options; financial adjustments are not promised.
