GA4 was never built for extensions — Measurement Protocol wiring, stored client IDs, permissions that trip Chrome Web Store review. Datibase is a copy-paste SDK with zero permissions, showing usage × revenue in one dashboard you'll actually open.
sample data
See which features people actually use — popup opens, side panel sessions, custom events — next to Stripe or Polar revenue and your Chrome Web Store user count.
The SDK requests zero extension permissions and never touches chrome.* APIs. No cookies, no storage, no fingerprints — you keep your "Does not collect user data" privacy disclosure.
One audited, unminified file you paste into your source tree. No npm install, no dependency tree, no remote code — read the whole SDK before you ship it.
Grab the single-file SDK from /install and paste it into your extension's source tree. No npm, no build step — verify the published SHA-256 and it's yours.
import { datibase } from "./lib/datibase.mjs";
datibase.init({ key: "wbs_xxx" });Add one host_permissions entry to your manifest.json. That's the only permission the SDK will ever need.
{
"manifest_version": 3,
"host_permissions": ["https://datibase.dev/*"]
}Works from service workers, popups, side panels, and content scripts. Track views and custom events with one call.
datibase.trackView("popup");
await datibase.track("feature_used", { plan: "pro" });Link Stripe or Polar to see revenue alongside usage. Optional — skip if you only need usage analytics. Revenue totals use USD assumptions today.
Side projects
Weekend hackers
For growing businesses
For large apps
GA4 doesn't work inside extensions out of the box — you have to wire up the Measurement Protocol by hand, generate and persist your own client IDs, and explain all of it in your privacy disclosure. Datibase is one file you paste in: no stored IDs, no permissions, and a dashboard that shows usage next to revenue.
It's designed not to. The SDK requests zero extension permissions and never calls chrome.* APIs — no cookies, no storage, no webRequest. The only manifest change is a single host_permissions entry for the datibase endpoint, and there's no remote code, so it's compatible with MV3 review requirements.
No cookies. No fingerprinting. No persistent storage — visitor IDs live in memory and rotate daily, so the same browser looks like a new visitor tomorrow. DNT and Global Privacy Control are respected, we don't store full IP addresses, and we've never shared data with a third party.
Yes. A project can be a Chrome extension, a website, or both. Websites use the same privacy model with an async <script> tag — no cookies, no consent banner — and everything lands in the same dashboard.
Yes. Datibase integrates with Stripe and Polar so you can attribute revenue to usage and subscriptions in your dashboard. Connect the provider you use for billing and keep analytics in one place. Revenue numbers assume USD today.
Yes. Manage your subscription through the billing portal linked from your account settings.
Start free. No credit card. No extension permissions. No calls from our sales team — because we don't have one.
Start free