The Web Store’s dashboard
“Aggregated data regarding installs, number of users, and average ratings”, in the words of its developer FAQ.
See what sells, and why they leave
Chrome extension analytics,from install to paid.
For every extension you sell with Toolaby: the devices it runs on, the way from a new device to a purchase, the feature that opened the paywall before each sale, and why people uninstall. Nothing to add to your code.
Word Counter · 17 Sept – 16 Oct
30 daysRevenue
$1,750.33
+16% vs $1,505.28 the 30 days before
Active devices
2,640
+47% vs 1,790 the 30 days before
New devices
3,386
+11% vs 3,047 the 30 days before
From a new device to a purchase
- New devices3,386100%
- Met the paywall74422.0%
- Opened checkout2316.8%
- Paid1183.5%
Monthly recurring revenue
$501.71
+22% vs $411.10 the 30 days before
Uninstalls
212
−12% vs 241 the 30 days before
Features
Which feature sells.
Every purchase is counted against what opened the paywall before it: a feature by the name you gave it, or the free uses running out. Lead your store listing with the one that sells.
The first 3 open 90% of all paywall opens
#Opened byPaywall opensCheckoutsPurchasesOpens to paidRevenue
1Export to CSV2,410164712.9%$355
2Free uses ran out1,88092382.0%$190
3Readability score9403170.7%$35
4Daily word goals6101220.3%$10
Uninstalls
Ask why, before they go.
When someone removes your extension, Chrome opens a short page that asks why, in their language. A buyer still paying sees how to stop, and you get an email when one leaves.
Word Counter is removed
Thank you for trying it. One question, if you have a moment: why did you remove it?
Your purchase still stands
Removing the extension cancels nothing. A subscription goes on until you cancel it on your account page.
Your accountPick a reason first
Why they left, this month
102 answers from 212 removals, 4 of them by someone paying.
102
answers
Versions and experiments
Every release, every price.
See each build take over and what it sold, and test two prices of a plan, or two headlines on its paywall, on the devices that meet it.
Builds in use
2.4.0 took over in ten days; 2.4.1 in five.
- v2.4.1
- v2.4.0
- v2.3.0
Lifetime at $7
Half the devices that met the paywall saw $7 for the lifetime plan.
- A, at $59.1% bought · $0.46 a device
- B, at $77.4% bought · $0.52 a device
B brings more for each device, by 14%, and a difference that size is unlikely to be chance (p = 0.36).
Why it knows
The sale and the device, together.
An analytics script
The events your own code sends it, once you add it, keep it working and say so in your privacy policy.
Toolaby
The device, the paywall it met, the sale it made and the day it left, tied together, because Toolaby takes the payment and checks the licence.
Your users’ data
Counted, and no more.
A device is the id your extension already signs its requests with. Counting is off for each tool until you turn it on, once your privacy policy says what is counted, as the Chrome Web Store asks. Each day's counts are kept thirteen months.
Counted
- The days a device runs your extension
- Its version
- How often the paywall opened, and what opened it
- Its first checkout and its purchase
- The day it was removed, and the answer, if given
Never counted
- Names or email addresses
- IP addresses
- The pages your extension runs on
- Anything your extension does beside the paywall
The words for your own privacy policy are in Your data.
Plans
On Hobby, and more on Pro.
Every part counts on every plan. A workspace that moves to Pro sees the rest, and its history, at once.
PartHobbyPro
Overview
Revenue
Devices
Funnel
Features
Uninstalls
Versions
Experiments
Analytics export and API
Analytics history30 daysThirteen months
Questions
Chrome extension analytics, asked.
How do I add analytics to a Chrome extension?
Wire the extension to Toolaby with npx -y toolaby@latest wire <tool-id>, then turn counting on in the tool's settings once your privacy policy says what is counted. Devices are counted from the hourly check-in the client makes, the paywall counts what opened it, and revenue is read from your Stripe account. There is no analytics code to write. The guide
Can I use Google Analytics in a Chrome extension?
Yes. An extension can send events to Google Analytics 4 through its Measurement Protocol, and Google Analytics reports the events your code sends. Toolaby counts the paywall, the checkout and the sale itself, because it takes the payment and checks the licence, so it can tell which device paid and what opened the paywall before.
How do I see why users uninstall my Chrome extension?
Chrome can open a page when an extension is removed (chrome.runtime.setUninstallURL). Toolaby sets one that asks why, in the person's language, with seven reasons and a note, and shows a buyer still paying how to stop. The answers are under Analytics, Uninstalls. The uninstall page
Does the Chrome Web Store show active users?
Yes, in aggregate. Its developer dashboard gives "aggregated data regarding installs, number of users, and average ratings", in the words of its developer FAQ. Toolaby counts each device your extension runs on: the devices active each day, in 7 days and in 30, how many of each week's new devices come back, and which of them paid.
What does Toolaby count about my users?
Only what a tool's developer turned counting on for. For each device: the days it ran, its version, how often the paywall opened and for which feature, its first checkout and purchase, the day it was removed and the reason given, if any. No names, email addresses or IP addresses, and nothing about the pages the extension runs on. Each day's counts are kept thirteen months. Your data
How much does it cost?
On Hobby, which is 0.5% of a sale: Overview, Revenue, Devices and Funnel, with 30 days of history. On Pro, $25 a month per workspace with no fee on sales: Features, Uninstalls, Versions, Experiments, CSV files and the API as well, and thirteen months of history. Pricing