Skip to main content

Overview

The Mixpanel browser extension, formerly called the Mixpanel Data Inspector, does two jobs:
  • The Data Inspector shows the events your web app sends to Mixpanel in real time, so you can validate tracking, debug data issues, and check data quality during development and testing.
  • The visual editor for Web Experiments lets you select elements on your live site, preview changes, and save them as experiment variants without a code deploy.
The visual editor is available in the Chrome extension only. The Data Inspector is available in Chrome and Firefox.

Data Inspector

View SDK Events

  • Monitor events sent from the Mixpanel SDK in real time
  • See events as they’re transmitted to Mixpanel servers
  • Track both successful and failed event calls

Inspect JSON Payloads

  • View the complete JSON payload for each event
  • Copy the JSON payload to your clipboard for analysis
  • Examine event structure and data formatting

Search Events and Properties

  • Search through event payloads to find specific properties
  • Filter out noisy events to find what you need
  • Inspect registered super properties and other event metadata

Web Experiments Visual Editor

The extension connects your Mixpanel tab to your website so you can design experiment variants directly on the page. With the extension installed, you can:
  • Select an element on your page and change its text, colors, CSS, classes, or attributes, or hide it
  • Describe a change to Mixpanel Agent and approve the edits it proposes
  • Switch between variants to preview each one on your live page
  • Review every change in the changes list and delete any you don’t want
  • Save your changes as variants of a Web Experiment
To open the editor, create a Web Experiment in Mixpanel, enter the URL of the page you want to test, and click Edit in Editor. Your site opens in a new tab with the editor toolbar on top. Variants still reach your end users through the Mixpanel JavaScript SDK, so visitors don’t need the extension and can use any browser. Your site needs the Web Experiments snippet installed before the editor can load. See Web Experiments for setup, targeting, permissions, and limits.

Installation

Chrome

  1. Open the Mixpanel extension in the Chrome Web Store
  2. Click Add to Chrome
  3. Confirm installation in the pop-up dialog
  4. If you plan to use Web Experiments, refresh any open Mixpanel tabs. Mixpanel checks for the extension when the page loads.
If you already have the Mixpanel Data Inspector installed in Chrome, update it to the latest version. It’s the same extension under its new name, so there’s nothing to uninstall or disable.

Firefox

  1. Open Mixpanel Data Inspector on Firefox Add-ons
  2. Click Add to Firefox
  3. Follow the installation prompts

Using the Data Inspector

  1. Install the extension from your browser’s extension store
  2. Go to a page on your site where Mixpanel tracking is implemented
  3. Click the Mixpanel icon in your browser toolbar to open the extension
  4. Interact with your site to trigger events and watch them appear in real time
  5. To keep the inspector open while you work in Chrome, open it as a DevTools panel through Inspect Element

Common Use Cases & Best Practices

Implementation Validation

Use Cases:
  • Verify events are being sent correctly from your Mixpanel SDK
  • Check that all expected properties are included in event payloads
  • Confirm event timing and sequencing
Best Practices:
  • Keep the Data Inspector open while implementing new tracking
  • Use the copy feature to document expected payload structures
  • Search for critical properties to ensure consistent naming

Debugging and Troubleshooting

Use Cases:
  • Identify missing or malformed event properties
  • Debug tracking issues before they reach production
  • Validate A/B test or feature flag implementations
Best Practices:
  • Start by checking if events appear in the extension
  • Use JSON view to examine payload structure and values
  • Search for specific properties that may be causing issues

Quality Assurance & Testing

Use Cases:
  • Examine complete event structure and nested properties
  • Compare expected vs. actual event data
  • Understand property naming conventions and values
Best Practices:
  • Validate tracking across different user flows
  • Copy and compare payloads between different test scenarios
  • Use search to verify that required properties are present

Property Discovery & Analysis

Use Cases:
  • Search for specific properties across multiple events
  • Copy JSON payloads for further analysis or documentation
  • Identify inconsistencies in property implementation
Best Practices:
  • Use search functionality to locate properties of interest quickly
  • Copy payloads to share with team members or include in documentation
  • Regularly review property naming and value consistency

Troubleshooting

Events Not Appearing

  • Verify SDK implementation: Ensure Mixpanel SDK is properly installed and configured. See JavaScript SDK documentation for installation methods.
  • Check browser console: Look for JavaScript errors that might prevent tracking
  • Refresh the page: Some events only fire during page initialization
  • Disable ad blockers: Ad blockers may prevent events from being sent to Mixpanel servers

The Visual Editor Reports the Extension Is Missing

  • Refresh the Mixpanel tab. Mixpanel detects the extension when the page loads.
  • Confirm the extension is updated to the latest version and enabled.

Support

For technical support or feature requests:
  • Report issues through your standard Mixpanel support channels
  • Include browser version and extension version in reports
  • Provide specific JSON payload examples when reporting data issues