The State of Extension Analytics

Aggregate, anonymized benchmarks for the browser-extension ecosystem — built entirely from extStat's own first-party data. How does a typical extension's installs, active users, and engagement compare? This page is our honest, running answer.

Privacy-first, like everything extStat does: every figure here is a median across many projects, computed only once enough projects have data to keep it anonymous. No single extension, developer, or user can be identified from anything on this page.

How to read these benchmarks

Each number is the median value across all contributing projects over the trailing 30 days. The median (the middle project, not the average) is deliberate: it isn't skewed by a handful of very large or very small extensions, so it reflects what's typical.

• Median active users — the middle project's count of unique clients (people) active in the window.
• Median installs — the middle project's unique installs in the window.
• Median events — the middle project's total tracked events (all volume).
• Median sessions — the middle project's session count (engagement volume).

Our privacy & honesty rules

This surface exists to be useful and trustworthy, not to inflate a vanity number — so we bind ourselves to a few rules:

• K-anonymity floor. We publish a benchmark only when at least 20 different projects have data in the window. Below that floor we show nothing but this methodology and a "coming soon" note — never a fabricated or thinly-sourced figure.
• Aggregates only, never rows. Every published figure is a median across the whole population of contributing projects. We never expose a per-project or per-user number, a minimum, a maximum, or a total that could single anyone out.
• First-party data only. These numbers come from extensions that use extStat and nothing else — no scraping of store listings, no purchased datasets, no estimates dressed up as measurements.
• No numbers until they're real. extStat is in public beta. While the sample is still small, this page is honest about it: you'll see the methodology and structure here, and the figures will appear the moment there's enough anonymized data to report them responsibly.

The benchmarks

Methodology, in full

The dataset is every event sent through extStat by participating extensions, aggregated across Chrome, Firefox, Edge, VS Code, Figma and other supported stores. For each project we compute its totals over the trailing 30-day window (installs and active users counted as unique clients; sessions and events counted as volume), then take the median of those per-project values across the whole set.

We report a coarse, rounded sample size (for example "20+ projects") rather than an exact count, so even the number of contributors can't be used to de-anonymize anyone. The window is 30 days in UTC, matching the default range in the extStat dashboard, and the figures update as the ecosystem does.

A note on interpretation: because participation is opt-in and the ecosystem is young, these medians describe extensions that use extStat, which may differ from the ecosystem as a whole. We'll say so plainly here as the picture sharpens, and we won't over-claim.

Measure your own extension

These are the ecosystem medians. To see where your extension lands against them — installs, active users, retention, and your own custom events, across every store — add the extStat SDK (about 2 KB, zero dependencies) and watch your numbers appear in the dashboard within seconds. It's free for 10,000 events a month.