Skip to main content
Pre-release. This guide applies when the Integrations hub is enabled for your ABConvert account.
Use Mixpanel’s Experiment report and product analytics to compare behavior after an ABConvert test-group exposure. ABConvert uses your existing Mixpanel Browser SDK.

​
Configure Mixpanel and ABConvert

1

Select a Mixpanel project

Initialize one Mixpanel Browser SDK for the storefront project that receives your product events. Load it after analytics consent.
2

Keep one browser SDK owner

If a Shopify app owns Mixpanel on the storefront, do not add a second theme browser SDK. Send page and commerce events through the same project.
3

Enable Mixpanel in ABConvert

In Integrations, enable Mixpanel. ABConvert uses the existing mixpanel.track and mixpanel.register_once methods.
4

Verify an exposure

Visit an eligible active test in a fresh, consented browser. In Mixpanel Events, confirm $experiment_started, then inspect Experiment name and Variant name.

​
What Mixpanel receives

The exposure format uses Mixpanel’s exact, case-sensitive property names. The super property uses register_once, so it remains browser-cookie-local and keeps its first value by default for the life of that cookie.

​
Use cases

  • Use Mixpanel Experiments: choose $experiment_started as the exposure event and compare a success metric against Control.
  • Analyze funnels: filter any funnel by [ABConvert] <test name> to compare checkout progression by test group.
  • Explore retention: measure whether people exposed to a group return or take a later product action.

​
Things to know

  • The exposure is sent at actual exposure, not merely when a visitor starts a session.
  • The super property is not a cross-device identity or a permanent attribution record. Configure identity and purchase events separately in Mixpanel.
  • A current vendor receipt requires an eligible non-preview visitor. A loaded SDK or an ABConvert Connected state is not sufficient evidence.