mixpanel-browser

About

The official Mixpanel JavaScript browser client library

What detecting mixpanel-browser tells you about a site

mixpanel-browser is the browser SDK for Mixpanel, a long-established product-analytics platform focused on event tracking, funnels, retention and cohort analysis. Finding it tells you the team measures specific user actions deliberately, since Mixpanel's model rewards intentional event design rather than passive page-view tracking. Its presence often indicates a product organisation with dedicated analytics or growth practice, because Mixpanel is typically chosen by teams that build event taxonomies and study behaviour cohorts. It signals a data-informed culture where what users do inside the app is tracked at the action level, not just at the page level.

Why the exact mixpanel-browser version matters

The Mixpanel browser SDK has shifted its defaults over major versions, notably around autocapture, EU data residency options and how it batches and persists events. The exact version tells you which tracking defaults and data-routing options are in play, which matters for understanding both data volume and where that data physically lands.

mixpanel-browser in a real-world stack

When you find mixpanel-browser in a bundle, it rarely travels alone. Sometimes alongside a separate session-replay or A/B tool, since Mixpanel focuses narrowly on event analytics.

Quick facts

What mixpanel-browser pulls in

mixpanel-browser declares 5 direct dependencies — each one also rides into any bundle that ships mixpanel-browser, so they are detection targets too. Reading them is a quick way to understand the package's real footprint .

How Sourcemap Explorer detects mixpanel-browser

mixpanel-browser ships as v2.81.0, published 2026-07-09 and carries 5 direct dependencies, 102 versions on the registry. Those exact numbers are the footprint Sourcemap Explorer matches when mixpanel-browser rides inside a deployed bundle — here is how the detection works.

We catch mixpanel-browser from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/mixpanel-browser/ paths inside the JavaScript sourcemap's sources[] array — that's the canonical signal. When the matching package.json is also captured in sourcesContent[], we read the exact version field — patch number included. No regex guessing, no version inference.

1. 1

   Confirm the site exposes sourcemaps

   In DevTools Network, check the response headers of any application script for `SourceMap` or `X-SourceMap`. Failing that, fetch the script's last 4 KB and look for a `//# sourceMappingURL=` comment — that map is where the `mixpanel-browser` paths live.

2. 2

   Find the package in the bundle

   Open DevTools → Network → reload. Click any application script and look at its sourcemap. Inside, search `sources[]` for entries matching `node_modules/mixpanel-browser/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/mixpanel-browser/package.json` gives you the exact installed version.

3. 3

   Read the version directly from package.json

   Run `jq -r '. as $m | $m.sources | to_entries[] | select(.value | endswith("node_modules/mixpanel-browser/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.

Recent versions

mixpanel-browser README

Live mirror of the GitHub README, for reference. Updated whenever the repo's default branch changes.

npm install --save mixpanel-browser

import mixpanel from 'mixpanel-browser';

mixpanel.init("YOUR_TOKEN", {autocapture: true});
mixpanel.track("An event");

import mixpanel from 'mixpanel-browser/src/loaders/loader-module-core';

import mixpanel from 'mixpanel-browser/src/loaders/loader-module-with-async-modules';

<script type="importmap">
{
  "imports": {
    "mixpanel-browser": "https://cdn.mxpnl.com/libs/mixpanel-js/dist/mixpanel.module.js"
  }
}
</script>
<script type="module" src="main.js"></script>

// main.js
import mixpanel from 'mixpanel-browser';

mixpanel.init('YOUR_TOKEN', {autocapture: true, debug: true, persistence: 'localStorage'});

FAQ