Ask most Chrome extension developers how their extension is doing and they'll quote one number: install count. It's the number the Web Store puts front and centre, and it feels like progress when it goes up.
It's also the number that hides everything that actually matters.
The Chrome Web Store developer dashboard is generous with counts and silent on causes. It will happily tell you that 4,000 people installed your extension and 900 uninstalled it. It will not tell you whether the 3,100 who stayed ever open it, why the 900 left, or what any of them wish it did instead. If you're making roadmap decisions off the dashboard alone, you're steering with half the instruments dark.
Here's precisely what Chrome gives you, the four blind spots it leaves, and how to light each one up.
What the Chrome Web Store dashboard actually gives you
Credit where it's due — the built-in stats are a real starting point. On the developer dashboard you get:
- Weekly users — the number of users with your extension installed, broken down by country, language, OS, and extension version.
- Install and uninstall counts — raw daily numbers.
- Impressions — how often your listing was shown in Web Store search and browse.
- Ratings and reviews — your public star rating and the reviews behind it.
You can also opt your listing page into Google Analytics 4, which adds funnel data for the store page itself — page_view, session_start, first_visit, user_engagement — so you can see how many people who saw your listing actually installed. (Worth turning on. Note that Chrome sets a two-month data-retention window and de-identifies the data, so you can't track individuals — by design.)
That's a solid picture of acquisition: how people find your listing and whether they install. The problem starts the moment they do install.
Blind spot #1: You can't see who's actually using it
The dashboard's headline metric is "users" — but "users" means installs that still exist, not people who open your extension. Someone who installed your extension three months ago, never used it, and forgot it's there counts exactly the same as your most devoted daily user.
And the cadence is weekly. Chrome reports weekly user counts; there is no daily-active-users figure, no session frequency, no "how many of my installs are actually alive." For a product decision like "is this feature worth maintaining?" that gap is enormous — retained-but-dormant looks identical to retained-and-loving-it.
How to actually measure it: the only way to know your real active usage is to instrument the extension itself. Fire a lightweight, privacy-respecting event when the user genuinely uses a core feature (not just on install), and you can finally compute daily and weekly actives, session frequency, and feature adoption. A few things to get right:
- In Manifest V3 your background logic runs in a service worker that spins down when idle, so batch events and flush them rather than holding a long-lived connection.
- Be transparent and anonymised. Extension users are (rightly) wary of tracking — aggregate, don't fingerprint, and say so in your privacy policy.
- Measure activation, not just opens: the event that predicts retention is usually the first time a user completes the thing they installed you for.
Blind spot #2: You can see that users leave, never why
The dashboard shows uninstall counts. It will never show you a single reason.
This matters more than any other blind spot, because uninstalls are where your most fixable problems hide. Studies of extension retention consistently show a large share of installs — commonly estimated at 40–60% — are removed within the first week. Most of those users hit some friction, removed the extension, and moved on without leaving a review, a ticket, or any trace. The dashboard records the departure as a number and throws the reason away.
Reviews don't fill this gap — they distort it. People who leave reviews are the emotional extremes: delighted or furious. The median churned user had a mild, specific, fixable problem ("it didn't work on the one site I needed") and simply left quietly. Optimise off reviews and you're serving the loud minority while the silent majority walks.
How to actually measure it: Chrome gives you exactly one hook to reach a leaving user — chrome.runtime.setUninstallURL(). It opens a URL of your choice the moment someone uninstalls. Point it at a short feedback form (one structured question — "why did you leave?" — plus an optional text field) and you convert a dead-end statistic into categorised churn data: bug, missing feature, too slow, found an alternative, no longer needed. We wrote a full guide on understanding and reducing extension churn if you want the deeper version. This is the single highest-leverage instrument you can add, and it takes one line of code plus a hosted form.
Blind spot #3: You have no idea what users actually want
Nothing in the dashboard captures a feature request, a bug report, or a "please add X." Your only inbound signal is reviews — and, again, reviews are biased and low-volume. A one-star review that says "needs dark mode" is a data point; it is not a count of how many of your thousands of users feel the same way.
Without a real feedback channel you end up building on vibes: the loudest reviewer, your own hunch, the last thing someone tweeted at you. Sometimes that's right. Often it means you ship a feature 1% of users wanted while the thing 20% keep asking for sits unbuilt because it never surfaced as a pattern.
How to actually measure it: give users a place to tell you — and, crucially, to vote. A public feedback board turns scattered opinions into a ranked signal: instead of guessing whether "dark mode" matters, you can see 240 upvotes next to it and three next to something else. It also closes the loop — users can see what's planned and shipped, which itself reduces churn because people stick with a product that's visibly listening. (This is exactly what we built UserFeed for, but the principle stands whatever you use: make wanting something a measurable action, not a review lottery.)
Blind spot #4: You can't see behaviour inside your own extension
The dashboard stops at the store. Once someone installs, you're blind to everything that happens next: which features they touch, where they get stuck, what they try before they give up. If your extension has an onboarding flow, a settings page, or a multi-step feature, Chrome tells you nothing about how people move through it.
This is the difference between "300 people uninstalled" and "300 people uninstalled after opening the options page and never returning." The second is a diagnosis; the first is just grief.
How to actually measure it: the same self-instrumentation from blind spot #1, extended to a funnel. Track the key steps of your core flow as events — installed → opened → activated first feature → returned next day — and the drop-off point tells you where to spend your next week of dev time. You don't need a heavy analytics stack; you need three or four well-chosen events on the path that matters.
The pattern: Chrome measures acquisition, you have to measure everything after
Line the blind spots up and the shape is obvious. The Web Store dashboard is an acquisition tool — impressions, installs, listing conversion. It was never built to tell you about activation, retention, or intent. Those three are where a good extension becomes a lasting one, and they're exactly the three Chrome leaves to you.
The good news is that filling the gaps is cheap and mostly one-time:
- Instrument core usage → real active users, feature adoption, in-extension funnels.
- Set an uninstall URL → survey → categorised reasons for churn, the most fixable problem you have.
- Run a feedback board with voting → ranked feature demand instead of review roulette.
None of these require a data team. They require deciding that install count isn't the scoreboard — retention and intent are — and adding the handful of instruments Chrome forgot to give you.
If you want the shortcut on the two highest-leverage ones, UserFeed gives you a hosted uninstall feedback form and a public feedback board built specifically for extension developers — the "why did they leave" and "what do they want" signals, without wiring them up yourself. Free for your first extension. Either way: stop steering by install count. Turn on the lights.