Built for extensions, not adapted to them
Moderok only does one thing: tell you what your browser extension does after it leaves your machine.
What it does
- Trends, events, and logs
Daily and monthly actives, installs, updates, uninstalls and errors — plus which features get used, how often, and on which version.
Every event is also in the log, filterable and expandable to raw JSON.
- Survives the service worker
Usage lines up with what actually happened, even when the browser suspends or restarts your extension.
Events queue in
chrome.storage.localand flush when the service worker wakes.- Nothing extra in your manifest
One package, zero dependencies, and no host permissions to request at install.
Store review sees the same permission list it saw before.
- Your events, your schema
You choose what to track and what each event carries.
Nothing is inferred and nothing is renamed.
Why Moderok
- Built for browser extensions first, so the flows match how you ship and publish updates.
- Trends, events and logs sit in one place — go from a shape change in a chart to the raw rows behind it.
- Works against a listed Chrome extension or a local build you have not launched yet.
- The client stays small and asks for nothing extra in your manifest, so store review stays boring.
- Every tier has the same charts and tools; a bigger plan only raises the monthly event allowance.
Connect your listing
When you are on the Chrome Web Store, link the extension in the dashboard so installs and store details stay tied to your app. Skip this while you are still local-only. Read the setup guide
Roadmap
- A/B testsComing soon
- Compare variants and rollouts next to the rest of your analytics.