Uninstall rate
Uninstall rate is the proportion of app installs that are subsequently removed from devices. It is a direct churn signal for mobile apps, but it is notoriously hard to observe precisely: mobile platforms restrict how and when removals are reported, so uninstall data is often delayed, aggregated, or modeled rather than exact. It is best read as a directional trend alongside retention.
What this means
Uninstall rate divides removals by installs over a window. App stores and platform consoles surface install and uninstall counts, but with constraints: removals are not reported instantly, are aggregated to protect privacy, and may be estimated. Some store consoles report installs and uninstalls by date and dimension, but the figures are platform-defined and not equivalent to a per-user, real-time signal.
Why it is hard to measure
Operating systems do not, in general, notify an app the moment it is uninstalled, so analytics SDKs cannot directly observe removal. Reported uninstall numbers come from store-level aggregation or from inference (for example, push tokens that stop being deliverable). These approaches introduce lag and approximation. As a result, uninstall rate is most useful as a relative trend — comparing periods or release versions — rather than as an exact count.
Read it together with retention: falling retention and rising uninstalls together strengthen a churn conclusion.
- Removals ÷ installs over a window
- Platform-reported, aggregated, and often delayed
- Cannot be observed per-user in real time
How it appears in analytics and logs
A rising uninstall rate after a release or campaign points to dissatisfaction, broken functionality, or low-quality acquisition. Because reporting lags and is partly modeled, treat it as directional rather than precise.
Diagnostic use case
Watch the trend of app removals as a churn and dissatisfaction signal, while accepting that platform reporting limits make exact, real-time uninstall counts unavailable.
What WebmasterID can help detect
WebmasterID does not measure native app uninstalls; for web properties it tracks return and lapse signals first-party as an analogous churn indicator without third-party identifiers.
Common mistakes
- Treating store-reported uninstalls as exact, real-time counts.
- Attributing aggregated uninstalls to specific users.
- Reading uninstall rate without the matching retention trend.
Privacy and accuracy notes
Uninstall rate is an aggregate ratio. Platform-reported uninstall data is aggregated by design; do not attempt to attribute removals to identified individuals. This is educational, not legal advice.
Related pages
- App retention rate
App retention rate measures how much of an install or first-use cohort comes back after a number of days. Definitions vary: day-N retention counts users active exactly on day N, while rolling or range retention counts users active on or after day N. Because these methods produce different curves from the same data, the retention definition must be stated for the number to mean anything.
- Churn rate
Churn rate measures how many customers (or how much recurring revenue) you lose in a period. Like retention, it is defined by choices: the window, what counts as 'churned', and whether you count customers or revenue. Customer churn and revenue churn can diverge sharply, so the basis must be stated.
- The app_open event
app_open is a GA4 event collected automatically by the Firebase/GA4 SDK when a user opens an app or brings it to the foreground after it was in the background. It marks app launches and returns, underpinning app engagement, retention, and session analysis — but a foreground event is not the same as meaningful use.
- Privacy-first analytics
Read churn signals from minimized, aggregate data.
Sources and verification notes
- Google Play Console — statistics: installs and uninstallsDocuments install/uninstall statistics and their aggregated, dated nature.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.