Skip to content

// stats

Etsy seller tools: live usage stats

Live numbers for the seller tools on this site: the Etsy Fee and Tariff Calculator Chrome extension and the Trial Radar extension. Each figure is a Chrome Web Store count, read from the public users badge or the store's own listing analytics at snapshot time. The current snapshot is November 12, 2026, and the methodology section defines what every metric means.

Data snapshot: November 12, 2026

Etsy Fee and Tariff Calculator

The extension went live in the Chrome Web Store on September 5, 2026. For four weekly reads the public install counter read zero, verified rather than missing, because the Chrome Web Store draws its users badge from one user up and renders nothing at zero, and in the same fetch windows a control listing rendered its badge fine. In the October 8 read, thirty-three days in, the badge appeared for the first time: two users. The October 15 read found the badge gone and the counter back at zero, while the control listing still rendered its badge in the same fetch window. At single-digit counts one uninstall or a store re-sync is enough to take the counter to zero, so the two October 8 users were real and the public read that week was zero. The October 22 read found the same, and the listing had no badge while the control rendered its six users in the same fetch, so the public read stayed at zero. The October 29 read put the badge back: three users, fifty-four days in, with the control listing rendering its six users in the same fetch window. The November 5 read kept the badge at three users, sixty-one days in, with the control listing at six users in the same fetch window. The November 12 read found the badge gone and the counter back at zero, sixty-eight days in, while the control listing rendered its six users in the same fetch window.

The listing saw its first traffic in the week of September 10: four page views and four first visits in the store's own analytics for the listing, and no installs yet. The following week added two page views and two first visits, the week of September 24 added four page views and four first visits, the week of October 1 added three of each, the week of October 8 added one of each, the week of October 15 added two of each, the week of October 22 added three of each, the week of October 30 added two of each, and the week of November 5 added three of each. Installs from the listing have stayed at zero in every weekly window, so whatever the public badge gained on October 8 and lost by October 15, none of it moved through the store's own listing funnel. The fee engine also runs on the open landing, so the tool works without an install; the install counter measures the extension, not the tool.

MetricValueWindow
Public installs (users badge)0as of November 12, 2026
Listing page views3November 5 to November 12, 2026
Installs from the listing0November 5 to November 12, 2026
Listing first visits3November 5 to November 12, 2026
Live sinceSeptember 5, 2026Chrome Web Store
  • The case page tells how the calculator counts the 15% Etsy fee on the DDP tariff charge, the line most fee tools skip.

Trial Radar

Trial Radar, the free trial reminder extension, has been live since August 9, 2026. It held the top spot in the Chrome catalog for its main query across the first three weekly reads, then slipped to second and third as the catalog rotated, the October 1 and October 8 reads left it out of the returned results, and the October 15 read brought it back: a full ten-result page again, with Trial Radar second. The October 22 read took it back out. The static response returned seven results and Trial Radar was not among them, the same short read as the two earlier outs. The October 29 read returned the same seven-result response with Trial Radar still out of it, and the November 5 read returned six results, the shortest static response of the series, with Trial Radar still out of it. The November 12 read returned the full ten-result page with Trial Radar back at the top, the first number-one read since September 3. I read my own badge weekly and the neighbors' badges in the same fetch, so the census below is a same-window measurement, not a mix of dates.

The whole niche is small enough to count in one table. None of the extensions in it had more than 14 users at the last reads, so a position moves on one or two installs, not on volume.

MetricValueWindow
Users6as of November 12, 2026
Rank for "cancel free trial"1November 12, 2026
Listing page views3November 5 to November 12, 2026
Installs from the listing0November 5 to November 12, 2026
Listing first visits3November 5 to November 12, 2026
Reviews0since launch
WeekUsersRank for "cancel free trial"
August 1951
August 2051
September 361
September 1042
September 1753
September 2453
October 14not in results
October 84not in results
October 1542
October 226not in results
October 296not in results
November 56not in results
November 1261
Extension (same fetch windows)UsersMeasured
Trial Reminder14September 10
CancelProof9September 10
Trial Radar (this one)6November 12
Subscription Bee4September 10
  • The users series comes from the store's public badge. The September 17 rank was read from the static search result HTML because the interactive catalog was unavailable that day; the September 24 slice repeated the same method and the position held, so the series stays on it. The October 1 and October 8 static reads each returned only seven results and Trial Radar was not among them; a short read can be an incomplete response rather than a real drop, so every out row carries that same caveat. The October 15 static read by the same method returned the full ten results with Trial Radar back at second, so the return is a same-method read, not a method change. The October 22 static read returned seven results and left Trial Radar out again, the same short response as the October 1 and October 8 reads. The October 22 badge read six users, the first change in the series since the October 1 read, and it ties the series maximum set on September 3. The October 29 badge read six again, the first time the maximum has held across two consecutive reads. The November 5 badge read six again, a third consecutive read at the series maximum. The November 12 badge read six again, a fourth consecutive read at the series maximum.
  • The week of September 17 to 23 returned zero funnel events while the analytics property itself stayed live (the week before returned three page views and one install). The week of September 24 to 30 then returned four page views and four first visits, and the week of October 1 to 7 returned two of each, so the tracking tag is live and the zero week meant the listing had no store traffic, not that the tracking failed. The week of October 8 to 14 returned six page views, three first visits, and the first install since the week of September 10 to 16, the strongest page view week of the series. The week of October 15 to 21 returned one page view, one first visit, and the second install of the series, and the session source was ext_sidebar in the store's analytics, the first non-direct source of the whole series. The week of October 22 to 28 returned three page views, three first visits, and no installs, with two direct sessions and one from Google organic. The week of October 30 to November 5 returned three page views, two first visits, and three installs, every session direct, and no earlier week of the series had returned more than one install. The week of November 5 to 12 returned three page views, three first visits, and no installs, and the session sources were direct, the store sidebar, and a referral from kovnerov.com, the second week of the series with a referral from this site. Five installs in the whole series still sit at the edge of the sample, so this page claims the counts and not a rate.

How the numbers are counted

What counts as an install

The Chrome Web Store shows a users badge from one user up and renders nothing at zero. A zero on this page means the badge was absent while a control listing in the same fetch window rendered its badge, so the fetch itself worked. Weekly badge reads come from the store's public pages; the per-week listing numbers (page views, installs, first visits) come from the Chrome Web Store's own analytics for the listing, which track store traffic and are not consent-gated the way a website analytics property is.

No hand entry

Every figure is copied from a live store page or dashboard read at snapshot time. If a figure ever needs a manual correction, the correction lands as a note next to the table, in the open.

Snapshot and updates

Data snapshot: November 12, 2026 for the install badges; the listing funnel windows are the week of November 5 to November 12, 2026. The page is refreshed on a cadence and every refresh restamps this block, so the date above is the one to cite.

A statistics page that quietly goes stale is worse than none, so each table carries its own window and the notes name every known caveat. If a number here contradicts the live tool, the live tool wins and this page gets the refresh.

All datasets on this page are published under theCC BY 4.0license: quote and reuse with attribution.

FAQ

›Where do these statistics come from?

From my own systems: the Chrome Web Store's public pages and its listing analytics for the extensions. Numbers are read from live sources at snapshot time, and the methodology section defines what every metric means and what counts as an install.

›When was this page last updated?

The snapshot date at the top is the last refresh: November 12, 2026 for the install badges, the week of November 5 to November 12, 2026 for the listing funnels.

›Can I cite these numbers?

Yes. Cite the page and the snapshot date. The counts are cumulative from the dates given in each table, the methodology spells out what each metric means, and known caveats are disclosed in the notes rather than trimmed out.

These tools are what I build for sellers and channels. The live demo stands run without a signup.