Your dashboard says 4,000 users. Your server logs say 600 people opened the thing this week. Both are telling the truth. They're just counting different things.
What the Chrome extension developer dashboard counts
Google's metrics page lists the stats plainly. Here's what each one means in practice, as one stop in our Chrome extension development guide.
| Stat | What it counts | What it doesn't tell you |
|---|---|---|
| Installs | Daily installs, new and returning | Whether they stayed past day one |
| Uninstalls | Daily removals | Why they left |
| Impressions | Times your listing was shown in a collection or visited directly | Search position |
| Users | Installed copies, by week | Whether anyone used it |
| GA4 (opt-in) | Extra listing data, not user-level | In-product behaviour |
Users means installed. Google's docs say the Users stat only captures installations and doesn't check activity. That one line explains most of the confusion founders hit.
Reading installs and uninstalls together
A single day of installs is noise. A week of installs next to a week of uninstalls is a story.
- Installs up, uninstalls flat: a listing change or a mention is working.
- Installs flat, uninstalls up: something broke, often after an update or a Chrome change.
- Both up together: you're getting traffic that doesn't match the promise on the listing.
Compare uninstalls to the version you shipped that week. Google splits Users by item version, so a bad release usually shows up there first.
The Developer Tools category page shows the dated counts behind this section.
Impressions are your listing's shop window
Impressions are the closest thing the dashboard has to "people who saw you." Install rate is installs divided by impressions, and it's the cheapest lever you control. More on that in our design ideas post.
What the dashboard can't show you
The dashboard is about the store. It knows nothing about what happens after install. For that, you need your own measurement:
- A first-run event when the extension opens for the first time.
- A weekly "used it" event tied to the core action.
- An uninstall survey URL, set with
chrome.runtime.setUninstallURL.
Keep it light and ask for consent where the law needs it. A handful of honest events beats a pile of tracking nobody reads.
How outside tools see the same listing
Outside tools, ours included, can only see the public listing. That means the rounded user bucket, the rating, the rating count and the version date. We're biased, but that's a real limit worth knowing: no outside tool can see your dashboard numbers.
In our crawl of 61,820 extensions (observed 2 Oct 2026), 3,202 of the 7,967 listings showing 10,000+ users had fewer than 50 ratings. Big installed counts with few ratings are common, and they're a hint that installed and engaged aren't the same crowd. Store ratings are the other half of that picture.
That ratio is the number your dashboard was never built to show. It's also the one that tells you whether the 4,000 are really there.
Questions people ask
Does the Chrome Web Store show active users?
No. Google's metrics page says the Users stat captures installations and doesn't monitor whether users are active.
Why is my public user count different from my dashboard?
The public listing shows a rounded figure, like 10,000+. The dashboard gives you the finer count behind it.
Can I connect Google Analytics to my listing?
Yes. Google lets developers opt in to Google Analytics 4 for extra, non-user-level data about the store listing.
Where these numbers come from
- developer.chrome.comChrome Web Store: Analyze your store listing metricsAccessed 3 Oct 2026
Part of our guide: Chrome Extension Development Guide for Founders: 5 Steps. More in Build and launch.
1,182 new extensions in the last 30 days in Developer Tools. See them all.
Start from a niche with proven demand instead of a blank page. Updated 3 Oct 2026 from our Chrome Web Store crawl
