aptabase alternative

The Chrome-native alternative
to Aptabase.

Aptabase is great for multi-platform analytics. But if you only ship Chrome extensions, Crxlytics gives you MV3 lifecycle tracking, churn detection and uninstall surveys — built specifically for chrome-extension:// origins.

Free to startMV3 nativeNo credit card

Let's be upfront: Aptabase is a solid tool. Open source, privacy-respecting, fair pricing, supports Web, iOS, Android, Desktop and Chrome extensions from one SDK. If you need cross-platform analytics, it's a legitimately good choice.

Crxlytics is different on one axis: we only do Chrome extensions, and we go deep. Manifest V3 service-worker hardening, automatic install/update/uninstall tracking, churn pattern detection, attribution from the Chrome Web Store, uninstall surveys. Things you'd otherwise build yourself on top of any generic analytics SDK.

// side-by-side

Crxlytics vs Aptabase

Where Crxlytics goes deeper. Where Aptabase has the edge.

FeatureAptabaseCrxlytics
Chrome extension support
Manifest V3 service-worker safe
Privacy-first (no PII, no fingerprinting)
Auto install / update / uninstall tracking
Crxlytics wires chrome.runtime.onInstalled, setUninstallURL automatically
chrome.alarms-based flushing (survives SW termination)
Pre-init event buffer
Events fired during async init aren’t dropped
Churn pattern detection
Single-session, error-driven, never-activated, site-trigger churn
Chrome Web Store attribution
Uninstall reason surveys
planned
Service-worker health metrics
planned
CWS rating monitoring
planned
Multi-platform (iOS, Android, Desktop, Web)
Open source
Self-hostable
API code can be deployed; dashboard is hosted
partial
Battle-tested in production
early access
✓ available · ○ possible with custom code · – not in scope · planned: on the roadmap
// why developers switch

What you get out of the box that you’d otherwise build.

01

You stopped fighting MV3 bugs.

Service workers suspend after 30s of inactivity. Most analytics SDKs lose events when that happens. Crxlytics uses chrome.alarms to wake the worker on schedule, flushes on onSuspend, and buffers events that fire before init completes — so install/uninstall events never get silently dropped.

02

You see why users leave.

Aptabase tells you the event count. Crxlytics correlates uninstalls back to last-seen patterns — was it the error 3 days ago, the never-activated cohort, the site-specific trigger? The churn engine surfaces patterns automatically.

03

You don’t build your own funnels.

Chrome Web Store attribution, install → activated → retained cohorts, feature usage heatmaps — wired by default. With a generic SDK you’d build all of this on top in SQL or a custom dashboard.

// when aptabase is the better fit

We won’t pretend.

If any of these apply, Aptabase is probably the better choice for you:

  • ·You ship beyond Chrome. Mobile apps, desktop, web — Aptabase has one SDK for all of them. Crxlytics only does Chrome extensions.
  • ·You need open source. Aptabase is Apache 2.0 — self-host the entire stack yourself. Crxlytics is closed source for now, though our API can be deployed standalone.
  • ·You need it today. Aptabase is battle-tested in production. Crxlytics is in early access — we’re shipping fast, but if you need years of track record right now, take the safer bet.
// already on aptabase?

Migration takes ~15 minutes.

You can run both SDKs in parallel for a few weeks if you want. Both expose a similartrack(event, props) API — most call sites change one import and you’re done. Auto-events (install/update/uninstall) are wired for you automatically.

// background.js — Manifest V3 service worker
importScripts('vendor/crxlytics.min.js')

self.Crxlytics.init({
  apiKey: 'pk_live_…',
  apiUrl: 'https://crxlyticsapi.../v1',
})
// faq

Common questions, honestly answered.

Aptabase is a multi-platform analytics tool (Web, iOS, Android, Desktop, Chrome extensions) with a single generic SDK. Crxlytics only does Chrome extensions but goes deeper: MV3 service-worker hardening, automatic install/update/uninstall tracking, churn pattern detection, Chrome Web Store attribution, and uninstall surveys — features you’d otherwise build on top of a generic analytics SDK.
// get started

Try Crxlytics. Stay on Aptabase if it loses.

No lock-in. Both SDKs run side-by-side. Founder pricing locked in for waitlist signups.