Chrome Web Store Extension Stats Tracker

Give it Chrome Web Store extension URLs or IDs. It returns one row per extension with the numbers on the public extension page: users, average rating, the exact rating count, version, last update, category, size and whether the extension carries the Featured badge.

Turn on monitoring mode and schedule it: later runs return an extension only when its users, rating, rating count or version changed, together with the previous values and the differences. A day on which nothing moved produces no extension rows.

Built for extension developers who watch their own extension and their competitors: who shipped a new version, whose rating count is climbing, who crossed the next user tier.

What you get

Field	Example	Notes
name	uBlock Origin Lite	As the store names it
developer	Raymond Hill (gorhill)	The "Offered by" line
users	21000000	See "How the store reports users" below
ratingAverage	4.5	Rounded to 2 decimals; null when the extension has no ratings
ratingCount	3641	The exact count from the page data (the page itself shows "3.6K ratings")
version	2026.930.1227
lastUpdated	2026-09-30	UTC date; lastUpdatedAt has the full timestamp
category	Privacy & Security	categoryPath has the store's own path, e.g. make_chrome_yours/privacy
size	9.2MiB	As written on the page
isFeatured	true	The Featured badge
url	https://chromewebstore.google.com/detail/ublock-origin-lite/ddkjiahejlhfcafbddmgiahcphecmpfh	The address the store redirects to
extensionId	ddkjiahejlhfcafbddmgiahcphecmpfh

Also in every row: shortDescription, developerWebsite (when the store lists one), languagesCount, iconUrl, input (the line you gave), scrapedAt.

In monitoring mode: change (first-check or changed), changedFields, previousUsers, previousRatingAverage, previousRatingCount, previousVersion, previousCheckedAt, usersChange, ratingCountChange, ratingAverageChange.

How the store reports users

The Chrome Web Store publishes an exact user count only below 1,000 (for example 484). From 1,000 up it publishes a rounded figure with one or two leading digits (20000, 2000000, 21000000), and that rounded figure is what users contains. Nothing is estimated. A large extension can therefore show the same users value for weeks. ratingCount is exact at every size, so it is the number that moves first.

Input

{
    "extensions": [
        "https://chromewebstore.google.com/detail/ublock-origin-lite/ddkjiahejlhfcafbddmgiahcphecmpfh",
        "mnjggcdmjocbbbhaepdhchncahnbgone"
    ],
    "monitoringMode": false
}

• extensions - extension page URLs or 32-letter extension IDs. Query parameters such as ?hl= are dropped. Old chrome.google.com/webstore/detail/... links are accepted: the ID is taken from them and the current address is requested. Names are not searched.
• maxExtensions - with monitoring off, stop after this many rows (default 100). A run reads at most 500 lines.
• monitoringMode - return only what changed since the previous monitoring run.
• monitorMode - any-change (default), users-change, rating-change or version-change.
• resetMonitoringState - forget the remembered figures.

Monitoring mode

1. The first monitoring run returns every extension once (change: "first-check") and remembers its figures.
2. Every later run reads each extension again and returns it only if a watched figure differs from the remembered one (change: "changed", with changedFields and the previous values).
3. When nothing changed, the dataset holds a single no-change row that is not charged.

Figures are remembered per extension on your account, not per list, so adding an extension to the list returns only the new one. The remembered figure of an extension is updated when that extension is returned, so a difference is always measured from the last row you received. Do not run two schedules with the same extension at the same moment: the two runs can overwrite each other's memory.

Pricing

Event	When
extension-returned	Each extension row in the dataset
extension-checked	Monitoring mode only: each extension that was read and compared

With monitoring off you pay only for extension rows. In monitoring mode every extension that was read costs one check, and an extension that is returned also costs one row. Rows that explain why something was not returned are never charged: no-such-extension, invalid-input, duplicate-input, unreadable, blocked, disallowed-by-robots, robots-unreadable, no-change, not-read, budget-reached.

If the maximum total charge of a run cannot cover one more check plus its row, the run stops before reading that extension and names the lines it did not read.

What it does not do

• No search and no reviews. The store's robots.txt disallows its search pages and the review pages, so this Actor reads only the extension page. It reads robots.txt at the start of every run and checks each address against it; if robots.txt cannot be read, nothing is requested.
• No developer e-mail addresses.
• No proxy and no workarounds. Requests go out directly, two seconds apart, with a User-Agent that names this Actor. If the store refuses a request or answers with a verification page, the run stops and lists what it did not read.
• Removed and non-existent extensions look the same. For an ID that does not exist and for an extension that was taken down, the store serves the same empty page, so both come back as no-such-extension.

Notes

• The store sends an unknown or removed ID to an "empty" page with HTTP 200. On the page of a removed extension it also suggests other extensions; those figures are never read. A row is produced only when the page data starts with the ID you asked for.
• lastUpdated is the UTC date of the update timestamp; the store shows the date in the viewer's own time zone, which can be one day off.
• category is the category name as the English page writes it. If the page does not show it, category is null and categoryPath still carries the store's path.
• An extension given only by ID takes two requests the first time (the store redirects to the full address); in monitoring mode the address is remembered.

Thanks for using this Actor

We build these tools for people who run them every day, and we improve them from what users tell us.

• Missing a field, or need another filter? Tell us in the Issues tab. If the data is there, we add it.
• Found a bug or a wrong value? Post the run ID in the Issues tab. Wrong data is the thing we fix first.

If this Actor saved you time, a short review helps other people find it.