1What FoxPlug reads from Chrome Web Store
These are the exact things it reads, and nothing else.
| What | The details it takes |
|---|---|
| The extension's public listing page | fetched from chromewebstore.google.com/detail/ with the 32 letter id; the page's data is parsed for the fields below |
| Name and id | the extension's name and its 32 letter id |
| Version | the listing's version number, when the page shows one |
| Users | the user count shown on the listing, used for the user milestones |
| Rating and number of ratings | the average star rating and how many ratings; they appear in the read summary and the stored snapshot, not as moments |
2Moments it finds, and what each becomes
A moment is one thing that happened in Chrome Web Store worth a second look. Each one is scored, then it becomes a post, a changelog entry, a thing to fix or an idea to email, or it is skipped.
the listing shows a different version than the last read
The moment is titled like this: Released Tab Tidy 3.2.0
Your made-up extension Tab Tidy moves from 3.1.4 to 3.2.0 on its listing. On the next Check for what's new FoxPlug writes 'Released Tab Tidy 3.2.0' with 'Tab Tidy 3.2.0 is published on the Chrome Web Store.' and the listing link, which can become a post and a changelog entry.
the user count crosses 100, 500, 1,000, 5,000, 10,000, 50,000, 100,000 and on up
The moment is titled like this: Tab Tidy passed 5,000 users
Tab Tidy shows 5,430 users on its listing. FoxPlug writes 'Tab Tidy passed 5,000 users' with 'Tab Tidy now has more than 5,000 users (5,430 at the last read).' It fires once per step.
the listing page can no longer be read in the expected shape
The moment is titled like this: no moment: the read reports 'chromewebstore.google.com: the listing page could not be read'
If Google changes the listing page, FoxPlug stops with that message rather than guessing a number. Nothing is written for that read.
3How the brain uses it
The rules below are the ones that apply to Chrome Web Store. The same rules, with worked examples, are on the brain page.
- A new version becomes an update and a changelog entry. A user milestone (100, 500, 1,000, 5,000, 10,000 and so on) becomes an update, once per step. How the brain decides
- The Chrome Web Store is read from public pages, so nothing secret is needed. How the brain decides
- Reads happen only when you press Build the brief or Check for what's new. How the brain decides
4Set up Chrome Web Store in a few steps
Access: none: the public listing address or id only (no login, no key). What to give it: extension id or listing link only, nothing secret.
- Open your extension's page on chromewebstore.google.com.
- Copy the address from the browser bar, or just the 32 letters at the end of it.
- Paste it into FoxPlug. To watch several extensions, separate them with commas (up to 5).
- Press Connect.
5Limits worth knowing
Where it stops, so nothing surprises you.
- Up to 5 extensions per connection.
- Only the public listing page is read; if its data cannot be parsed the read stops with an error.
- The first read only records a baseline; a version moment fires only after a version was stored and differs.
- A version moment needs the listing to show a version number; if it does not, only users are tracked.
- No 1-star or 5-star moments: the store gives no public review feed, so new ratings are not read.
- Each request waits up to 25 seconds.
6What it never reads
Read only means read only, and the list below is what the code leaves alone.
- Any login of yours (it reads only the public listing page)
- New ratings or reviews (the store has no public reviews feed, so none are read here)
- Your developer dashboard or extension package
7How Chrome Web Store differs from the tools next to it
WordPress.org also needs no login, but gives a public ratings breakdown so new 1-star and 5-star ratings are noticed; the Chrome Web Store has no public reviews feed, so FoxPlug reads version, users, rating and rating count only.
8Questions
Do I paste my developer account details?
No. You paste the listing address or the 32 letter id. FoxPlug reads the public listing page, so there is no key and no login.
Does FoxPlug tell me about new reviews on my extension?
No. The store has no public reviews feed, so FoxPlug does not read new ratings there. It reads version, users and the average rating and rating count.
What does it write moments about?
A new version and the user count crossing a step such as 1,000 or 10,000. Each step fires once.
What if Google changes the listing page?
FoxPlug says the listing page could not be read and writes nothing for that read, instead of guessing.
Checked with a real connected account of ours: real public listing read of uBlock Origin Lite 2026.1103 (22M users, 4.5 stars) through the shipped reader (T1670, T1683).
FoxPlug reads this tool only when you press Check for what's new, and only to read. Plans and limits are on the pricing page. Questions: support.