Install metrics
Google provides daily install and uninstall reports with country, language and operating-system breakdowns. Both new and returning users are included. Use Date range to select the period and export the report as CSV when you need a saved record. These controls are described in the Chrome Web Store metrics documentation.
An install total answers how many installations the store counted under that report’s rules. Subtracting uninstalls gives a difference between event totals; it does not calculate return among the people who first used the product on one date.
Keep the exact label with a number. The Installs definition is a short reference for a report or brief.
Users and activity are different measures
The store’s Users section groups its statistic by country, language, operating system and item version. Google’s documentation explicitly says this statistic captures installations and does not monitor whether users are active.
For product activity, choose an action that demonstrates use: for example, successfully saving a note. Record the event, the identifiers you can observe and the time window. A background update and a completed product action answer different questions.
Use the store Users definition when labelling a store export. Questions about onboarding or the first useful action belong in extension growth.
A cohort and D7 example
Teaching example with invented dates and counts. It is not an Extcorp campaign result, benchmark or retention promise.
Take 120 distinct product IDs whose first recorded use of a note-saving Chrome extension was between September 1, 2026, 00:00 inclusive and September 2, 00:00 exclusive, UTC. Observation is complete and permitted, IDs stay stable and test IDs have been removed. Each ID represents one measured browser profile, rather than a verified person across devices.
| Part of the calculation | Definition and value |
|---|---|
| Denominator | All 120 IDs in the September 1 first-use cohort, including IDs with no observed return. |
| Qualifying return | Successfully saving a note through the extension. Installation, background updates and automatic page loads do not qualify. |
| D7 window | September 8, 2026, 00:00 inclusive to September 9, 00:00 exclusive, UTC. Only day 7 is counted. |
| Numerator | 30 of the original 120 IDs return. They generate 66 qualifying events; each returning ID counts once. |
| Completed review | September 10, 2026, 12:00 UTC. The window is closed and event processing is complete. |
| D7 return rate | 30 ÷ 120 × 100 = 25%. |
The remaining 90 IDs have no qualifying return observed on day 7; this does not classify them as uninstalled or permanently lost. The 66 events count actions, while the 30 returning IDs count members of the original cohort. All active IDs on September 8 could also include older cohorts.
This calculation uses separate product observations. Store installs, uninstalls and Users cannot supply its numerator. The D7 definition keeps the cohort, action and observation window together.
Calculate the rate after the window closes and processing is complete. With missing observations, keep it unknown; with a zero denominator or unmatched IDs, resolve the inputs first.
How to check and record a campaign report
Before comparing two readings:
- Match the store listing and the exact report name.
- Select the same period and available country, language and operating-system filters.
- Save the metric, value, capture date and CSV export.
- If product return matters, attach the separate cohort definition, event, window and review date.
Use the extension install pilot plan to agree these fields before a campaign. For discovery in the store, see Chrome extension store visibility.
Extcorp offers extension install campaigns through advertising. Price and test terms are available on request. Send the store link, target browser and the installation measure you want to discuss; activity and retention require their own product data.
Extcorp is independent of Google and Chrome Web Store.