Update Impact Analysis
0 measurable observations (out of 99 total) · Observation start date not yet finalized
Before you read this page
This table pairs rankings before and after an update — it does not mean the update caused the ranking change.
Rankings also move with competing games. Even if a game stays exactly the same, its rank can shift if other games rise or fall.
This metric is based on Google Play's top-grossing rank, not revenue figures. This site does not track revenue or download counts.
How to read these numbers
So far, 0 updates have both before and after rankings available. That's not enough to break down by type yet — the type breakdown table will appear once 20 observations have accumulated.
Ranking snapshots are collected once a week and can't be backfilled, so updates released before data collection began can't produce before/after values. That means observations can only grow over time. What you can see right now is the breakdown of exclusion reasons — readable even with a small sample, and a preview of which observations will remain going forward. Currently, 99 of 99 total updates (100%) are excluded from the count.
The figures below are values that moved together — they are not evidence that the update caused the change.
Key metrics
Measurable observations
0
out of 99 total
Games observed
0
Lower numbers mean a higher rank. "▲" means the rank moved up (better), "▼" means it moved down (worse).
Reasons for exclusion from measurement
We disclose, by reason, the observations excluded from aggregation because before/after rankings couldn't be confirmed. What we couldn't see matters as much as what we did.
| Reason | Count | Share of total |
|---|---|---|
| No rank data for the prior week | 99 cases | 100% |
| Outside top 100 the following week | Not applicable | Not applicable |
| Outside top 100 the prior week | Not applicable | Not applicable |
| Another update overlapped the same week | Not applicable | Not applicable |
| No rank data for the following week | Not applicable | Not applicable |
Filling in missing data with zero instead of excluding it would fabricate the false claim that 'nothing changed.' So we don't count what we can't confirm — instead, we state plainly here how many were excluded and why. Rules that were never triggered are still listed, because leaving them out would read as if those rules never existed.